May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223260] New: SELinux denies pcp
by bugzilla_noreply＠suse.com 22 Aug '24

22 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1223260 Bug ID: 1223260 Summary: SELinux denies pcp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874416 --> https://bugzilla.suse.com/attachment.cgi?id=874416&action=edit ausearch -ts boot -m avc On MicroOS starting pmlogger with SELinux in enforcing mode fails with several SELinux related denials > Apr 22 13:14:01 microos systemd[1]: Starting Performance Metrics Archive Logger... > Apr 22 13:14:01 microos rc[2682]: /etc/pcp/pmlogger/rc: line 153: /var/lib/pcp/tmp/pmlogger_rc.d9N3i7aLW/tmp: Permission denied > Apr 22 13:14:01 microos rc[2750]: /etc/pcp/pmlogger/rc: line 92: /var/lib/pcp/tmp/pmlogger_rc_start.7vdZJLmGN/pmcheck.out: Permission denied > Apr 22 13:14:01 microos systemd[1]: pmlogger.service: Main process exited, code=exited, status=1/FAILURE > Apr 22 13:14:01 microos systemd[1]: pmlogger.service: Failed with result 'exit-code'. > Apr 22 13:14:01 microos systemd[1]: Failed to start Performance Metrics Archive Logger. > Apr 22 13:14:01 microos systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 1. > Apr 22 13:14:01 microos systemd[1]: Stopped Performance Metrics Archive Logger. > Apr 22 13:14:01 microos systemd[1]: Starting Performance Metrics Archive Logger... > Apr 22 13:14:01 microos rc[2958]: /etc/pcp/pmlogger/rc: line 153: /var/lib/pcp/tmp/pmlogger_rc.yWYJd9JBe/tmp: Permission denied > Apr 22 13:14:01 microos rc[2991]: /etc/pcp/pmlogger/rc: line 92: /var/lib/pcp/tmp/pmlogger_rc_start.OcmNVcLdA/pmcheck.out: Permission denied > Apr 22 13:14:01 microos systemd[1]: pmlogger.service: Main process exited, code=exited, status=1/FAILURE > Apr 22 13:14:01 microos systemd[1]: pmlogger.service: Failed with result 'exit-code'. > Apr 22 13:14:01 microos systemd[1]: Failed to start Performance Metrics Archive Logger. > ... I'm attaching the output of ausearch -ts boot -m avc, failures are coming from the rc program and related to tmp and pmcheck.out. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219527] New: abcde breaks on non-octal track numbers
by bugzilla_noreply＠suse.com 22 Aug '24

22 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1219527 Bug ID: 1219527 Summary: abcde breaks on non-octal track numbers Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: geoff(a)cs.hmc.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872425 --> https://bugzilla.suse.com/attachment.cgi?id=872425&action=edit Patch to /usr/bin/abcde abcde pads track numbers with a leading zero but later does some bash arithmetic on the track number. That breaks for track numbers 8 and 9, because 09 isn't an octal number. Reproduce by inserting an 8+ track CD and running "abcde -T 1 8-8". The attached patch will correct the problem for any CD having 99 or fewer tracks. (As far as I know, 99 is the track limit for CDs, though I definitely could be wrong.) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216895] New: VUL-0: CVE-2023-47272: Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (used for attachment preview or download).
by bugzilla_noreply＠suse.com 21 Aug '24

21 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216895 Bug ID: 1216895 Summary: VUL-0: CVE-2023-47272: Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (used for attachment preview or download). Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/384151/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: aj(a)ajaissle.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: --- Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (used for attachment preview or download). References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-47272 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221504] New: bluetooth errors on every kernel starting
by bugzilla_noreply＠suse.com 20 Aug '24

