January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1214458] New: /usr/bin/xzegrep: line 219: /usr/bin/egrep: Permission denied
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214458 Bug ID: 1214458 Summary: /usr/bin/xzegrep: line 219: /usr/bin/egrep: Permission denied Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Doing a simple xzegrep - # xzegrep 'GET /release/[0-9A-F]+' vhost_access_log ...[snip] /usr/bin/xzegrep: line 219: /usr/bin/egrep: Permission denied See also https://progress.opensuse.org/issues/113108 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216368] New: Thunderbird "Error reading events from display: Connection reset by peer"
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1216368 Bug ID: 1216368 Summary: Thunderbird "Error reading events from display: Connection reset by peer" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, since some time (unfortunately I don't know which snapshot it first occurred with) Thunderbird on Tumbleweed crashes unpredictably with the console message: ``` Gdk-Message: 11:12:36.813: Error reading events from display: Connection reset by peer ``` Sometimes it happens only after Thunderbird is running for some hours after clicking some element in the UI, sometimes by itself shortly after startup. This is on Wayland/Sway with the openSUSEway configuration. Would appreciate any advice. ``` $ grep VERSION_ID /etc/os-release VERSION_ID="20231006" $ zypper se -is thunderbird S | Name | Type | Version | Arch | Repository ---+--------------------+---------+-------------+--------+---------------------- i+ | MozillaThunderbird | package | 115.3.2-1.1 | x86_64 | Main Repository (OSS) ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1212954] New: amdgpu: Monitor displaying wrong resolution
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1212954 Bug ID: 1212954 Summary: amdgpu: Monitor displaying wrong resolution Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: holgi(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867944 --> https://bugzilla.suse.com/attachment.cgi?id=867944&action=edit IMG_20230703_164538751_HDR.jpg Having a 4K monitor (SAMSUNG LU28R55) attached to the docking station of my ThinkPad via HDMI I can easily 1:1 mirror the screen output of the laptop and the monitor with openSUSE Leap 15.4. Doing the same with openSUSE Leap 15.5 will result in monitor displaying a resolution 1980x2160 instead of the set 1980x1080. Using a 4x different screen (Philips) is working fine. Photo of monitor attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1218864] New: grub2: error messages: 'not a correct XFS inode' shown many many times
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218864 Bug ID: 1218864 Summary: grub2: error messages: 'not a correct XFS inode' shown many many times Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Do a fresh tumbleweed installation and select xfs as root filesystem. The installation completes successfully and the system reboot. After login run: update-bootloader --reinit and reboot. The system still reboots fine. Login and run again: update-bootloader --reinit Now after reboot before the grub menu appears you can see the following line printer many times: error: ../../grub-core/fs/xfs.c:541:not a correct XFS inode. This goes on for about a minute and then the boot porcess continues normally. Login and run again: update-bootloader --reinit After reboot before the grub menu appears you will see the previous error line printer many times but this time for about a couple of minutes and then the boot process continues normally. Running again: update-bootloader --reinit does not seem to extend the delay during which the error message is printed. I found this fedora bug report that describes the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=2254370 and on comment 48 it is said that the following commit: https://github.com/rhboot/grub2/commit/1955d781ba20c1952adc820f3e587878b4f5… of grub2 1.12 is causing the issue. To test I have rebuild grub2 removing such commit from the source, I have installed the modified version of grub2 and run again: update-bootloader --reinit Now the system boots again without showing the error. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1218754] New: VUL-0: CVE-2023-52339: In libebml before 1.4.5, an integer overflow in MemIOCallback.cpp can occur when reading or writing. It may result in buffer overflows.
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218754 Bug ID: 1218754 Summary: VUL-0: CVE-2023-52339: In libebml before 1.4.5, an integer overflow in MemIOCallback.cpp can occur when reading or writing. It may result in buffer overflows. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/390983/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: rpm(a)fthiessen.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: stoyan.manolov(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- In libebml before 1.4.5, an integer overflow in MemIOCallback.cpp can occur when reading or writing. It may result in buffer overflows. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52339 https://www.cve.org/CVERecord?id=CVE-2023-52339 https://github.com/Matroska-Org/libebml/blob/v1.x/NEWS.md https://github.com/Matroska-Org/libebml/compare/release-1.4.4...release-1.4… https://github.com/Matroska-Org/libebml/issues/147 https://github.com/Matroska-Org/libebml/pull/148 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1218618] New: systemctl is-system-running - degraded after update
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218618 Bug ID: 1218618 Summary: systemctl is-system-running - degraded after update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: michael.trapp(a)sap.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, with the last update on Tumbleweed we've noticed the following issue after rebooting the server # systemctl is-system-running degraded # systemctl ● systemd-vconsole-setup.service loaded failed failed Virtual Console Setup # systemctl status systemd-vconsole-setup.service × systemd-vconsole-setup.service - Virtual Console Setup Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static) Active: failed (Result: exit-code) since Mon 2024-01-08 12:02:41 CET; 5min ago Duration: 9.112s Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Process: 827 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=1/FAILURE) Main PID: 827 (code=exited, status=1/FAILURE) CPU: 10ms Jan 08 12:02:41 tumbleweed systemd[1]: Starting Virtual Console Setup... Jan 08 12:02:41 tumbleweed systemd-vconsole-setup[827]: No usable source console found: Device or resource busy Jan 08 12:02:41 tumbleweed systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Jan 08 12:02:41 tumbleweed systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. Jan 08 12:02:41 tumbleweed systemd[1]: Failed to start Virtual Console Setup. a journalctl for the service did not provide useful details but a strace in the service file showed 824 access("/dev/vcs2", F_OK) = -1 ENOENT (No such file or directory) 824 access("/dev/vcs3", F_OK) = -1 ENOENT (No such file or directory) ... The service can be started manually because from the active session we can see # ls -l /dev/vcs* crw-rw---- 1 root tty 7, 0 Jan 8 12:18 /dev/vcs crw-rw---- 1 root tty 7, 1 Jan 8 12:18 /dev/vcs1 crw-rw---- 1 root tty 7, 2 Jan 8 12:18 /dev/vcs2 crw-rw---- 1 root tty 7, 3 Jan 8 12:18 /dev/vcs3 ... # systemctl list-dependencies systemd-vconsole-setup.service systemd-vconsole-setup.service ● ├─kbdsettings.service ● └─system.slice Would you please check and fix the issue. Kind regards Michael -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1219136] New: Missing built-in mic support for Thinkpad P14s AMD Gen4
by bugzilla_noreply＠suse.com 15 Feb '24

15 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219136 Bug ID: 1219136 Summary: Missing built-in mic support for Thinkpad P14s AMD Gen4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The built-in mic on Lenovo Thinkpad P14s AMD Gen4 isn't supported by SLE15-SP5 kernel as of now (while SP6 already supports it). It's acp63. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1218052] New: longterm 6.1 update tracker for Factory
by bugzilla_noreply＠suse.com 15 Feb '24

15 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218052 Bug ID: 1218052 Summary: longterm 6.1 update tracker for Factory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: rfrohl(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Tracker for 6.1 longterm kernel updates. Mostly for testing and separating the process. I do not expect that 6.1 will ever reach Factory(with 6.6 on the horizon) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217786] New: Ob SLowroll picom causes 100% load of the Xorg.bin server using Nvidia GL05
by bugzilla_noreply＠suse.com 14 Feb '24

14 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1217786 Bug ID: 1217786 Summary: Ob SLowroll picom causes 100% load of the Xorg.bin server using Nvidia GL05 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: werner(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting on the command line or via lxsession (or any other session manager) the picom command shows a) a blacked root screen as well as b) 100% load of the Xorg.bin server on one CPU and c) endless scrolling error messages: [ 12/04/23 17:36:58.847 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001181 [ 12/04/23 17:36:58.849 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001272 [ 12/04/23 17:36:58.850 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001363 [ 12/04/23 17:36:58.851 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001454 [ 12/04/23 17:36:58.853 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001545 [ 12/04/23 17:36:58.854 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001636 [ 12/04/23 17:36:58.855 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001727 [ 12/04/23 17:36:58.857 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001818 [ 12/04/23 17:36:58.858 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1001909 [ 12/04/23 17:36:58.859 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002000 [ 12/04/23 17:36:58.861 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002091 [ 12/04/23 17:36:58.862 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002182 [ 12/04/23 17:36:58.863 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002273 [ 12/04/23 17:36:58.865 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002364 [ 12/04/23 17:36:58.866 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002455 [ 12/04/23 17:36:58.868 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002546 [ 12/04/23 17:36:58.869 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002637 [ 12/04/23 17:36:58.871 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002728 [ 12/04/23 17:36:58.872 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002819 [ 12/04/23 17:36:58.874 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1002910 [ 12/04/23 17:36:58.875 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003001 [ 12/04/23 17:36:58.877 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003092 [ 12/04/23 17:36:58.878 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003183 [ 12/04/23 17:36:58.880 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003274 [ 12/04/23 17:36:58.881 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003365 [ 12/04/23 17:36:58.883 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003456 [ 12/04/23 17:36:58.884 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003547 [ 12/04/23 17:36:58.886 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003638 [ 12/04/23 17:36:58.887 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003729 [ 12/04/23 17:36:58.889 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003820 [ 12/04/23 17:36:58.890 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1003911 [ 12/04/23 17:36:58.892 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1004002 [ 12/04/23 17:36:58.893 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1004093 [ 12/04/23 17:36:58.895 x_log_error WARN ] X error 143 RENDER_PICTURE request 139 minor 5 serial 1004190 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1217402] New: AUDIT-FIND: Updating server configuration as root while parsing untrusted data
by bugzilla_noreply＠suse.com 14 Feb '24

14 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1217402 Bug ID: 1217402 Summary: AUDIT-FIND: Updating server configuration as root while parsing untrusted data Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fstrba(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the new tomcat10 packages I stumbled across: 687 %post webapps 688 %{serverxmltool} add-context.xslt docBase=%{tomcatappdir}/ROOT path=/ 689 %{serverxmltool} add-context.xslt docBase=%{tomcatappdir}/sample path=/sample 690 %{serverxmltool} add-context.xslt docBase=%{tomcatappdir}/examples path=/examples This translates to e.g. /usr/libexec/tomcat/serverxml-tool.sh add-context.xslt docBase=/usr/share/tomcat/tomcat-webapps/ROOT path=/ serverxml-tool.sh invokes java with serverxmltool.jar to update /etc/tomcat/server.xml. All of this runs as root and parses XML. I didn't find a security issue with this (but also just spend a couple of minutes on this), but it's a bigger risk than necessary. Apart from overwriting the config file root privileges are not needed. Especially the java call should not run as root, xml operations are notoriously dangerous. runuser is a good tool for this. You can do the XML parsing as the tomcat user and then if necessary overwrite the tomcat config with an update file. -- You are receiving this mail because: You are on the CC list for the bug.

1 4