November 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222473] New: VUL-0: CVE-2024-22189: dnscrypt-proxy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
by bugzilla_noreply＠suse.com 20 Jan '25

20 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222473 Bug ID: 1222473 Summary: VUL-0: CVE-2024-22189: dnscrypt-proxy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/400376/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: cunix(a)mail.de Reporter: camila.matos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: camila.matos(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1222461 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1222461 +++ quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22189 https://www.cve.org/CVERecord?id=CVE-2024-22189 https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c… https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478 https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme… https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s https://bugzilla.redhat.com/show_bug.cgi?id=2273513 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1228797] New: python3-schema and python3-daemon not available with sle-module-pythons
by bugzilla_noreply＠suse.com 20 Jan '25

20 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228797 Bug ID: 1228797 Summary: python3-schema and python3-daemon not available with sle-module-pythons Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am attempting to build cobbler-tftp here [1]. This is failing due to two dependencies not being enabled for sle-module-pythons. I would desire that sle15allpythons is used so the package builds for both 3.6 and 3.11. Both versions in Leap are available at the moment with 3.6 and are compatible with it. [1]: https://build.opensuse.org/package/show/systemsmanagement:cobbler:release34… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225863] New: Chromium crashes on startup
by bugzilla_noreply＠suse.com 19 Jan '25

19 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1225863 Bug ID: 1225863 Summary: Chromium crashes on startup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dev(a)dominik-schmidt.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After updating openSUSE Tumbleweed the other day Chromium is now crashing for me on startup (i.e. I don't get to see a window at all). My system is completely up to date, I switched all packages from packman to repo-oss. When running Chromium in GDB I can retrieve this backtrace: > 0x000055555e2ec853 in partition_alloc::internal::FreelistCorruptionDetected(unsigned long) () > (gdb) bt > #0 0x000055555e2ec853 in partition_alloc::internal::FreelistCorruptionDetected(unsigned long) () > #1 0x000055555e2fc487 in allocator_shim::internal::PartitionMalloc(allocator_shim::AllocatorDispatch const*, unsigned long, void*) () > #2 0x000055555dc170f2 in base::allocator::dispatcher::internal::DispatcherImpl<base::PoissonAllocationSampler>::AllocFn(allocator_shim::AllocatorDispatch const*, unsigned long, void*) () > #3 0x000055555e2fba1b in malloc () > #4 0x00007ffff36aa75e in strdup () at /lib64/libc.so.6 > #5 0x00007ffff72a7439 in () at /lib64/libfontconfig.so.1 > #6 0x00007ffff72a8f3c in () at /lib64/libfontconfig.so.1 > #7 0x00007ffff72ad2c5 in () at /lib64/libfontconfig.so.1 > #8 0x00007ffff71ce988 in () at /lib64/libexpat.so.1 > #9 0x00007ffff71cb7c4 in () at /lib64/libexpat.so.1 > #10 0x00007ffff71cdc49 in () at /lib64/libexpat.so.1 > #11 0x00007ffff71c2258 in () at /lib64/libexpat.so.1 > #12 0x00007ffff71ca3e5 in XML_ParseBuffer () at /lib64/libexpat.so.1 > #13 0x00007ffff72a97d5 in () at /lib64/libfontconfig.so.1 > #14 0x00007ffff72aa11e in () at /lib64/libfontconfig.so.1 > #15 0x00007ffff72924ef in () at /lib64/libfontconfig.so.1 > #16 0x00007ffff728d5b9 in () at /lib64/libfontconfig.so.1 > #17 0x00007ffff72927d9 in FcInit () at /lib64/libfontconfig.so.1 > #18 0x000055555f0e7a78 in base::NoDestructor<gfx::(anonymous namespace)::GlobalFontConfig>::NoDestructor<>() () > #19 0x000055555f0e7a06 in base::internal::Invoker<base::internal::FunctorTraits<gfx::InitializeGlobalFontConfigAsync()::$_0&&>, base::internal::BindState<false, false, false, gfx::InitializeGlobalFontConfigAsync()::$_0>, void ()>::RunOnce(base::internal::BindStateBase*) () > #20 0x000055555e236f4b in base::TaskAnnotator::RunTaskImpl(base::PendingTask&) () > #21 0x000055555e25aef8 in base::internal::TaskTracker::RunTaskImpl(base::internal::Task&, base::TaskTraits const&, base::internal::TaskSource*, base::internal::SequenceToken const&) () > #22 0x000055555e25afc1 in base::internal::TaskTracker::RunSkipOnShutdown(base::internal::Task&, base::TaskTraits const&, base::internal::TaskSource*, base::internal::SequenceToken const&) () > #23 0x000055555e25abf3 in base::internal::TaskTracker::RunTask(base::internal::Task, base::internal::TaskSource*, base::TaskTraits const&) () > #24 0x000055555e25a717 in base::internal::TaskTracker::RunAndPopNextTask(base::internal::RegisteredTaskSource) () > #25 0x000055555e26d2df in base::internal::WorkerThread::RunWorker() () > #26 0x000055555e26ceaa in base::internal::WorkerThread::RunPooledWorker() () > #27 0x000055555e26cd2a in base::internal::WorkerThread::ThreadMain() () > #28 0x000055555e28a08a in base::(anonymous namespace)::ThreadFunc(void*) () > #29 0x00007ffff3692ba2 in start_thread () at /lib64/libc.so.6 > #30 0x00007ffff371400c in clone3 () at /lib64/libc.so.6 I also tried 125.0.6422.141-1965.1-x86_64 from network:chromium/chromium, but it shows the same behavior. As it looks related to fontconfig, I ran > fc-cache -f -v as user and root with no success either. Happy to provide any additional system information, logs, outputs... Thanks in advance -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1230106] New: screengrab doesn't start anymore
by bugzilla_noreply＠suse.com 19 Jan '25

19 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230106 Bug ID: 1230106 Summary: screengrab doesn't start anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: alex.hucke(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, the screengrab app doesn't start anymore. When you try to start, you get a memory access error. The app version is 2.8.0-1.1 My system: Operating System: openSUSE Tumbleweed-Slowroll 20240803 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.5-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: Micro-Star International Co., Ltd Product Name: MS-7B86 System Version: 4.0 The bug report: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. PID: 3107 (screengrab) UID: 1001 (alex) GID: 1001 (alex) Signal: 11 (SEGV) Timestamp: Tue 2024-09-03 16:24:18 CEST (4min 31s ago) Command Line: /usr/bin/screengrab Executable: /usr/bin/screengrab Control Group: /user.slice/user-1001.slice/user@1001.service/app.slice/app-screengrab@df5e5a43a81244518ad17d9099bcf6f3.service Unit: user(a)1001.service User Unit: app-screengrab(a)df5e5a43a81244518ad17d9099bcf6f3.service Slice: user-1001.slice Owner UID: 1001 (alex) Boot ID: 8997f53b6d024558a446e9e4dc8d36c2 Machine ID: 79d3cf25ebc244a88f56b706ba20347e Hostname: MS-7B86 Storage: /var/lib/systemd/coredump/core.screengrab.1001.8997f53b6d024558a446e9e4dc8d36c2.3107.1725373458000000.zst (present) Size on Disk: 2.6M Message: Process 3107 (screengrab) of user 1001 dumped core. Stack trace of thread 3107: #0 0x0000555de5e0e02d n/a (screengrab + 0x4402d) #1 0x0000555de5de5c7d n/a (screengrab + 0x1bc7d) #2 0x00007fe15682a340 __libc_start_call_main (libc.so.6 + 0x2a340) #3 0x00007fe15682a409 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a409) #4 0x0000555de5de7b15 n/a (screengrab + 0x1db15) Stack trace of thread 3118: #0 0x00007fe156905aff __poll (libc.so.6 + 0x105aff) #1 0x00007fe156fe28aa n/a (libxcb.so.1 + 0xe8aa) #2 0x00007fe156fe441c xcb_wait_for_event (libxcb.so.1 + 0x1041c) #3 0x00007fe15338e110 n/a (libQt6XcbQpa.so.6 + 0x5e110) #4 0x00007fe1572ed0f9 n/a (libQt6Core.so.6 + 0x2ed0f9) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3144: #0 0x00007fe156905aff __poll (libc.so.6 + 0x105aff) #1 0x00007fe15771434f n/a (libglib-2.0.so.0 + 0x5f34f) #2 0x00007fe157714a5c g_main_context_iteration (libglib-2.0.so.0 + 0x5fa5c) #3 0x00007fe157714aa1 n/a (libglib-2.0.so.0 + 0x5faa1) #4 0x00007fe15774132e n/a (libglib-2.0.so.0 + 0x8c32e) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3123: #0 0x00007fe15688f25e __futex_abstimed_wait_common (libc.so.6 + 0x8f25e) #1 0x00007fe156891fa0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91fa0) #2 0x00007fe14891c5a9 n/a (radeonsi_dri.so + 0x11c5a9) #3 0x00007fe1488fc74b n/a (radeonsi_dri.so + 0xfc74b) #4 0x00007fe14891c4e7 n/a (radeonsi_dri.so + 0x11c4e7) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3122: #0 0x00007fe15688f25e __futex_abstimed_wait_common (libc.so.6 + 0x8f25e) #1 0x00007fe156891fa0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91fa0) #2 0x00007fe14891c5a9 n/a (radeonsi_dri.so + 0x11c5a9) #3 0x00007fe1488fc74b n/a (radeonsi_dri.so + 0xfc74b) #4 0x00007fe14891c4e7 n/a (radeonsi_dri.so + 0x11c4e7) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3114: #0 0x00007fe156905aff __poll (libc.so.6 + 0x105aff) #1 0x00007fe15771434f n/a (libglib-2.0.so.0 + 0x5f34f) #2 0x00007fe157714a5c g_main_context_iteration (libglib-2.0.so.0 + 0x5fa5c) #3 0x00007fe1573c1a9c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3c1a9c) #4 0x00007fe15719939b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x19939b) #5 0x00007fe157274a24 _ZN7QThread4execEv (libQt6Core.so.6 + 0x274a24) #6 0x00007fe15817b70a n/a (libQt6DBus.so.6 + 0x3870a) #7 0x00007fe1572ed0f9 n/a (libQt6Core.so.6 + 0x2ed0f9) #8 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #9 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3127: #0 0x00007fe15688f25e __futex_abstimed_wait_common (libc.so.6 + 0x8f25e) #1 0x00007fe156891fa0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91fa0) #2 0x00007fe14891c5a9 n/a (radeonsi_dri.so + 0x11c5a9) #3 0x00007fe1488fc74b n/a (radeonsi_dri.so + 0xfc74b) #4 0x00007fe14891c4e7 n/a (radeonsi_dri.so + 0x11c4e7) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3125: #0 0x00007fe15688f25e __futex_abstimed_wait_common (libc.so.6 + 0x8f25e) #1 0x00007fe156891fa0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91fa0) #2 0x00007fe14891c5a9 n/a (radeonsi_dri.so + 0x11c5a9) #3 0x00007fe1488fc74b n/a (radeonsi_dri.so + 0xfc74b) #4 0x00007fe14891c4e7 n/a (radeonsi_dri.so + 0x11c4e7) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3124: #0 0x00007fe15688f25e __futex_abstimed_wait_common (libc.so.6 + 0x8f25e) #1 0x00007fe156891fa0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91fa0) #2 0x00007fe14891c5a9 n/a (radeonsi_dri.so + 0x11c5a9) #3 0x00007fe1488fc74b n/a (radeonsi_dri.so + 0xfc74b) #4 0x00007fe14891c4e7 n/a (radeonsi_dri.so + 0x11c4e7) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) Stack trace of thread 3126: #0 0x00007fe15688f25e __futex_abstimed_wait_common (libc.so.6 + 0x8f25e) #1 0x00007fe156891fa0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91fa0) #2 0x00007fe14891c5a9 n/a (radeonsi_dri.so + 0x11c5a9) #3 0x00007fe1488fc74b n/a (radeonsi_dri.so + 0xfc74b) #4 0x00007fe14891c4e7 n/a (radeonsi_dri.so + 0x11c4e7) #5 0x00007fe156892e22 start_thread (libc.so.6 + 0x92e22) #6 0x00007fe15691433c __clone3 (libc.so.6 + 0x11433c) ELF object binary architecture: AMD x86-64 I tried also with kernel 6.10.7-1-default (64-bit), but no change. Hope that is enough information Many thanks Alex -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228777] New: VUL-0: CVE-2024-42458: server.c in Neat VNC (aka neatvnc) before 0.8.1 does not properly validate the security type.
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228777 Bug ID: 1228777 Summary: VUL-0: CVE-2024-42458: server.c in Neat VNC (aka neatvnc) before 0.8.1 does not properly validate the security type. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/416161/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mvetter(a)suse.com 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: --- server.c in Neat VNC (aka neatvnc) before 0.8.1 does not properly validate the security type. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-42458 https://www.cve.org/CVERecord?id=CVE-2024-42458 https://github.com/any1/neatvnc/commit/cc71650a69abc2573a0d96d082409d246880… https://github.com/any1/neatvnc/compare/v0.8.0...v0.8.1 https://github.com/any1/neatvnc/releases/tag/v0.8.1 http://www.openwall.com/lists/oss-security/2024/08/02/1 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1233997] New: VUL-0: CVE-2024-48651: proftpd: supplemental group inheritance grants unintended access to GID 0
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233997 Bug ID: 1233997 Summary: VUL-0: CVE-2024-48651: proftpd: supplemental group inheritance grants unintended access to GID 0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/430587/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: chris(a)computersalat.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- In ProFTPD through 1.3.8b before cec01cc, supplemental group inheritance grants unintended access to GID 0 because of the lack of supplemental groups from mod_sql. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-48651 https://www.cve.org/CVERecord?id=CVE-2024-48651 https://github.com/proftpd/proftpd/commit/cec01cc0a2523453e5da5a486bc6d977c… https://github.com/proftpd/proftpd/issues/1830 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1222505] New: ckermit: cannot create lock file in /var/lock
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222505 Bug ID: 1222505 Summary: ckermit: cannot create lock file in /var/lock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ceggers(a)arri.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Kermit needs to create a lock file for the used serial port (e.g. /dev/ttyUSB0) under /var/lock (symlink to /run/lock). Until Leap 15.5, that directory was owned by group "lock", so it was sufficient to add the current user to the "lock" group. But now the directory is owned by group "root", so using the "lock" group is not sufficient anymore. Reproducible: Always Steps to Reproduce: 1. Add current user to "dialout" group (and create re-login after that). 2. Ensure that step 1. was successful (e.g. by using the "id" command). 3. kermit -l /dev/ttyUSB0 Actual Results: Kermit gives an error "can't open device". Using "set line /dev/ttyUSB0" in kermit's interactive mode gives a more precise error message: "Sorry, write access to UUCP lockfile directory denied." Expected Results: kermit should have created the lock file and open /dev/ttyUSB0 A workaround is to change the group of /run/lock to "dialout" (and to add the current user to this group). But this change is lost after every reboot. Possibly related to https://bugzilla.opensuse.org/show_bug.cgi?id=624290 ("ckermit from contrib repository does not use lockdev, so cannot write to /var/lock"). The packet installed is: $ rpm -q ckermit --info Name : ckermit Version : 9.0.302 Release : 150000.3.3.1 Architecture: x86_64 Install Date: Mo 08 Apr 2024 09:44:42 CEST Group : Hardware/Modem Size : 2621762 License : BSD-3-Clause Signature : RSA/SHA256, Fr 01 Apr 2022 13:39:36 CEST, Key ID 70af9e8139db7c82 Source RPM : ckermit-9.0.302-150000.3.3.1.src.rpm Build Date : Fr 01 Apr 2022 13:39:14 CEST Build Host : goat10 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : http://www.kermitproject.org/ Summary : A Combined Serial and Network Communication Software Package Description : C-Kermit is a combined serial and network communication software package offering a consistent, medium-independent, and cross-platform approach to connection establishment, terminal sessions, file transfer, character-set translation, and automation of communication tasks. Distribution: SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1226392] New: lxqt-config-monitor crashes with kscreen on login, wakeup, launch
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1226392 Bug ID: 1226392 Summary: lxqt-config-monitor crashes with kscreen on login, wakeup, launch Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: lxqt-bugs(a)suse.de Reporter: brbigam(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- lxqt-config-monitor crashes on every login, every wake from sleep, and every user launch of the settings module. It segfaults and coredumps, with kscreen. Steps to Reproduce Log in to an LXQt session, or wake from sleep within one (not just from screen lock) OR open l-c-monitor Check journalctl and look in /var/lib/systemd/coredump/ folder See the coredump and sefault reports from those times Expected Behavior l-c-monitor doesn't crash and coredump in any standard usage. If kscreen crashes, l-c-monitor errors rather than crashing and coredumping. Current Behavior I don't have any particular need for l-c-monitor, since I use only one monitor, my laptop display. But opening it shows a window that's blank as if there's no detected display, and when I close it, it and kscreen segfault and coredump. If I check journalctl, it shows similar segfaults and coredumps for l-c-monitor on my user session login or wake from sleep, and the coredumps pile up in /var/lib/systemd/coredump/ Since there's no user-facing option to disable l-c-monitor, the coredumps just keep piling up. System Information Distribution & Version: openSUSE Tumbleweed 20240612 Kernel: 6.9.3 Qt Version: 6.7.1 liblxqt Version: 2.0.0 lxqt-build-tools Version: not installed Package version: lxqt-config 2.0.0; libkf6screen8 6.0.5 Openbox Other info: I wish there was a UI option to disable l-c-monitor. This bug has also been filed upstream: https://github.com/lxqt/lxqt-config/issues/1004 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230228] New: alpine-3.20.2 image fails with "Boot failed: not a bootable disk"
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230228 Bug ID: 1230228 Summary: alpine-3.20.2 image fails with "Boot failed: not a bootable disk" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: alice.brooks(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The following fails to boot with "Boot failed: not a bootable disk": ``` curl -o /tmp/alpine.qcow2 https://dl-cdn.alpinelinux.org/alpine/v3.20/releases/cloud/nocloud_alpine-3… virt-install --debug --connect qemu:///system --name alpine \ --os-variant "alpinelinux3.20" \ --boot hd \ --vcpus 1 \ --memory 128 \ --import --disk /tmp/alpine.qcow2 \ --graphics vnc,listen=127.0.0.1 \ --console file,target.type=serial,source.path=/tmp/vm \ --print-step 1 > /tmp/xml-connection virsh define /tmp/xml-connection virsh start alpine ``` This has only happened in the last few releases (tested on release 20240903 of TW). I've confirmed the qcow2 is fine by running the above on fedora and that's fine -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1226394] New: xdg-desktop-portal-lxqt not started by default
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1226394 Bug ID: 1226394 Summary: xdg-desktop-portal-lxqt not started by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: lxqt-bugs(a)suse.de Reporter: brbigam(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- xdg-desktop-portal-lxqt isn't automatically started by xdg-desktop-portal on login, so the LXQt file dialog isn't picked up by apps that could use it, like Firefox. Steps to reproduce: Log in to LXQt check running processes, such as in qps check file dialog in Firefox with widget.use-xdg-desktop-portal.file-picker set to 1 Actual result: x-d-p is running, but not x-d-p-lxqt no file dialog opens in Firefox (Unless another portal backend is also installed) Expected result: x-d-p-lxqt is running LXQt file dialog is used by Firefox System: Tumbleweed 20240613 and earlier, as long as LXQt 2.0.0 has been available LXQt 2.0.0 xdg-desktop-portal-lxqt 1.0.2 xdg-desktop-portal 1.18.4 Qt 6.7.1 Workaround: If I run /usr/libexec/xdg-desktop-portal --replace after login, x-d-p correctly picks up x-d-p-lxqt and everything works correctly. Adding this to autostart apps also works correctly. So if it's an upstream issue, openSUSE might consider adding this to packaging temporarily as a workaround. I don't know what the underlying problem might be. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1233381] New: Tumbleweed won’t recover from sleep. Force shutdown required
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233381 Bug ID: 1233381 Summary: Tumbleweed won’t recover from sleep. Force shutdown required Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kosimo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Once the computer enters sleep it won’t wake up anymore. I have to force a shut down and power it up again. Blank screen, not even cap loks light on the keyboard. ---------------- JJJJJJ =JJJJJJJ OS: openSUSE Tumbleweed x86_64 JJJJ =JJJ JJJJ Kernel: 6.11.7-1-default JJJ =JJJ JJJ Uptime: 1 hour, 1 min JJJJ =JJJ JJJ Packages: 42 (pip), 2744 (rpm), 12 (steam), 6 (flatpak-system) JJJJJJJJJJJJJJJ JJJJ Shell: bash 5.2.37 JJJJJJJJJJJJJJ JJJJ Resolution: 3840x2160 JJJJ JJJJ DE: Plasma 6.2.3 [KF 6.8.0] [Qt 6.8.0] (wayland) JJJJJ= JJJJ WM: kwin_wayland_wr JJJJJJJJJJJJJJJJJJJJJJJJJJJJJ= Theme: Breeze-Dark [GTK2/3] =JJJJJJJJJJJJJJJJJJJJJJJJJJJJJ Icons: breeze-dark [GTK2/3] JJJJ =JJJJJJ Terminal: konsole JJJJ =JJJJ CPU: AMD Ryzen 7 7800X3D (8) @ 5.050GHz JJJJ JJJJJJJJJJJJJJ GPU: AMD ATI TUF Gaming Radeon RX 7900 XTX OC JJJJ JJJJJJJJJJJJJJJ GPU: AMD ATI Raphael JJJJ JJJJ JJJJ Memory: 5884.57 MiB / 63432.22 MiB ----------------------- KDE 6.2.3 Frameworks: 6.8.0 QT: 6.8.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1229690] New: Periodic system freeze due to btrfs-cleaner even after uninstalling btrfsmaintenance
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229690 Bug ID: 1229690 Summary: Periodic system freeze due to btrfs-cleaner even after uninstalling btrfsmaintenance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: o.rojon(a)posteo.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0 Build Identifier: There are issues similar but not identical to the current one: - https://bugzilla.opensuse.org/show_bug.cgi?id=1063638 - https://bugzilla.opensuse.org/show_bug.cgi?id=1214988 - https://bugzilla.opensuse.org/show_bug.cgi?id=1111523 There is a regular btrfs-cleaner job which grinds the system to a halt, rendering it completely unresponsive for several minutes. It also happens in moments where I am working, completely disrupting my process (a note on that later). I tried several solutions to stop this from occurring, some of which are described here: https://en.opensuse.org/SDB:Disable_btrfsmaintenance: 1) Disabled Scheduled Maintenance. This did not change the behaviour, btrfs-cleaner continues being executed. 2) Resource Control services related to BTRFSMAINTENANCE with systemd and control groups. While this seemed to temporarily offset the resource usage of btrfs-cleaner in the cpu department, it regularly ground the system to a halt nonetheless. 3) Uninstall BTRFSMAINTENANCE altogether. This didn't do anything, btrfs-cleaner executes nonetheless and grinds the system to a halt. Reproducible: Didn't try Steps to Reproduce: Since I haven't understood the machinery that makes btrfs-cleaner run, I don't know how to reproduce the issue other than waiting for it to grind my system to a halt. By now, I am uncertain whether it is (or is not) related to BTRFSMAINTENANCE, which I spent a bit of time understanding (the systemd-units related to the script). Actual Results: I feel like no matter what I do (see Details), brtfs-cleaner will run anyway. I found one potential piece of interest while viewing and testing the systemd-units. It seems that the BTRFSMAINTENANCE-related units use systemd-settings to determine the current strain on the system in terms of CPU and IO which are called "CPUScheduling(Class|Priority)" and "IOScheduling(Class|Priority)" (not certain if Class or Priority was used anymore, sorry). Trying to activate the BTRFS-BALANCE.service manually, systemd showed that both options are unknown and thus ignored. If it is indeed the case that those options are not implemented in current iterations (found out about a week ago), it is a possible explanation as to why BTRFSMAINTENANCE (or btrfs-cleaner, I really don't know about their relationship) runs in moments when the system is in use, even if the setting for both options is "idle" which, according to my understanding of the manual, should prevent those jobs running when the system is currently in use. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225509] New: AUDIT-FIND: 4Pane: predictable /tmp path in PreviewPopup::DisplayImage
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1225509 Bug ID: 1225509 Summary: AUDIT-FIND: 4Pane: predictable /tmp path in PreviewPopup::DisplayImage 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: --- 4Pane uses predictable /tmp paths in PreviewPopup::DisplayImage() > 2054 pngfilepath = "/tmp/" + fn.GetName() + ".png"; > 2055 if (SvgToPng(filepath, pngfilepath, handle)) > 2056 image = wxImage(pngfilepath); > 2057 wxRemoveFile(pngfilepath); If fs.protected_symlinks=1, an unprivileged user can prevent 4Pane from displaying previews for SVG images. If fs.protected_symlinks=0, an unprivileged user can overwrite arbitrary world-readable files owned by the 4Pane user. Steps to reproduce: nobody@localhost:/tmp> ln -s /home/user/somefile foo.png # ... wait until the user previews a file named foo.svg # somefile will be overwritten An attacker can pre-create symlinks for the names of all existing SVG files on the system to increase the likelihood of triggering the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1231416] New: ZSWAP config cleanup
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1231416 Bug ID: 1231416 Summary: ZSWAP config cleanup 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Following: commit 13a488ad6c85976074f78f80a06414914890703c Author: Yosry Ahmed <yosryahmed(a)google.com> Date: Mon Oct 7 19:21:16 2024 +0000 mm: z3fold: deprecate CONFIG_Z3FOLD The z3fold compressed pages allocator is rarely used, most users use zsmalloc. The only disadvantage of zsmalloc in comparison is the dependency on MMU, and zbud is a more common option for !MMU as it was the default zswap allocator for a long time. Historically, zsmalloc had worse latency than zbud and z3fold but offered better memory savings. This is no longer the case as shown by a simple recent analysis [1]. That analysis showed that z3fold does not have any advantage over zsmalloc or zbud considering both performance and memory usage. In a kernel build test on tmpfs in a limited cgroup, z3fold took 3% more time and used 1.8% more memory. The latency of zswap_load() was 7% higher, and that of zswap_store() was 10% higher. Zsmalloc is better in all metrics. Moreover, z3fold apparently has latent bugs, which was made noticeable by a recent soft lockup bug report with z3fold [2]. Switching to zsmalloc not only fixed the problem, but also reduced the swap usage from 6~8G to 1~2G. Other users have also reported being bitten by mistakenly enabling z3fold. Other than hurting users, z3fold is repeatedly causing wasted engineering effort. Apart from investigating the above bug, it came up in multiple development discussions (e.g. [3]) as something we need to handle, when there aren't any legit users (at least not intentionally). The natural course of action is to deprecate z3fold, and remove in a few cycles if no objections are raised from active users. Next on the list should be zbud, as it offers marginal latency gains at the cost of huge memory waste when compared to zsmalloc. That one will need to wait until zsmalloc does not depend on MMU. We should likely: * set CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD_DEPRECATED=n * set CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC=y and CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=n -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1227231] New: virt-manager agama based deployment with default layout will not fit on 20GB VM
by bugzilla_noreply＠suse.com 15 Jan '25

15 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227231 Bug ID: 1227231 Summary: virt-manager agama based deployment with default layout will not fit on 20GB VM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'd like to propose new default size for VMs to be 25GB. When it comes to Agama 8/9 of today you have to drop swap (in my case 3GB) to fit on the default 20GB VM image in virt-manager. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1223420] New: VUL-0: CVE-2024-31755: cJSON: NULL pointer dereference via cJSON_SetValuestring()
by bugzilla_noreply＠suse.com 15 Jan '25

15 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1223420 Bug ID: 1223420 Summary: VUL-0: CVE-2024-31755: cJSON: NULL pointer dereference via cJSON_SetValuestring() Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/403222/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- cJSON v1.7.17 was discovered to contain a segmentation violation, which can trigger through the second parameter of function cJSON_SetValuestring at cJSON.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-31755 https://www.cve.org/CVERecord?id=CVE-2024-31755 https://github.com/DaveGamble/cJSON/issues/839 https://bugzilla.redhat.com/show_bug.cgi?id=2277268 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1229913] New: AUDIT-1: kio-admin: revisit kio-admin privileged file operations via D-Bus
by bugzilla_noreply＠suse.com 15 Jan '25

15 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229913 Bug ID: 1229913 Summary: AUDIT-1: kio-admin: revisit kio-admin privileged file operations via D-Bus 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: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: popov895(a)ukr.net Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1205607 We've been asked to have a fresh look ad kio-admin, formerly rejected in bug 1205607. AFAIK upstream activities to come up with a robust API have been abandoned, but we can still have another look at the current production code. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1233358] New: [SELinux] AVC denial for sdbootutil during snapper cleanup
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233358 Bug ID: 1233358 Summary: [SELinux] AVC denial for sdbootutil during snapper cleanup 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my Tumbleweed system with systemd-boot + TPM backed FDE and the SELinux targeted policy in enforcing mode, I found some AVC denials which were triggered by snapper-cleanup.service. snapper cleanup runs sdbootutil which in turn executes systemd-pcrlock: type=AVC msg=audit(14.11.2024 10:13:13.145:227) : avc: denied { execute } for pid=6038 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.145:228) : avc: denied { execute } for pid=6038 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.319:229) : avc: denied { execute } for pid=6082 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.319:230) : avc: denied { execute } for pid=6082 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.482:231) : avc: denied { execute } for pid=6126 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.482:232) : avc: denied { execute } for pid=6126 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.652:233) : avc: denied { execute } for pid=6170 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.652:234) : avc: denied { execute } for pid=6170 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.829:235) : avc: denied { execute } for pid=6214 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.829:236) : avc: denied { execute } for pid=6214 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.999:237) : avc: denied { execute } for pid=6258 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.999:238) : avc: denied { execute } for pid=6258 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:14.175:239) : avc: denied { execute } for pid=6302 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:14.175:240) : avc: denied { execute } for pid=6302 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1226110] New: After plasma upgrade sessions are no longer saved and restored when logging out
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1226110 Bug ID: 1226110 Summary: After plasma upgrade sessions are no longer saved and restored when logging out Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: jhtaylor20(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After the plasma upgrade to plasma5-workspace|5.27.9-bp155.2.6.1 on 06/06/24 sessions are no longer saved on logging out or restored on logging back in. Login comes up with an empty session. Changing Desktop Session from "on last logout" to something else and back makes no difference. Although I don't use it "When sessions was manually saved" does not seem to be working correctly either. If you check it and log out with two kconsole windows open when you log back in it asks for roots password for both and opens them as root instead of the user. -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1232527] New: [SELinux] "systemd-bless-boot good" fail during boot time
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1232527 Bug ID: 1232527 Summary: [SELinux] "systemd-bless-boot good" fail during boot time 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: danilo.spinella(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE MicroOS SELinux status, mode and policy name: enabled, enforcing, targeted SELinux policy version and repository: 20241021-1.1, openSUSE-Tumbleweed-Oss The software (incl. version) that is affected by the SELinux issue and the error message: systemd 256.7, systemd-bless-boot, "Failed to rename '/loader/entries/opensuse-microos-6.11.5-1-default-1+2-1.conf' to '/loader/entries/opensuse-microos-6.11.5-1-default-1.conf': Permission Denied" SELinux Audit log: type=AVC msg=audit(1730195064.486:34): avc: denied { rename } for pid=1142 comm="systemd-bless-b" name="opensuse-microos-6.11.5-1-default-1+2-1.conf" dev="vda2" ino=11 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:dosfs_t:s0 tclass=file permissive=0 Any other important details: N/A -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1228659] New: Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228659 Bug ID: 1228659 Summary: Snapshot 20240730 - unbootable after transactional-update dup Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Transactional Update Assignee: aplanas(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- All Aeon installations (and I suspect all MicroOS systemd-boot installations) are failing to boot after a transactional-update dup to the latest snapshot I suspect the cause is the misbehaviour of the sdbootutil plugin reported during the transactional-update Example logs below: (25/41) Installing: kernel-default-6.10.2-1.1.x86_64 [... Error: No ESP detected. Legacy system? ................................................................................................... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.10.2-1-default 6.10.2-1-default dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: No KEYMAP configured. dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: health-checker *** dracut-install: ERROR: installing 'grub2-editenv' dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.kGpiZ2/initramfs -a date btrfs awk grub2-editenv dracut[I]: *** Including module: pcr-signature *** dracut[I]: *** Including module: transactional-update *** dracut[I]: *** Including module: btrfs *** dracut[I]: *** Including module: kernel-modules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: rootfs-block *** dracut[I]: *** Including module: suse-btrfs *** dracut[I]: *** Including module: suse-xfs *** dracut[I]: *** Including module: terminfo *** dracut[I]: *** Including module: udev-rules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[E]: Failed to detect udev version! dracut[I]: *** Including module: dracut-systemd *** dracut[I]: *** Including module: ostree *** dracut[I]: *** Including module: selinux-microos *** dracut[I]: *** Including module: usrmount *** dracut[I]: *** Including module: base *** dracut[I]: *** Including module: fs-lib *** dracut[I]: *** Including module: shutdown *** dracut[I]: *** Including module: suse *** dracut[I]: *** Including module: suse-initrd *** dracut[I]: *** Including modules done *** dracut[I]: *** Installing kernel module dependencies *** dracut[I]: *** Installing kernel module dependencies done *** dracut[I]: *** Resolving executable dependencies *** dracut[I]: *** Resolving executable dependencies done *** dracut[I]: *** Hardlinking files *** dracut[I]: *** Hardlinking files done *** dracut[I]: *** Generating early-microcode cpio image *** dracut[I]: *** Store current command line parameters *** dracut[I]: Stored kernel commandline: dracut[I]: rd.driver.pre=btrfs dracut[I]: rd.driver.pre=overlay dracut[I]: root=UUID=42fc02eb-e038-424f-b5a5-aed45173338d rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=403,subvol=/@/.snapshots/98/snapshot,subvol=@/.snapshots/98/snapshot dracut[I]: *** Stripping files *** dracut[I]: *** Stripping files done *** dracut[I]: *** Creating image file '/boot/initrd-6.10.2-1-default' *** dracut[I]: *** Creating initramfs image file '/boot/initrd-6.10.2-1-default' done *** /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory CA enrolled. Skip /etc/uefi/certs/1F673297.crt Error: No ESP detected. Legacy system? ... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory done] -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1230118] New: [SELinux] Select SELinux as default MAC in enforcing mode in the tumbleweed installer
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230118 Bug ID: 1230118 Summary: [SELinux] Select SELinux as default MAC in enforcing mode in the tumbleweed installer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: cathy.hu(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- just pasting the email to factory as reference: RFC: SELinux as default MAC system on new Tumbleweed installations SELinux is being adopted more and more as the main Mandatory Access Control (MAC) system in openSUSE distributions and SUSE products. The SUSE SELinux working group would like to announce the plan to switch new Tumbleweed installations to SELinux as default MAC system *by the end of this year*. Currently, new Tumbleweed installations select AppArmor in the installer as default MAC system. After this change, new Tumbleweed installations will select SELinux in enforcing mode as default MAC system. Users will still be able to select AppArmor as MAC system in the installer. Existing installations will *not* be affected. If you would like to migrate your existing system from AppArmor to SELinux, we have a guide on what to consider and how to do that here [0]. *What does it mean for users?* Our SELinux policy contains many policy modules, which confine most well-known services. Switching to SELinux means more services are confined by default, which means enhanced security. On the other hand, more confinement also means that in the early phase of the adoption there could be more bugs caused by SELinux denying legitimate accesses. We perform both manual and automated tests via openQA, to ensure that our policy works seamlessly. We also rely on you, the community, to create bugreports so that we can adapt the policy to any scenarios that we did not foresee. We have a page on how to report bugs here: https://en.opensuse.org/openSUSE:Bugreport_SELinux To learn more about SELinux, we also have a Portal in the openSUSE wiki: https://en.opensuse.org/Portal:SELinux Please feel free to reply to this email in case you have any questions or concerns. We plan to do the change earliest in September 2024, and latest by the end of the year. Separate announcements will follow just before and after the change. TL;DR: - The Tumbleweed installer will select SELinux in enforcing mode as default on new installations - When: by the end of 2024, earliest in September, we will do separate announcements before and after - AppArmor can still be selected in the installer as an alternative - Existing installations will *not* change - Leap 15.x is not affected in any way [0] https://en.opensuse.org/Portal:SELinux/Setup#Setup_SELinux_on_existing_tumb… -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1221095] New: Go application packages can no longer set CGO_ENABLED=0 if external linker will be used
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1221095 Bug ID: 1221095 Summary: Go application packages can no longer set CGO_ENABLED=0 if external linker will be used Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Per Go upstream change https://go-review.googlesource.com/c/website/+/569296, as of go1.21.8+ and go1.22.1+ go build commands cannot set CGO_ENABLED=0 if the external linker will be used. (Cgo lets Go packages call C code, see https://go.dev/blog/cgo, 2011) The most commonly used option that triggers the external linker is -buildmode=pie, which we aspirationally use in most Go application packages behind conditionals for architectures where it is unsupported, currently only ppc64le. We first encountered this issue when trying to set the go metapackage from go1.21 to go1.22. Approximately 40+ Go application packages in Factory set CGO_ENABLED=0 and -buildmode=pie together. On arch i586, builds started to fail with error: -buildmode=pie requires external (cgo) linking, but cgo is not enabled This tracking bug will be referenced for SR submissions to Go application packages to adapt to the new requirements. Most of these submissions will to remove CGO_ENABLED=0 absent a requirement for its use by a specific package. Upstream comments from the above change: https://go.dev/issue/31544, CL 477839 When using an external (C) linker with cgo enabled, the `runtime/cgo` package is now supplied to the Go linker as an additional dependency to ensure that the Go runtime is compatible with any additional libraries added by the C linker. https://go.dev/issue/46330, CL 522239 go build commands that invoke the linker now error out if an external (C) linker will be used but cgo is not enabled. (The Go runtime requires cgo support to ensure that it is compatible with any additional libraries added by the C linker.) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1233961] New: VUL-0: CVE-2024-11738: gstreamer-plugins-rs: rustls: accept`
by bugzilla_noreply＠suse.com 13 Jan '25

13 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233961 https://bugzilla.suse.com/show_bug.cgi?id=1233961#c1 Bug ID: 1233961 Summary: VUL-0: CVE-2024-11738: gstreamer-plugins-rs: rustls: accept` Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/430408/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-11738:5.9:(AV:N/AC:H/PR:N/UI:N/ S:U/C:N/I:N/A:H) Severity: Normal Priority: P5 - None Component: Security Assignee: bjorn.lie(a)gmail.com Reporter: emanuele.cappello(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1233897 Target Milestone: --- Found By: --- Blocker: --- --- Comment #1 from Emanuele Cappello <emanuele.cappello(a)suse.com> --- A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use `rustls::server::Acceptor::accept()` are affected. Servers that use `tokio-rustls`'s `LazyConfigAcceptor` API are affected. Servers that use `tokio-rustls`'s `TlsAcceptor` API are not affected. Servers that use `rustls-ffi`'s `rustls_acceptor_accept` API are affected. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-11738 https://bugzilla.redhat.com/show_bug.cgi?id=2328732 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1233414] New: Torn screen when at 4k@120hz after Tumbleweed 2024-10-05
by bugzilla_noreply＠suse.com 12 Jan '25

12 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233414 Bug ID: 1233414 Summary: Torn screen when at 4k@120hz after Tumbleweed 2024-10-05 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: me(a)bobloblaw.eu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878608 --> https://bugzilla.suse.com/attachment.cgi?id=878608&action=edit Photo of torn screen at 4k@120hz Hello! I run Tumbleweed on a mini pc which is connected to a TV and which I usually run at 4k (3840x2160) resolution and 120hz refresh rate. After I ran a dist upgrade on 2024-10-05 the screen is no longer displayed properly at this resolution and refresh rate combo. The screen looks split in half, with the right half looking stretched and purple. See attached photo. If I reduce the refresh rate to 60hz, it displays normally. Extra info: - Link to opensuse forums thread where I originally asked for help regarding this issue https://forums.opensuse.org/t/torn-screen-when-at-4k-120hz-after-tumbleweed… - Output of "inxi -aFz" on the working version (20240920): System: Kernel: 6.10.11-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: hpet avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.10.11-1-default root=UUID=49473a36-7184-4268-91c6-15b630c1a7e7 splash=silent preempt=full mitigations=auto quiet security=apparmor Console: pty pts/2 DM: 1: LightDM v: 1.32.0 2: SDDM note: stopped Distro: openSUSE Tumbleweed 20240920 Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50 v: 0624 serial: <filter> Mobo: ASUSTeK model: PN50 serial: N/A uuid: a9563f6d-7353-1868-24c9-7c10c9501656 UEFI: ASUSTeK v: 0624 date: 07/06/2022 CPU: Info: model: AMD Ryzen 7 4700U with Radeon Graphics socket: FP6 bits: 64 type: MCP arch: Zen 2 gen: 2 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1 microcode: 0x8600106 Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 smt: <unsupported> cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB desc: 2x4 MiB Speed (MHz): avg: 1400 min/max: 1400/2000 boost: disabled base/boost: 2000/4200 scaling: driver: acpi-cpufreq governor: schedutil volts: 1.2 V ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 bogomips: 31959 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: reg_file_data_sampling status: Not affected Type: retbleed mitigation: untrained return thunk; SMT disabled Type: spec_rstack_overflow mitigation: SMT disabled Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir [Radeon Vega Series / Radeon Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 05:00.0 chip-ID: 1002:1636 class-ID: 0300 temp: 48.0 C Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.2 compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: amdgpu tty: 82x43 Monitor-1: HDMI-A-1 model: LG (GoldStar) TV SSCR2 serial: <filter> built: 2021 res: 3840x2160 dpi: 61 gamma: 1.2 size: 1600x900mm (62.99x35.43") diag: 1836mm (72.3") ratio: 16:9 modes: max: 3840x2160 min: 720x400 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi inactive: wayland,x11 API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 24.1.7 note: console (EGL sourced) renderer: AMD Radeon Graphics (radeonsi renoir LLVM 18.1.8 DRM 3.57 6.10.11-1-default), llvmpipe (LLVM 18.1.8 256 bits) API: Vulkan v: 1.3.290 layers: 1 device: 0 type: integrated-gpu name: AMD Radeon Graphics (RADV RENOIR) driver: N/A device-ID: 1002:1636 surfaces: N/A Audio: Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403 Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480 Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403 API: ALSA v: k6.10.11-1-default status: kernel-api with: aoss type: oss-emulator tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.2.3 status: n/a (root, process) with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: fc00 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280 IF: wlan1 state: down mac: <filter> Info: services: NetworkManager,smbd,sshd Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 6-1.1:4 chip-ID: 0a12:0001 class-ID: e001 Report: btmgmt ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 4.0 lmp-v: 6 status: discoverable: no pairing: no class-ID: 7c0104 Device-2: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 6-3:3 chip-ID: 8087:0029 class-ID: e001 Report: ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104 Drives: Local Storage: total: 2.73 TiB used: 961.66 GiB (34.4%) ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S1000G size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: SBM02103 temp: 46.9 C scheme: GPT SMART: yes health: PASSED on: 1y 141d 0h cycles: 33 read-units: 43,751,830 [22.4 TB] written-units: 29,433,615 [15.0 TB] ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 2TB family: based SSDs size: 1.82 TiB block-size: physical: 512 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 2B6Q temp: 36 C scheme: GPT SMART: yes state: enabled health: PASSED on: 1y 187d 6h cycles: 706 written: 25.77 TiB Partition: ID-1: / raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 100.27 GiB (12.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 11.9 MiB (2.3%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1 ID-3: /home raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 100.27 GiB (12.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-4: /opt raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 100.27 GiB (12.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-5: /tmp raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 100.27 GiB (12.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-6: /var raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 100.27 GiB (12.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 50.2 C mobo: N/A gpu: amdgpu temp: 48.0 C Fan Speeds (rpm): N/A Info: Memory: total: 16 GiB note: est. available: 15.05 GiB used: 5.31 GiB (35.3%) Processes: 395 Power: uptime: 0h 1m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6 GiB services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical tool: systemctl Packages: pm: rpm pkgs: N/A note: see --rpm tools: yast,zypper pm: flatpak pkgs: 21 Compilers: gcc: 14.2.0 alt: 13 Shell: Sudo (sudo) v: 1.9.15p5 default: Bash v: 5.2.32 running-in: pty pts/2 inxi: 3.3.36 - Output of "inxi -aFz" on the current, non-working version (20241112) System: Kernel: 6.11.7-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: hpet avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.11.7-1-default root=UUID=49473a36-7184-4268-91c6-15b630c1a7e7 splash=silent preempt=full mitigations=auto quiet security=apparmor Console: pty pts/3 DM: 1: LightDM v: 1.32.0 2: SDDM note: stopped Distro: openSUSE Tumbleweed 20241112 Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50 v: 0624 serial: <filter> Mobo: ASUSTeK model: PN50 serial: N/A uuid: a9563f6d-7353-1868-24c9-7c10c9501656 UEFI: ASUSTeK v: 0624 date: 07/06/2022 CPU: Info: model: AMD Ryzen 7 4700U with Radeon Graphics socket: FP6 bits: 64 type: MCP arch: Zen 2 gen: 2 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1 microcode: 0x8600106 Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 smt: <unsupported> cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB desc: 2x4 MiB Speed (MHz): avg: 1400 min/max: 1400/2000 boost: disabled base/boost: 2000/4200 scaling: driver: acpi-cpufreq governor: schedutil volts: 1.2 V ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 bogomips: 31959 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: reg_file_data_sampling status: Not affected Type: retbleed mitigation: untrained return thunk; SMT disabled Type: spec_rstack_overflow mitigation: SMT disabled Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir [Radeon Vega Series / Radeon Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 05:00.0 chip-ID: 1002:1636 class-ID: 0300 temp: 47.0 C Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4 compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: amdgpu tty: 82x43 Monitor-1: HDMI-A-1 model: LG (GoldStar) TV SSCR2 serial: <filter> built: 2021 res: 3840x2160 dpi: 61 gamma: 1.2 size: 1600x900mm (62.99x35.43") diag: 1836mm (72.3") ratio: 16:9 modes: max: 3840x2160 min: 720x400 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi inactive: wayland,x11 API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 24.2.6 note: console (EGL sourced) renderer: AMD Radeon Graphics (radeonsi renoir LLVM 19.1.3 DRM 3.59 6.11.7-1-default), llvmpipe (LLVM 19.1.3 256 bits) API: Vulkan v: 1.3.296 layers: 1 device: 0 type: integrated-gpu name: AMD Radeon Graphics (RADV RENOIR) driver: N/A device-ID: 1002:1636 surfaces: N/A Audio: Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403 Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480 Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403 API: ALSA v: k6.11.7-1-default status: kernel-api with: aoss type: oss-emulator tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.2.6 status: n/a (root, process) with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: fc00 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280 IF: wlan1 state: down mac: <filter> Info: services: NetworkManager,smbd,sshd Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 6-1.1:4 chip-ID: 0a12:0001 class-ID: e001 Report: btmgmt ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 4.0 lmp-v: 6 status: discoverable: no pairing: no class-ID: 7c0104 Device-2: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 6-3:3 chip-ID: 8087:0029 class-ID: e001 Report: ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104 Drives: Local Storage: total: 2.73 TiB used: 964.85 GiB (34.5%) ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S1000G size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: SBM02103 temp: 47.9 C scheme: GPT SMART: yes health: PASSED on: 1y 162d 10h cycles: 33 read-units: 44,323,055 [22.6 TB] written-units: 30,718,266 [15.7 TB] ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 2TB family: based SSDs size: 1.82 TiB block-size: physical: 512 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 2B6Q temp: 37 C scheme: GPT SMART: yes state: enabled health: PASSED on: 1y 209d 2h cycles: 706 written: 25.78 TiB Partition: ID-1: / raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 102.69 GiB (12.3%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 11.9 MiB (2.3%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1 ID-3: /home raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 102.69 GiB (12.3%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-4: /opt raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 102.69 GiB (12.3%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-5: /tmp raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 102.69 GiB (12.3%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 ID-6: /var raw-size: 837.91 GiB size: 837.91 GiB (100.00%) used: 102.69 GiB (12.3%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 49.5 C mobo: N/A gpu: amdgpu temp: 47.0 C Fan Speeds (rpm): N/A Info: Memory: total: 16 GiB note: est. available: 15.05 GiB used: 8.67 GiB (57.6%) Processes: 389 Power: uptime: 3d 8h 26m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6 GiB services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical tool: systemctl Packages: pm: rpm pkgs: N/A note: see --rpm tools: yast,zypper pm: flatpak pkgs: 21 Compilers: gcc: 14.2.1 alt: 13 Shell: Sudo (sudo) v: 1.9.15p5 default: Bash v: 5.2.37 running-in: pty pts/3 inxi: 3.3.36 -- You are receiving this mail because: You are on the CC list for the bug.

1 4