20 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1221504 Bug ID: 1221504 Summary: bluetooth errors on every kernel starting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Dell Precision 7530 with Intel Wireless-AC 9260 Bluetooth Adapter and kernel 6.4.0-150600.9.2. Errors constantly appear when booting the system, but bluetooth works with my headphones, although there are some audio artifacts at the beginning when playing sound. Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth daemon 5.71 Mär 16 17:49:38 precision bluetoothd[1073]: Starting SDP server Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support csip plugin Mär 16 17:49:38 precision bluetoothd[1073]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support micp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support vcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support mcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bass plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bap plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support admin plugin Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth management interface 1.22 initialized Mär 16 17:49:38 precision dbus-daemon[1074]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=1073 comm="/usr/lib/bluetooth/bluetoothd ") Mär 16 17:49:38 precision bluetoothd[1073]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Battery Provider Manager created Mär 16 17:49:38 precision bluetoothd[1073]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution Mär 16 17:49:38 precision bluetoothd[1073]: Failed to clear UUIDs: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Too small Add Device complete event Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision (smartd)[1105]: smartd.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts Looks like this is the error https://bugzilla.kernel.org/show_bug.cgi?id=217651 Here's a fix https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi… -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1220569] New: No mouse pointer in noVNC when installing latest Tumbleweed using BVCP
by bugzilla_noreply＠suse.com 20 Aug '24

