December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234134] AUDIT-0: timekpr-next: review of new D-Bus service com.timekpr.server, new polkit action com.ubuntu.timekpr.pkexec
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234134 https://bugzilla.suse.com/show_bug.cgi?id=1234134#c1 Wolfgang Frisch <wolfgang.frisch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |wolfgang.frisch(a)suse.com CC| |wolfgang.frisch(a)suse.com Status|NEW |CONFIRMED --- Comment #1 from Wolfgang Frisch <wolfgang.frisch(a)suse.com> --- Thanks for opening this bug report. I will work on this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234134] New: AUDIT-0: timekpr-next: review of new D-Bus service com.timekpr.server, new polkit action com.ubuntu.timekpr.pkexec
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234134 Bug ID: 1234134 Summary: AUDIT-0: timekpr-next: review of new D-Bus service com.timekpr.server, new polkit action com.ubuntu.timekpr.pkexec 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: svalx78(a)gmail.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For package found in OBS in X11:Utilities:timekpr-next I would like a whitelisting for the following rpmlint errors: timekpr-next.noarch: E: polkit-untracked-privilege (Badness: 10) com.ubuntu.timekpr.pkexec (auth_admin:auth_admin:auth_admin) The polkit action is not listed in the polkit-default-privs profiles which makes it harder for admins to find. Furthermore improper polkit authorization checks can easily introduce security issues. timekpr-next.noarch: E: dbus-file-unauthorized (Badness: 10) /usr/share/dbus-1/system.d/timekpr.conf (sha256 file digest default filter:499245aea51f15a98d88a81e0352b9f3c7a1acad3abc53b5ca1ec5dd10e8441a shell filter:670fbbd637a7db138caded139420cb5bc41f24b4a3a1106cde4fb2f489f71ffb xml filter:37117f57a599e1d0b8f565e493b6dc1c152683ea6d9fa8183e7f592143713934) Packaging D-Bus services requires a review and whitelisting by the SUSE security team. Package can be found at https://build.opensuse.org/package/show/X11:Utilities/timekpr-next Sources at https://launchpad.net/timekpr-next I am plan to submit this package to Factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225574] New: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225574 Bug ID: 1225574 Summary: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp 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: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- apache2-mod_mono, by default, creates a socket `/tmp/mod_mono_server_global`, allowing unprivileged users to break the module by creating an identically named file in that location. However a) this behavior is documented b) it is mitigated by a systemd hardening in the apache2 package: > [Unit] > Description=The Apache Webserver > After=network.target nss-lookup.target time-sync.target remote-fs.target > Before=getty(a)tty1.service plymouth-quit.service xdm.service > PartOf=apache2.target > [Service] > Type=notify > PrivateTmp=true -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1193250] [META] Fully switch TW to DRM graphics drivers and disable fbdev drivers
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1193250 Jeffrey Cheung <jcheung(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227378] New: /usr/bin/idle* don't have executable bits
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1227378 Bug ID: 1227378 Summary: /usr/bin/idle* don't have executable bits 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: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- tumbleweed-pkg~$ l /usr/bin/*idle* -rw-r--r--. 1 root root 94 čen 25 23:57 /usr/bin/idle3.11 -rw-r--r--. 1 root root 94 čen 30 21:20 /usr/bin/idle3.13 tumbleweed-pkg~$ -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1233590] New: GCC14 C++ CTAD failure due to ambiguous overload
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233590 Bug ID: 1233590 Summary: GCC14 C++ CTAD failure due to ambiguous overload Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: SLES 15 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: pafee(a)tycoint.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878657 --> https://bugzilla.suse.com/attachment.cgi?id=878657&action=edit Illustration of compilation failure on Leap While using a C++ compile time fixed_string library, I encountered an issue with Leap's version of GCC 14. I tried a number of combinations: * GCC-13, C++20: Pass * GCC-13, C++23: Pass * GCC-14, C++20: Pass * GCC-14, C++23: Fail Testing on Tumbleweed all combinations passed. Distro compiler versions reported by "g++-14 -v" Leap 15.6: gcc version 14.2.0 (SUSE Linux) Tumbleweed: gcc version 14.2.1 20241007 [revision 4af44f2cf7d281f3e4f3957efce10e8b2ccb2ad3] (SUSE Linux) I've stripped down the code in question to produce a minimal reproducible example (see attachment). Since the code works with GCC 14.2.1 on Tumbleweed, is the Leap package lacking upstream updates? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1234053] Podman cannot create container in network
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234053 https://bugzilla.suse.com/show_bug.cgi?id=1234053#c6 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |containers-bugowner(a)suse.de Assignee|containers-bugowner(a)suse.de |alexandre.vicenzi(a)suse.com --- Comment #6 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- The output of lsmod and nft list looks odd indeed. I'll try to reproduce and debug this under WSL. The only workaround, for now, is to roll back to an earlier release of netavark, e.g. 1.13.0-1.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233958] New: System lockup possibly related to USB device
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233958 Bug ID: 1233958 Summary: System lockup possibly related to USB device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Observed running TW20241124, Kernel 6.11.8-1-default Yesterday, on my Laptop, my system freezed without it being a kernel crash. I was running Xorg + i3 as usual when out of nowhere while in Firefox: - mouse and keyboard freezed, entirely unresponsive - no ability to switch to a VT - remote login via ssh unresponsive - no kernel crash (nothing in dmesg, no led blinking) The only solution was to hard shutdown the laptop long-pressing its power button. I had never observed something like this, but yesterday I plugged my brand new Pixel 8 Pro with an USB-C cable for the first time (actually using a TB3 cable connected to the TB3 output of my laptop). I plugged it at 17:16 and the system freeze happened around 17:54 (logs below during that tine interval). Maybe these unusual "PME: Spurious native interrupt!" and "attempt power cycle" messages are a hint to this issue ? For reference, I previously used a Pixel 4a for years with the same cable and never had this issue. If this freeze ever happens again I will report it again here. ////////////// Nov 27 17:16:05 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:05 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:05 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:05 p72 kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd Nov 27 17:16:05 p72 kernel: usb 4-1: LPM exit latency is zeroed, disabling LPM. Nov 27 17:16:05 p72 kernel: usb 4-1: New USB device found, idVendor=18d1, idProduct=4eea, bcdDevice= 5.15 Nov 27 17:16:06 p72 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 27 17:16:06 p72 kernel: usb 4-1: Product: Pixel 8 Pro Nov 27 17:16:06 p72 kernel: usb 4-1: Manufacturer: Google Nov 27 17:16:06 p72 kernel: usb 4-1: SerialNumber: 41111FDJG002BN Nov 27 17:16:06 p72 kernel: usb 4-1: Quirk or no altset; falling back to MIDI 1.0 Nov 27 17:16:06 p72 boltd[1930]: probing: started [1000] Nov 27 17:16:06 p72 (udev-worker)[31737]: controlC2: Process '/usr/sbin/alsactl restore 2' failed with exit code 99. Nov 27 17:16:06 p72 systemd[3109]: Reached target Sound Card. Nov 27 17:16:09 p72 kernel: usb 4-1: USB disconnect, device number 2 Nov 27 17:16:09 p72 boltd[1930]: probing: timeout, done: [2974775] (2000000) Nov 27 17:16:09 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:09 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:09 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:19 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:20 p72 kernel: usb 4-1: new SuperSpeed USB device number 4 using xhci_hcd Nov 27 17:16:20 p72 kernel: usb 4-1: LPM exit latency is zeroed, disabling LPM. Nov 27 17:16:20 p72 kernel: usb 4-1: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 5.15 Nov 27 17:16:20 p72 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 27 17:16:20 p72 kernel: usb 4-1: Product: Pixel 8 Pro Nov 27 17:16:20 p72 kernel: usb 4-1: Manufacturer: Google Nov 27 17:16:20 p72 kernel: usb 4-1: SerialNumber: 41111FDJG002BN Nov 27 17:16:20 p72 boltd[1930]: probing: started [1000] Nov 27 17:16:21 p72 kernel: usb 4-1: USB disconnect, device number 4 Nov 27 17:16:22 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:16:23 p72 kernel: usb 4-1: new SuperSpeed USB device number 5 using xhci_hcd Nov 27 17:16:23 p72 kernel: usb 4-1: LPM exit latency is zeroed, disabling LPM. Nov 27 17:16:23 p72 kernel: usb 4-1: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 5.15 Nov 27 17:16:23 p72 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 27 17:16:23 p72 kernel: usb 4-1: Product: Pixel 8 Pro Nov 27 17:16:23 p72 kernel: usb 4-1: Manufacturer: Google Nov 27 17:16:23 p72 kernel: usb 4-1: SerialNumber: 41111FDJG002BN Nov 27 17:16:25 p72 boltd[1930]: probing: timeout, done: [2177366] (2000000) Nov 27 17:17:23 p72 systemd[1]: Started Daily Cleanup of Snapper Snapshots. Nov 27 17:17:23 p72 systemd[1]: Starting DBus interface for snapper... Nov 27 17:17:23 p72 systemd[1]: Started DBus interface for snapper. Nov 27 17:17:23 p72 systemd-helper[32109]: Running cleanup for 'root'. Nov 27 17:17:23 p72 systemd-helper[32109]: Running number cleanup for 'root'. Nov 27 17:17:23 p72 systemd-helper[32109]: quota not working (qgroup not set) Nov 27 17:17:23 p72 systemd-helper[32109]: Running timeline cleanup for 'root'. Nov 27 17:17:23 p72 systemd-helper[32109]: Running empty-pre-post cleanup for 'root'. Nov 27 17:17:25 p72 systemd-helper[32109]: Running 'btrfs qgroup clear-stale /.snapshots'. Nov 27 17:17:25 p72 systemd-helper[32109]: 'btrfs qgroup clear-stale /.snapshots' failed. Nov 27 17:17:25 p72 systemd[1]: snapper-cleanup.service: Deactivated successfully. Nov 27 17:18:25 p72 systemd[1]: snapperd.service: Deactivated successfully. Nov 27 17:18:25 p72 systemd[1]: snapperd.service: Consumed 1.192s CPU time. Nov 27 17:48:29 p72 smartd[1805]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 63 to 64 Nov 27 17:48:29 p72 smartd[1805]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 37 to 36 Nov 27 17:54:34 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:54:34 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:54:34 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:54:34 p72 kernel: usb 4-1: USB disconnect, device number 5 Nov 27 17:54:34 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:54:34 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:54:34 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:54:43 p72 kernel: usb usb4-port1: attempt power cycle Nov 27 17:54:47 p72 kernel: pcieport 0000:00:1c.0: PME: Spurious native interrupt! Nov 27 17:54:56 p72 kernel: usb usb4-port1: attempt power cycle -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1233690] Docker containers are not reachable from network after OS update from 20241114 to 20241115
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 Ricardo Branco <rbranco(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbranco(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233381] Tumbleweed won’t recover from sleep. Force shutdown required
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233381 https://bugzilla.suse.com/show_bug.cgi?id=1233381#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(kosimo(a)gmail.com) --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- And, since TW is already moving to 6.12.x, please test with the kernel in OBS Kernel:stable repo. -- You are receiving this mail because: You are on the CC list for the bug.

1 0