September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1179492] New: Test grub booting using pe/coff boot entry to support shim and MOK
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1179492 Bug ID: 1179492 Summary: Test grub booting using pe/coff boot entry to support shim and MOK Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: mchang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To support shim lock protocol and use MOK (Machine Owner Key), grub has to load and boot the kernel on it's own without resorting to firmware protocols, namely UEFI LoadImage and StartImage protocols, which would only know about keys in db and dbx and thus would reject image with signature of MOK. To finalize UEFI Secure Boot to fully utilize the capability of shim, the grub package with needed implementation to achieve that is available here. https://build.opensuse.org/package/show/home:michael-chang:arm64-linuxefi/g… In a nut shell, it will call out shim_lock protocol to verify the image, and then jump directly to the PE/COFF entry to boot the image if preceding verification goes successfully. This ticket is opened to track any issue in grub with respect to needed change to adopt shim and MOK on aarch64. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1201529] New: VUL-0: CVE-2022-32323: autotrace: Heap overflow in AutoTrace v0.40.0
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1201529 Bug ID: 1201529 Summary: VUL-0: CVE-2022-32323: autotrace: Heap overflow in AutoTrace v0.40.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/337313/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: sbrabec(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2022-32323 AutoTrace v0.40.0 was discovered to contain a heap overflow via the ReadImage function at input-bmp.c:660. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32323 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32323 https://github.com/autotrace/autotrace/commit/2b44c173027736c64b3f379bd154c… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1202199] New: Gnome Files (Nautilus) format on USB key does nothing
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202199 Bug ID: 1202199 Summary: Gnome Files (Nautilus) format on USB key does nothing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: c.j(a)tuta.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The problem: 1. Insert a USB key (fat 32). 2. It appears in the left panel in nautilus. 3. In the right click menu on the USB key, click "Format..." 4. Nothing happens. I have tried: - copying/deleting files on the USB key (it works fine) - formatting the USB key with Gnome Disks (it works fine). Thanks for fixing this. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1203655] New: Libroffice 7.4 app windows don't open after starting them the first time (on KDE).
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203655 Bug ID: 1203655 Summary: Libroffice 7.4 app windows don't open after starting them the first time (on KDE). Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: c.j(a)tuta.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting Writer, Calc, etc... the first time after install works. But after the first time, they never open again (the app appears in the task bar, but the windows never appear. Rebooting doesn't help). The only way to start the apps is using the "Libreoffice Start Center". (starting writer, calc, etc... directly doesn't work). Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1203646] New: cinnamon-settings network won't open
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203646 Bug ID: 1203646 Summary: cinnamon-settings network won't open Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: aravind96mufc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using Cinnamon DE with Tumbleweed. Issue cinnamon-settings network crashes with a segfault when launched. Steps to reproduce Write "cinnamon-settings network" in a terminal and run. Expected behaviour Networking settings should open. The same bug is reported and resolved in cinnamon github. But it is not updated in Tumbleweed repos. Kindly do this ASAP! https://github.com/linuxmint/cinnamon/issues/10616 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1188363] New: windows:mingw:win{32|64}/mingw{32|64}-python3 missing
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188363 Bug ID: 1188363 Summary: windows:mingw:win{32|64}/mingw{32|64}-python3 missing Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- It would be nice to have a mingw build for Python3 that can be used by mingwxx-gdb and other packages wanting Python3 support. There could be two sources for such a package: 1. https://build.opensuse.org/package/show/home%3Ajayvdb%3Awine-python3%3Apy37… 2. https://github.com/python-cmake-buildsystem/python-cmake-buildsystem The first one uses a custom python build system that is native to the obs project and looks like it would be a lot of work to understand and maintain. Since the build system of the second proposal is based on a known build system (cmake) and it is managed on github, it is suspected that maintenance will be easier here, but may still need adjustments to add mingw based cross-compile functionality and package that. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1202930] New: After install did not boot in graphic mode at Thinkpad T60 with Ati X1300. Need to install xf86-video-ati
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202930 Bug ID: 1202930 Summary: After install did not boot in graphic mode at Thinkpad T60 with Ati X1300. Need to install xf86-video-ati Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: virex(a)mail.ru QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After install did not boot in graphic mode at Thinkpad T60 with Ati X1300. Need to install xf86-video-ati in text mode and reboot to work fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1202821] New: Containers lose permission to /dev/pts after some time
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202821 Bug ID: 1202821 Summary: Containers lose permission to /dev/pts after some time Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On openqaworker1, there are four (pretty much identical) containers set up as services which run openQA tests. After some uptime (~1 day?), xterm fails to start due to permission issues. When it happens, those issues can be triggered manually by executing e.g. su -P. After restarting a container, the permission issues disappear for a while. Sometimes a container has a different issue regarding cgroups, where it looks like the assigned cgroup somehow disappeared. Here's some example output showing the symptoms. containers 101 and 104 were recently restarted and work fine. openqaworker1:~ # podman exec -i openqaworker1_container_101 su -P openqaworker1_container:/ # exit openqaworker1:~ # podman exec -i openqaworker1_container_104 su -P openqaworker1_container:/ # exit openqaworker1:~ # podman exec -i openqaworker1_container_102 su -P su: failed to create pseudo-terminal: Operation not permitted openqaworker1:~ # podman exec -i openqaworker1_container_103 su -P Error: exec failed: unable to start container process: error adding pid 10265 to cgroups: failed to write 10265: openat2 /sys/fs/cgroup/unified/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope/cgroup.procs: no such file or directory: OCI runtime attempted to invoke a command that was not found I didn't know where to begin looking, so I started at the bottom and used systemtap to trace where openat gets its error code from. I traced the permission issue down to the devices cgroup (v1). Some information about the relevant cgroups: container 101 (restarted, works): openqaworker1:~ # podman inspect openqaworker1_container_101 | grep CgroupPath "CgroupPath": "/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope" openqaworker1:~ # cat /sys/fs/cgroup/devices/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope/devices.list c 10:200 rwm c 5:2 rwm c 5:0 rwm c 1:9 rwm c 1:8 rwm c 1:7 rwm c 1:5 rwm c 1:3 rwm b *:* m c *:* m c 136:* rwm openqaworker1:~ # podman inspect openqaworker1_container_101 | grep -i pid "Pid": 9426, "ConmonPid": 9413, "ConmonPidFile": "/var/run/containers/storage/btrfs-containers/955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812/userdata/conmon.pid", "PidFile": "", "PidMode": "private", "PidsLimit": 2048, openqaworker1:~ # cat /proc/9426/cgroup 13:blkio:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 12:perf_event:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 11:devices:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 10:pids:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 9:memory:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 8:rdma:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 7:misc:/ 6:cpuset:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 5:net_cls,net_prio:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 4:freezer:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 3:cpu,cpuacct:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 2:hugetlb:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 1:name=systemd:/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope 0::/machine.slice/libpod-955b615b984df586c92fdc7177ab4a8338bdbad109c3b9fc151ec90e7f420812.scope container 102 (permission issue, device entries missing): openqaworker1:~ # podman inspect openqaworker1_container_102 | grep CgroupPath "CgroupPath": "/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope" openqaworker1:~ # cat /sys/fs/cgroup/devices/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope/devices.list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 10:200 rwm openqaworker1:~ # cat /proc/17525/cgroup 13:blkio:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 12:perf_event:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 11:devices:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 10:pids:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 9:memory:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 8:rdma:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 7:misc:/ 6:cpuset:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 5:net_cls,net_prio:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 4:freezer:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 3:cpu,cpuacct:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 2:hugetlb:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 1:name=systemd:/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope 0::/machine.slice/libpod-bb7f7bed785fed4e77244d316cea6ee21ba9e6a26b609f02c894430f72beb3eb.scope container 103 (cgroup missing?): openqaworker1:~ # podman inspect openqaworker1_container_103 | grep -i pid "Pid": 18167, "ConmonPid": 18154, "ConmonPidFile": "/var/run/containers/storage/btrfs-containers/6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0/userdata/conmon.pid", "PidFile": "", "PidMode": "private", "PidsLimit": 2048, openqaworker1:~ # cat /proc/18167/cgroup 13:blkio:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 12:perf_event:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 11:devices:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 10:pids:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 9:memory:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 8:rdma:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 7:misc:/ 6:cpuset:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 5:net_cls,net_prio:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 4:freezer:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 3:cpu,cpuacct:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 2:hugetlb:/machine.slice/libpod-6c5af02df66206caa2b364013a6ef4f8a6add7206beed39d7a2d85bfd0bfc1c0.scope 1:name=systemd:/system.slice/container-openqaworker1_container_103.service 0::/system.slice/container-openqaworker1_container_103.service It's visible that in the case of container 102, the device cgroup entries "b *:* m" and "c *:* m" got removed somehow and for container 103, the cgroup changed completely (system.slice/*.service instead of machine.slice/libpod-*). bug 1178775 sounds similar. I guess systemd is somehow interfering with podman? -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1191084] New: ocfs2-tools: finish UsrMerge, install to /usr
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1191084 Bug ID: 1191084 Summary: ocfs2-tools: finish UsrMerge, install to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: renzhengeek(a)gmail.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ghe(a)suse.com Blocks: 1191054 Found By: --- Blocker: --- Following up on the discussion on the Factory list https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… All packages installing files into /bin, /sbin, /lib and /lib64 should change the location to the counterpart in /usr instead. Please consider doing that for ocfs2-tools. If ocfs2-tools still needs to build for released distros you may keep the legacy locations within a "%if %suse_version < 1550" block of course. If you do that, please do *NOT* install symlinks from/to /usr as it was done with some packages in the past. Move the files in question instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1129466] New: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129466 Bug ID: 1129466 Summary: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fwdupd 1.2.3-2.1 cannot update the BIOS on my laptop because of this error: $fwupdmgr get-devices ... 20MBCTO1WW System Firmware DeviceId: 65b6a9dc7b7df18bdff003584b51bf21373e3aa6 Guid: 1e1fe415-74e8-49e1-9508-106b3d13d50d Guid: 230c8b18-8d9b-53ec-838b-6cfc0383493a Guid: 171800c9-1a51-5fd9-a32b-7b3999cb1c4e Plugin: uefi Flags: internal|require-ac|supported|registered|needs-reboot Version: 0.1.18 VersionLowest: 0.1.0 Icon: computer Created: 2019-03-15 UpdateError: /usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found Apparently, if Secure Boot is enabled (my case and I believe TW default on UEFI installs), it looks for /usr/lib/fwupd/efi/fwupdx64.efi.signed. This file is missing but it turns out that /usr/lib/fwupd/efi/fwupdx64.efi is present AND signed: $pesign -S -i /usr/lib/fwupd/efi/fwupdx64.efi --------------------------------------------- certificate address is 0x7f0e55679f78 Content was not encrypted. Content is detached; signature cannot be verified. The signer's common name is openSUSE Secure Boot Signkey The signer's email address is build(a)opensuse.org Signing time: Tue Mar 05, 2019 There were certs or crls included. --------------------------------------------- So the fix is simply so make a symlink and restart fwupd so it sees the change: $ln -s /usr/lib/fwupd/fwupdx64.efi /usr/lib/fwupd/fwupdx64.efi.signed $systemctl restart fwupd Then the error goes away in 'fwupdmgr get-devices' and you can supposedly update with 'fwupdmgr update' (didn't try it at updating the BIOS is rather scary and I do not absolutely need this update currently). So I think the package should be updated to make the symlink (or rename the file if keeping fwupdx64.efi is unecessary). -- You are receiving this mail because: You are on the CC list for the bug.

2 19