20 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1220569 Bug ID: 1220569 Summary: No mouse pointer in noVNC when installing latest Tumbleweed using BVCP 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: roger.whittaker(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I have been using an unusual but rather nice virtualisation setup BVCP (https://bhyve.npulse.net/) which runs on FreeBSD and displays VMs using noVNC ( https://novnc.com/info.html) When installing the latest Tumbleweed the mouse pointer in the noVNC window does not move, nor does it move in a completed install. This problem does not exist with for example Leap 15.5. I do not see this with virt-install / virt-viewer on Linux, so this seems to a specific problem with Tumbleweed when using noVNC. I understand that this is an unusual use case, but maybe something has changed that might be a problem in other circumstances as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 99

[Bug 1222972] New: Update nvidia driver to version 550.76
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222972 Bug ID: 1222972 Summary: Update nvidia driver to version 550.76 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to version 550.76 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1220970] New: GCC 14: python package fails
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1220970 Bug ID: 1220970 Summary: GCC 14: python package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mcepl(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building python with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): Python-2.7.18/Modules/_tkinter.c: In function ‘AsObj’: Python-2.7.18/Modules/_tkinter.c:1178:38: error: passing argument 1 of ‘Tcl_NewUnicodeObj’ from incompatible pointer type [-Wincompatible-pointer-types] 1178 | return Tcl_NewUnicodeObj(inbuf, size); | ^~~~~ | | | Py_UNICODE * {aka int *} In file included from /usr/include/tcl.h:2418, from /home/abuild/rpmbuild/BUILD/Python-2.7.18/Modules/_tkinter.c:70: /usr/include/tclDecls.h:1102:62: note: expected ‘const Tcl_UniChar *’ {aka ‘const short unsigned int *’} but argument is of type ‘Py_UNICODE *’ {aka ‘int *’} 1102 | EXTERN Tcl_Obj * Tcl_NewUnicodeObj(const Tcl_UniChar *unicode, | ~~~~~~~~~~~~~~~~~~~^~~~~~~ See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1222314] New: YaST doesn't set zypper locales during installation
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222314 Bug ID: 1222314 Summary: YaST doesn't set zypper locales during installation 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: fvogt(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 874066 --> https://bugzilla.suse.com/attachment.cgi?id=874066&action=edit YaST installation logs I installed YaST with German locale. While the system has the locale configured as expected (e.g. /etc/locale.conf), zypper does not: ~> sudo zypper locales Code | Language | Requested -----+----------+---------- As a result, language specific packages are missing. -- You are receiving this mail because: You are on the CC list for the bug.

1 50

[Bug 1219841] New: dracut: segfault with rd.break option
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1219841 Bug ID: 1219841 Summary: dracut: segfault with rd.break option Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Commit https://github.com/openSUSE/dracut/commit/3950f801e26a3aeb1e3bc91e31c7fd459… fixed a regression with multiple `rd.break=` options set on the kernel command line. But, it detected a call to `strcmp` without checking that the arguments are not NULL first, which causes a segfault when passing the `rd.break` option without value on the kernel command line. > Feb 12 11:37:23 localhost systemd[1]: Starting dracut cmdline hook... > Feb 12 11:37:23 localhost dracut-cmdline[237]: dracut-059+suse.538.ge7a5cff9-1.3 > Feb 12 11:37:23 localhost dracut-cmdline[237]: Using kernel command line parameters: rd.driver.pre=btrfs resume=UUID=de0a0a36-ef3b-4935-aae6-209c689c0dd2 root=UUID=5594bae0-44c9-49e5-b17b-8ef41682899e rootfstype=btrfs rootflags=rw,relatime,discard=async,space_cache=v2,subvolid=266,subvol=/@/.snapshots/1/snapshot,subvol=@/.snapshots/1/snapshot BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=UUID=5594bae0-44c9-49e5-b17b-8ef41682899e console=tty0 console=ttyS0,9600 security=apparmor mitigations=auto rd.break > Feb 12 11:37:23 localhost kernel: dracut-getargs[279]: segfault at 0 ip 00007f88b1c88726 sp 00007ffc3fbefc98 error 4 in libc.so.6[7f88b1b31000+16d000] likely on CPU 0 (core 0, socket 0) > Feb 12 11:37:23 localhost kernel: Code: 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 89 f8 09 f0 c1 e0 14 3d 00 00 00 f8 0f 87 1a 03 00 00 <62> e1 fe 28 6f 07 62 b2 7d 20 26 d0 62 f1 7d 22 74 0e c5 fb 93 c9 > Feb 12 11:37:23 localhost systemd-coredump[280]: Failed to connect to coredump service: No such file or directory > Feb 12 11:37:23 localhost systemd[1]: Finished dracut cmdline hook. > Feb 12 11:37:23 localhost systemd[1]: Starting dracut pre-udev hook... > Feb 12 11:37:23 localhost kernel: dracut-getargs[315]: segfault at 0 ip 00007f2d52753726 sp 00007ffd0a7f8f78 error 4 in libc.so.6[7f2d525fc000+16d000] likely on CPU 1 (core 0, socket 1) However these segfaults are not critical, because it happens on a separate C binary used to parse the kernel command line, so the system boots anyway. Fix to be backported: https://github.com/dracutdevs/dracut/pull/2607/commits/b9d395a373a1da0e869d… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1217083] New: snapshot 20231107 --> 20231108 boot fails
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217083 Bug ID: 1217083 Summary: snapshot 20231107 --> 20231108 boot fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: roeland.jansen(a)sue.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently I updated 23031107 to 20231108 on two laptops running legacy boot. Both hang some time at console plymouth stuff. dracut then comes up with the inability to find /dev/system/root. It ends up in the dracut emergency shell. in the shell, lvm pvscan will report no physical volumes. It also happens on a virtual machine. (also not UEFI). If I try to recover with an usb stick, no partitions are shown. If I show "all", the installed system is being identified als unknown, architecture unknown. (and yes it's a 64 bit TW stick). I could not recover them anymore. Also, on one of the laptops, grub does not show windosws anmore, the other does. I luckily have a snapshot on my work vm so I can revert back. The following packages are updated when this happens. alsa alsa-devel code kernel-firmware-all kernel-firmware-amdgpu kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-atheros kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915 kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform kernel-firmware-prestera kernel-firmware-qcom kernel-firmware-qlogic kernel-firmware-radeon kernel-firmware-realtek kernel-firmware-serial kernel-firmware-sound kernel-firmware-ti kernel-firmware-ueagle kernel-firmware-usb-network libasound2 libatopology2 libbrotli-devel libbrotlicommon1 libbrotlicommon1-x86-64-v3 libbrotlidec1 libbrotlidec1-x86-64-v3 libbrotlienc1 libbrotlienc1-x86-64-v3 libbytesize-lang libbytesize1 libgusb2 libnghttp2-14 libsqlite3-0 libsqlite3-0-x86-64-v3 libsvn_auth_kwallet-1-0 libxxhash0 openSUSE-release openSUSE-release-appliance-custom openSUSE-release-ftp sqlite3-devel sqlite3-tcl subversion subversion-bash-completion subversion-perl sysuser-shadow ucode-amd wmctrl I tried by mounting in rescue, created a new grub.cfg where osprober does not show windows anymore. The interesting part is that dracut -f will as last line shows "adding boot menu entry for UEFI firmware settings" Basically I will end up in reinstalling windows and linux on both laptops. (in legacy boot) If needed, I can install the non-kernel parts and see what package eventualy triggers this. -- You are receiving this mail because: You are on the CC list for the bug.

1 27