April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1029919] New: zypper crashes when baseurl does not contain http/https
by bugzilla_noreply＠novell.com 13 Oct '22

13 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1029919 Bug ID: 1029919 Summary: zypper crashes when baseurl does not contain http/https Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: wattersm(a)watters.ws QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper crashes when a repo file is missing the protocol in the download URL. For example, the following repo file causes zypper to crash. [home_Ximi1970_openSUSE_Extra] baseurl=download.opensuse.org/repositories/home:/Ximi1970:/openSUSE:/Extra/… enabled=1 gpgcheck=1 gpgkey=download.opensuse.org/repositories/home:/Ximi1970:/openSUSE:/Extra/o… priority=99 autorefresh=1 keeppackages=1 type=rpm-md Running any zypper command results in a crash as follows. linux-0yvh:~ # zypper search bacula Unexpected exception. Url scheme is a required component Please file a bug report about this. See http://en.opensuse.org/Zypper/Troubleshooting for instructions -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1166289] New: virt-viewer: Missing upstream bug fixes
by bugzilla_noreply＠novell.com 12 Oct '22

12 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1166289 Bug ID: 1166289 Summary: virt-viewer: Missing upstream bug fixes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: carnold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are upstream patches fixing bugs needed for this version of virt-viewer. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 920901] New: USB mouse disconnects every 60 seconds without X
by bugzilla_noreply＠novell.com 11 Oct '22

11 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=920901 Bug ID: 920901 Summary: USB mouse disconnects every 60 seconds without X Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: oneukum(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some mice need X to run or will disconnects and reconnect every 60 seconds. The fix is a new quirk to always poll. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1130084] New: openSUSE:Leap:15.1/piglit failed
by bugzilla_noreply＠novell.com 11 Oct '22

11 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1130084 Bug ID: 1130084 Summary: openSUSE:Leap:15.1/piglit failed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://build.opensuse.org/package/live_build_log/open SUSE:Leap:15.1/piglit/standard/x86_64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mimi.vx(a)gmail.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Leap:15.1/piglit failed to build. Please see build log: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1/piglit… Job gets stuck, rebuild doesn't help -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1160059] New: openSUSE:Leap:15.2/ltrace failed
by bugzilla_noreply＠novell.com 11 Oct '22

