October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[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 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

[Bug 1137997] New: Expert Partitioner: import multi-device Btrfs mount points
by bugzilla_noreply＠novell.com 04 Oct '22

04 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1137997 Bug ID: 1137997 Summary: Expert Partitioner: import multi-device Btrfs mount points Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jlopez(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When importing mount points from a system with a multi-device Btrfs filesystem, the multi-device Btrfs is imported as a single-device. It should reconstruct the multi-device Btrfs, if possible. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 993401] New: grub2-install for EFI installs an EFI entry that is not bootable
by bugzilla_noreply＠novell.com 30 Sep '22

30 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=993401 Bug ID: 993401 Summary: grub2-install for EFI installs an EFI entry that is not bootable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: aarch64 OS: openSUSE 42.1 Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: alan(a)softiron.co.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Running grub2-install does not yield a bootable entry in EFI's boot menu. On Leap and Tumbleweed, this means booting relies instead on the startup.nsh in the EFI partition. This occurs on Aarch64 with both AMD/AMI firmware and Tianocore/edk2/OpenPlatformPkg firmware. Steps to reproduce: 1. Install Leap 42.1 from the OEM image 2. Restart and boot the system 2a. Observe that the startup.nsh (in the EFI partition) is used to boot the system. 3. Reboot again, but During boot-up, enter the EFI menu. 3a. Observe that in the boot manager in the EFI menus, there is no entry for Leap. 4. Restart the system or select the UEFI shell option, booting from startup.nsh 5. From the command prompt in Leap, run: grub2-install /dev/sda 6. Reboot the system 7. During start-up enter the EFI menu. 7a. Observe that in the EFI menu there is an entry called opensuse-leap42.1-arm-jeos-devel-efi, or something like it. 8. Select the opensuse-leap* boot menu item and try to boot it. 9. Observe that it does not boot, and returns to the boot menu. 10. Select the UEFI Shell option, and observe that it will boot using startup.nsh. 11. From the Linux command prompt, run "efibootmgr -v" 11a. Observe that the entry for opensuse-leap* is truncated :( 11b. Note the same can be observed by running "dumpstore" from the EFI environment. Note: The same thing happens if the bootloader is re-installed using "yast2 bootloader". Note that this is broken in Leap, but works fine in SLES, probably because the path and OS name for SLES is so much shorter. Interestingly, if I try to add my own entry with the proper path: efibootmgr -c -d /dev/sda -p 1 --loader "EFI\\opensuse-leap42.1-arm-jeos-devel-efi\\grubarm64.efi" -L Test_Entry_By_Alan and then inspect it with: efibootmgr -v I see my entry is truncated too :( Boot0007* Test_Entry_By_Alan HD(1,800,64004,cb3a713f-f051-4c9c-b643-b9e1358f6c2d)File(EFI\opensuse-leap42.1-arm-jeos-devel-ef) In summary, grub2-install and/or efibootmgr is simply putting a boot entry into NVRAM that is truncated and not valid. Thanks! Alan. -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 1079439] New: New area for ARCES Inter-Department Research Center Bologna
by bugzilla_noreply＠novell.com 26 Sep '22

26 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1079439 Bug ID: 1079439 Summary: New area for ARCES Inter-Department Research Center Bologna Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request Assignee: mrueckert(a)suse.com Reporter: marco.giusti(a)posteo.de QA Contact: adrian(a)suse.com Found By: --- Blocker: --- We first reached OBS at ARCES[1] after the demand of porting our application, Virtualbricks[2], to SLE 12. Even without any experience with SUSE or RPM, OBS allowed us to easily create the needed packages and to deliver the software to our partners. Convinced of the benefits of OBS we want to exploit it more. Following the advice from adrianS_ in #opensuse-buildservice here I ask for a dedicated space that could be recognized as connected to us, ideally with arces.unibo.it in the name. Here[3] you can see the results of my attempts made with my account. For a confirmation of the officiality* of my request you can contact Carlo Caini[4], Associate Professor at ARCES, who directed the development of Virtualbricks the last years. A few words about Virtualbricks and how it is exploited by ARCES. Virtualbricks is a frontend for the management of Qemu Virtual Machines (VMs) and VDE virtualized network devices (switches, channel emulators, etc.). Although it can be used to manage isolated VMs, its peculiar aim is to design and manage testbeds consisting of many VMs interconnected by VDE elements. In other words, it allows to extend the concept of VM to testbeds, which thanks to Virtualbricks can become entirely software-defined. Among the wide variety of possible applications, we have academic research and teaching on computer networks. In particular, we would like to use this space as main hub to distribute our software to the students of the course Protocols and Architectures for Space Networks, master degrees in TLC and Computer Engineering of the University of Bologna, as well as to our research partners, including some European space agencies (ESA, DLR). Thank you for taking this request in account. Marco * Although this request received the consensus of the Director of ARCES, this space will not be recognized as *official* by the University of Bologna i.e. it will not receive any direct support from University of Bologna outside our own effort to maintain it. [1] http://www.arces.unibo.it/en [2] https://github.com/virtualsquare/virtualbricks [3] https://build.opensuse.org/project/show/home:marcogiusti [4] https://www.unibo.it/sitoweb/carlo.caini/en -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1062260] New: Repository medical gone ... where are the packages?
by bugzilla_noreply＠novell.com 26 Sep '22

26 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1062260 Bug ID: 1062260 Summary: Repository medical gone ... where are the packages? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- I'd like to know where the packages of the former repository medical are located? I'm missing the packages aeskulap, xmedcon, ... -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1137381] New: A package name passed to the lang_package macro with the -n option is not included in the summary and description
by bugzilla_noreply＠novell.com 26 Sep '22

26 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137381 Bug ID: 1137381 Summary: A package name passed to the lang_package macro with the -n option is not included in the summary and description 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: ralf.habacker(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- See implementation for macro lang_package at https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0:Update/rpm/… for details -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1093827] New: imagewriter fails with dbus error
by bugzilla_noreply＠novell.com 24 Sep '22

24 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1093827 Bug ID: 1093827 Summary: imagewriter fails with dbus error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hacking(a)mail.quatrox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SUSE Studio Image Writer (imagewriter) does not work for me (in Tumbleweed). The GUI opens and I select the image and device and click write. Then it asks to umount the disk (if it is already mounted). The partitions are now unmounted. It now asks me to confirm to overwrite the content of the device, and I click OK. Now nothing is happening for maybe 30 seconds. Then a dialog window appears with the following text: DBUS error (sdc): Did not receive reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. The dialog only gives me the option to accept this by pressing OK. Then a new dialog appears with the following text: Couldn't open /dev/sdc: Resource temporarily unavailable Again, I have to press OK. -- You are receiving this mail because: You are on the CC list for the bug.

2 1