11 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1160059 Bug ID: 1160059 Summary: openSUSE:Leap:15.2/ltrace failed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://build.opensuse.org/package/live_build_log/open SUSE:Leap:15.2/ltrace/standard/x86_64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: matz(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mischa.salle(a)gmail.com Found By: --- Blocker: --- openSUSE:Leap:15.2/ltrace failed to build. Please see build log: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.2/ltrace… -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1096050] New: sudo doesn't work after upgrade from leap 42,3
by bugzilla_noreply＠novell.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1096050 Bug ID: 1096050 Summary: sudo doesn't work after upgrade from leap 42,3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: alarrosa(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading to Leap 15.0 from 42.3, sudo shows an error in the first lines: sudo: PERM_ROOT: setresuid(0, -1, -1): Operation not permitted sudo: unable to open /var/lib/sudo/ts/antonio: Permission denied Then it asks for the root password as usual, but it doesn't accept it (I can log in as root, so I know it's correctly written). After writting it 3 times, it fails with: sudo: unable to send audit message: Operation not permitted sudo: PERM_ROOT: setresuid(0, -1, -1): Operation not permitted The user id output: uid=1000(antonio), gid=100(users) groups=100(users),10(wheel),485(kvm) The output from 'rpm -V sudo' is: .M....... g /var/lib/sudo .M....... g /var/lib/sudo/ts So I reinstalled the package and ran 'rpm --setperms sudo' with no change. Btw, the package seems to set the permissions of the /var/lib/sudo/ts directory to 000 but I had other working systems where the permissions are 700, so I set it to that. In any case, the owner is root:root. I also tried reinstalling pam and pam-config with no luck. Any idea of what to try? -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1166616] New: Ansible requires rebuild to work with python3.8 upgrade
by bugzilla_noreply＠novell.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1166616 Bug ID: 1166616 Summary: Ansible requires rebuild to work with python3.8 upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: elimat(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- A rebuild of ansible is required for it to be work with python3.8 upgrade. Right now the only option is to deinstall ansible if I do a zypper dup -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1143725] New: qemu-aarch64-binfmt, from qemu-linux-user, not working (no output)
by bugzilla_noreply＠novell.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1143725 Bug ID: 1143725 Summary: qemu-aarch64-binfmt, from qemu-linux-user, not working (no output) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Context: I want to run an ARM64 (aarch64) container on an x86 host. This is possible using qemu Linux user emulation and Linux binfmt. It is supposed to work like this: //Fetching an ARM container on x86 (long story) $ skopeo --override-arch arm64 copy docker://opensuse/leap docker-daemon:opensuse-arm64/leap:latest //Install qemu Linux user, and setup binfmt for aarch64 # zypper install qemu-linux-user $ cp /usr/bin/qemu-aarch64-binfmt . # echo -1 > /proc/sys/fs/binfmt_misc/qemu-aarch64 # echo ':qemu-aarch64:M:0:\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-aarch64-binfmt:POCF' > /proc/sys/fs/binfmt_misc/register //Build our container $ cat << EOF > Dockerfile FROM opensuse-arm64/leap COPY qemu-aarch64-binfmt /usr/bin/qemu-aarch64-binfmt EOF docker build -t qemu-leap . //Now I should be able to run the ARM container, like this: # docker run -it qemu-leap-aarch64-binfmt /bin/sh But, basically, nothing happens. No output at all, and I'm definitely not inside an ARM container. Actually, it appears the container exited: $ docker ps --all CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ea2252caf90a qemu-leap "/bin/sh" 4 seconds ago Exited (255) 3 seconds ago relaxed_goodall Now, if I, instead of qemu-aarch64-binfmt, use a qemu-aarch64-static binary copied from a Debian unstable box I have in my home network, i.e., this one: # ./qemu-aarch64-static -version qemu-aarch64 version 3.1.0 (Debian 1:3.1+dfsg-8) Things work! In fact: $ docker run -it --rm qemu-leap uname -a Linux bf12752f6a51 5.1.16-1-default #1 SMP Wed Jul 3 12:37:47 UTC 2019 (2af8a22) aarch64 aarch64 aarch64 GNU/Linux Note the *aarch64*. Of course, we need to change the aarch64 interpreter file too, in /proc/sys/fs/binfmt So, basically, it looks like the procedure is correct, or at least can work. But our qemu-linux-user packages contain binaries that are not adequate for being used for this use case. Things/differences to check: - QEMU version (the debian stolen from Debian, that makes things works is from QEMU 3.1.0, while we ship 4.0.0 - our patch queue - our configuration and compile options -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1062518] New: x2gothinclient(d) is missing File/Path/Expand.pm perl module
by bugzilla_noreply＠novell.com 06 Oct '22

06 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1062518 Bug ID: 1062518 Summary: x2gothinclient(d) is missing File/Path/Expand.pm perl module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- Starting x2gothinclientd cause the message Can't locate File/Path/Expand.pm in @INC (you may need to install the File::Path::Expand module) (@INC contains: /usr/lib/perl5/site_perl/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.26.1 /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.26.1 /usr/lib/perl5/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/5.26.1 /usr/lib/perl5/site_perl) at /usr/sbin/x2gothinclientd line 23. AFAICS there is no such file below /usr/lib/perl5/ nor any provides of 'perl(File::Path::Expand)' -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1041794] New: Recent update breaks some Youtube videos
by bugzilla_noreply＠novell.com 04 Oct '22

04 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1041794 Bug ID: 1041794 Summary: Recent update breaks some Youtube videos Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: james.knott(a)rogers.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- An update around mid May caused some Youtube videos to fail. When this happens, loading the video stops, leaving only the dot going around a circle showing. This happens with Firefox, Seamonkey and Chromium browsers. The videos that fail play OK in Windows. To verify the problem, I tried the videos with a VirtualBox VM or a fresh 42.2 install. The problem videos played. I then cloned the VM and ensured the videos played. I then updated the clone to the latest updates and now the videos fail. The original non-updated VM still continued to play the videos. It appears the problem is related to the type of codec used. For example, videos with the vp9 codec play, but those with avc1.4d400d now fail. Here are 2 links, this one plays OK: https://www.youtube.com/watch?v=Rzqq581Q3Us But this one doesn't: https://www.youtube.com/watch?v=t8tdmaEhMHE Again, this problem occurred recently. Videos that played a few weeks ago now fail. -- You are receiving this mail because: You are on the CC list for the bug.

2 14