Created attachment 156838 [details] Powerdevil error log SUMMARY *** The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working). *** STEPS TO REPRODUCE After installing KDE 5.27.2 I see that the error with Powerdevil continues to occur. I have done some more testing and have been able to pinpoint a bit more when the problem occurs. The bug is independent of the installed kernel version, contrary to what I reported at first. I see that the failure occurs when the computer loses the HDMI signal for a period of about 15 minutes. I don't mean just the monitor turning off, I mean completely losing the signal to the monitor by unplugging the cable (or switching the active computer on a KVM switch, which would be the same result). I have done 2 tests. Test 1: 1. Having two computers connected to a KVM switch (IMPORTANT: without it having EDID emulation). 2. Boot computer 1 with Linux. Logging in KDE. 3. Now through the KVM switch, pass control to computer 2, in such a way that computer 1 loses the HDMI signal. 4. Wait around 15 minutes. 5. Return control now to computer 1. 6. Go to the power management option in Settings. Now the following error will be displayed: "Power Management configuration module could not be loaded. The Power Management Service appears not to be running". Test 2: (without KVM switch) 1. Boot the computer with Linux. Logging in KDE. 2. Disconnect the HDMI cable from the computer. 3. Wait around 15 minutes. 4. Reconnect the HDMI cable to the computer. 6. Go to the power management option in Settings. Now the following error will be displayed: "Power Management configuration module could not be loaded. The Power Management Service appears not to be running". Looking at the logs in KSystemLog (which I attached), I see that it is leaving this error related to Power Management: 2/28/23 20:12 systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" 2/28/23 20:12 systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" 2/28/23 20:12 systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 29,3 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: BESSTAR TECH LIMITED Product Name: UM350
Tested that this error does not occur with GNOME. I have made the same combinations that I have indicated above and in all cases in GNOME the power management has worked perfectly, with or without an HDMI cable connected or without an HDMI signal through the KVM switch.
Created attachment 156840 [details] Powerdevil error log 2 I have done more tests and I have a news about this: it is not necessary to wait 15 minutes, as soon as KDE loses the HDMI signal, either by disconnecting the HDMI cable or by activating another computer on the KVM swtich, the error occurs from Powerdevil and power management stops working. I attach another log with this case, the crash starts at line 900: 28/2/23 23:07 systemd-coredump Process 3736 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 3736: #0 0x00007f6d3cea08ec n/a (libc.so.6 + 0x878ec) #1 0x00007f6d3ce51ea8 raise (libc.so.6 + 0x38ea8) #2 0x00007f6d3e3e637c _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x737c) #3 0x00007f6d3ce51f50 n/a (libc.so.6 + 0x38f50) #4 0x00007f6d3e405479 wl_proxy_marshal_array_flags (libwayland-client.so.0 + 0xa479) #5 0x00007f6d3e405afa wl_proxy_marshal_flags (libwayland-client.so.0 + 0xaafa) #6 0x00007f6d34161f5b n/a (libKF5ScreenDpms.so.8 + 0x6f5b) #7 0x00007f6d34162960 n/a (libKF5ScreenDpms.so.8 + 0x7960) #8 0x00007f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #9 0x00007f6d37524aef _ZN15QtWaylandClient15QWaylandDisplay19addRegistryListenerEPFvPvP11wl_registryjRK7QStringjES1_ (libQt5WaylandClient.so.5 + 0x74aef) #10 0x00007f6d37542760 _ZN23QWaylandClientExtension19addRegistryListenerEv (libQt5WaylandClient.so.5 + 0x92760) #11 0x00007f6d3d69d51e _ZNK11QMetaMethod6invokeEP7QObjectN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS5_S5_S5_S5_S5_S5_S5_S5_S5_ (libQt5Core.so.5 + 0x29d51e) #12 0x00007f6d3d69df10 _ZN11QMetaObject12invokeMethodEP7QObjectPKcN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS7_S7_S7_S7_S7_S7_S7_S7_S7_ (libQt5Core.so.5 + 0x29df10) #13 0x00007f6d34161d8c n/a (libKF5ScreenDpms.so.8 + 0x6d8c) #14 0x00007f6d34163928 _ZNK7KScreen4Dpms11isSupportedEv (libKF5ScreenDpms.so.8 + 0x8928) #15 0x00007f6d3e3afd70 _ZN10PowerDevil10ActionPool4initEPNS_4CoreE (libpowerdevilcore.so.2 + 0x12d70) #16 0x00007f6d3e3b7a9d _ZN10PowerDevil4Core14onBackendReadyEv (libpowerdevilcore.so.2 + 0x1aa9d) #17 0x00007f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #18 0x00007f6d36c2f35b _ZN23PowerDevilUPowerBackend18initWithBrightnessEb (powerdevilupowerbackend.so + 0x1135b) #19 0x00007f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #20 0x00007f6d36c26414 _ZN23PowerDevilUPowerBackend24brightnessSupportQueriedEb (powerdevilupowerbackend.so + 0x8414) #21 0x00007f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #22 0x00007f6d3e23843a _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x5a43a) #23 0x00007f6d3e23e54c _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x6054c) #24 0x00007f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #25 0x00007f6d3805a785 n/a (kauth_helper_plugin.so + 0xa785) #26 0x00007f6d3805ae91 n/a (kauth_helper_plugin.so + 0xae91) #27 0x00007f6d3e1bf45f n/a (libQt5DBus.so.5 + 0x6145f) #28 0x00007f6d3d6b1bb0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1bb0) #29 0x00007f6d3d68df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48) #30 0x00007f6d3d68ea53 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x28ea53) #31 0x00007f6d3d6d4e88 n/a (libQt5Core.so.5 + 0x2d4e88) #32 0x00007f6d3c11682b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b) #33 0x00007f6d3c16dcc9 n/a (libglib-2.0.so.0 + 0xaccc9) #34 0x00007f6d3c1150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #35 0x00007f6d3d6d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #36 0x00007f6d3d6866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #37 0x00007f6d3d691219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #38 0x000055eb4210055b n/a (org_kde_powerdevil + 0x655b) #39 0x00007f6d3ce3c790 n/a (libc.so.6 + 0x23790) #40 0x00007f6d3ce3c84a __libc_start_main (libc.so.6 + 0x2384a) #41 0x000055eb42101095 n/a (org_kde_powerdevil + 0x7095) Stack trace of thread 3738: #0 0x00007f6d3ce9b9a0 n/a (libc.so.6 + 0x829a0) #1 0x00007f6d3cea1ea2 pthread_mutex_lock (libc.so.6 + 0x88ea2) #2 0x00007f6d3e403635 wl_display_read_events (libwayland-client.so.0 + 0x8635) #3 0x00007f6d37522d3d n/a (libQt5WaylandClient.so.5 + 0x72d3d) #4 0x00007f6d3d4e432a n/a (libQt5Core.so.5 + 0xe432a) #5 0x00007f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x00007f6d3cf20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 3739: #0 0x00007f6d3ce9b9a0 n/a (libc.so.6 + 0x829a0) #1 0x00007f6d3cea1ea2 pthread_mutex_lock (libc.so.6 + 0x88ea2) #2 0x00007f6d3e403635 wl_display_read_events (libwayland-client.so.0 + 0x8635) #3 0x00007f6d37522d3d n/a (libQt5WaylandClient.so.5 + 0x72d3d) #4 0x00007f6d3d4e432a n/a (libQt5Core.so.5 + 0xe432a) #5 0x00007f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x00007f6d3cf20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 3740: #0 0x00007f6d3cf139df __poll (libc.so.6 + 0xfa9df) #1 0x00007f6d3c16dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007f6d3c1150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #3 0x00007f6d3c115132 n/a (libglib-2.0.so.0 + 0x54132) #4 0x00007f6d3c143db5 n/a (libglib-2.0.so.0 + 0x82db5) #5 0x00007f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x00007f6d3cf20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 3741: #0 0x00007f6d3cf139df __poll (libc.so.6 + 0xfa9df) #1 0x00007f6d3c16dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007f6d3c115d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f) #3 0x00007f6d35af7aec n/a (libgio-2.0.so.0 + 0x10aaec) #4 0x00007f6d3c143db5 n/a (libglib-2.0.so.0 + 0x82db5) #5 0x00007f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x00007f6d3cf20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 3737: #0 0x00007f6d3cf139df __poll (libc.so.6 + 0xfa9df) #1 0x00007f6d3c16dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007f6d3c1150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #3 0x00007f6d3d6d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #4 0x00007f6d3d6866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #5 0x00007f6d3d4e725f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe725f) #6 0x00007f6d3e181cba n/a (libQt5DBus.so.5 + 0x23cba) #7 0x00007f6d3d4e432a n/a (libQt5Core.so.5 + 0xe432a) #8 0x00007f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5) #9 0x00007f6d3cf20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 3749: #0 0x00007f6d3cf16341 pselect (libc.so.6 + 0xfd341) #1 0x00007f6d3b216524 n/a (libusbmuxd-2.0.so.6 + 0x2524) #2 0x00007f6d3b2178a9 n/a (libusbmuxd-2.0.so.6 + 0x38a9) #3 0x00007f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5) #4 0x00007f6d3cf20d90 n/a (libc.so.6 + 0x107d90) ELF object binary architecture: AMD x86-64 28/2/23 23:07 audit SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-coredump@21-3792-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 28/2/23 23:07 systemd systemd-coredump@21-3792-0.service: Deactivated successfully. 28/2/23 23:07 systemd Failed to start Powerdevil. 28/2/23 23:07 audit BPF prog-id=102 op=UNLOAD 28/2/23 23:07 audit BPF prog-id=101 op=UNLOAD 28/2/23 23:07 audit BPF prog-id=100 op=UNLOAD 28/2/23 23:07 kernel usb 2-3.2: new low-speed USB device number 13 using xhci_hcd 28/2/23 23:07 systemd plasma-powerdevil.service: Scheduled restart job, restart counter is at 6. 28/2/23 23:07 systemd Stopped Powerdevil. 28/2/23 23:07 systemd Failed to start Powerdevil.
The backtrace is virtually identical to the one in Bug 466181. But it's not *exactly* identical. It would help if you could get debug symbols for libkscreen and get a new backtrace. And also not a raw stack trace; an actual human-readable backtrace. `coredumpctl
...I was about to say: `coredumpctl` can help with this. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.
coredumpctl backtrace: PID: 1984 (org_kde_powerde) UID: 1000 (rondo) GID: 1000 (rondo) Signal: 11 (SEGV) Timestamp: Tue 2023-02-28 23:05:34 CET (1 day 4h ago) Command Line: /usr/lib/org_kde_powerdevil Executable: /usr/lib/org_kde_powerdevil Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service Unit: user@1000.service User Unit: plasma-powerdevil.service Slice: user-1000.slice Owner UID: 1000 (rondo) Boot ID: 1f36683284624ef78d6a3a1b6af2fda9 Machine ID: f894d2e603cd424bb9bcb2d128098414 Hostname: ComputerL Storage: /var/lib/systemd/coredump/core.org_kde_powerde.1000.1f36683284624ef78d6a3a1b6af2fda9.1984.1677621934000000.zst (present) Size on Disk: 1.2M Message: Process 1984 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 1984: #0 0x00007fdffcd3a479 wl_proxy_marshal_array_flags (libwayland-client.so.0 + 0xa479) #1 0x00007fdffcd3aafa wl_proxy_marshal_flags (libwayland-client.so.0 + 0xaafa) #2 0x00007fdff429af5b n/a (libKF5ScreenDpms.so.8 + 0x6f5b) #3 0x00007fdff429b960 n/a (libKF5ScreenDpms.so.8 + 0x7960) #4 0x00007fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #5 0x00007fdff641daef _ZN15QtWaylandClient15QWaylandDisplay19addRegistryListenerEPFvPvP11wl_registryjRK7QStringjES1_ (libQt5WaylandClient.so.5 + 0x74aef) #6 0x00007fdff643b760 _ZN23QWaylandClientExtension19addRegistryListenerEv (libQt5WaylandClient.so.5 + 0x92760) #7 0x00007fdffc09d51e _ZNK11QMetaMethod6invokeEP7QObjectN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS5_S5_S5_S5_S5_S5_S5_S5_S5_ (libQt5Core.so.5 + 0x29d51e) #8 0x00007fdffc09df10 _ZN11QMetaObject12invokeMethodEP7QObjectPKcN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS7_S7_S7_S7_S7_S7_S7_S7_S7_ (libQt5Core.so.5 + 0x29df10) #9 0x00007fdff429ad8c n/a (libKF5ScreenDpms.so.8 + 0x6d8c) #10 0x00007fdff429c928 _ZNK7KScreen4Dpms11isSupportedEv (libKF5ScreenDpms.so.8 + 0x8928) #11 0x00007fdffcce4d70 _ZN10PowerDevil10ActionPool4initEPNS_4CoreE (libpowerdevilcore.so.2 + 0x12d70) #12 0x00007fdffcceca9d _ZN10PowerDevil4Core14onBackendReadyEv (libpowerdevilcore.so.2 + 0x1aa9d) #13 0x00007fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #14 0x00007fdff556735b _ZN23PowerDevilUPowerBackend18initWithBrightnessEb (powerdevilupowerbackend.so + 0x1135b) #15 0x00007fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #16 0x00007fdff555e414 _ZN23PowerDevilUPowerBackend24brightnessSupportQueriedEb (powerdevilupowerbackend.so + 0x8414) #17 0x00007fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #18 0x00007fdffcb6d43a _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x5a43a) #19 0x00007fdffcb7354c _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x6054c) #20 0x00007fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #21 0x00007fdff557f785 n/a (kauth_helper_plugin.so + 0xa785) #22 0x00007fdff557fe91 n/a (kauth_helper_plugin.so + 0xae91) #23 0x00007fdffcaf445f n/a (libQt5DBus.so.5 + 0x6145f) #24 0x00007fdffc0b1bb0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1bb0) #25 0x00007fdffc08df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48) #26 0x00007fdffc08ea53 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x28ea53) #27 0x00007fdffc0d4e88 n/a (libQt5Core.so.5 + 0x2d4e88) #28 0x00007fdffad1682b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b) #29 0x00007fdffad6dcc9 n/a (libglib-2.0.so.0 + 0xaccc9) #30 0x00007fdffad150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #31 0x00007fdffc0d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #32 0x00007fdffc0866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #33 0x00007fdffc091219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #34 0x0000563ded70c55b n/a (org_kde_powerdevil + 0x655b) #35 0x00007fdffb83c790 n/a (libc.so.6 + 0x23790) #36 0x00007fdffb83c84a __libc_start_main (libc.so.6 + 0x2384a) #37 0x0000563ded70d095 n/a (org_kde_powerdevil + 0x7095) Stack trace of thread 1992: #0 0x00007fdffb9139df __poll (libc.so.6 + 0xfa9df) #1 0x00007fdffad6dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007fdffad150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #3 0x00007fdffad15132 n/a (libglib-2.0.so.0 + 0x54132) #4 0x00007fdffad43db5 n/a (libglib-2.0.so.0 + 0x82db5) #5 0x00007fdffb89ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x00007fdffb920d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 1989: #0 0x00007fdffb9139df __poll (libc.so.6 + 0xfa9df) #1 0x00007fdffad6dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007fdffad150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #3 0x00007fdffc0d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #4 0x00007fdffc0866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #5 0x00007fdffbee725f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe725f) #6 0x00007fdffcab6cba n/a (libQt5DBus.so.5 + 0x23cba) #7 0x00007fdffbee432a n/a (libQt5Core.so.5 + 0xe432a) #8 0x00007fdffb89ebb5 n/a (libc.so.6 + 0x85bb5) #9 0x00007fdffb920d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 1990: #0 0x00007fdffb9139df __poll (libc.so.6 + 0xfa9df) #1 0x00007fdff641bd1d n/a (libQt5WaylandClient.so.5 + 0x72d1d) #2 0x00007fdffbee432a n/a (libQt5Core.so.5 + 0xe432a) #3 0x00007fdffb89ebb5 n/a (libc.so.6 + 0x85bb5) #4 0x00007fdffb920d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 1993: #0 0x00007fdffb9139df __poll (libc.so.6 + 0xfa9df) #1 0x00007fdffad6dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007fdffad15d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f) #3 0x00007fdff443faec n/a (libgio-2.0.so.0 + 0x10aaec) #4 0x00007fdffad43db5 n/a (libglib-2.0.so.0 + 0x82db5) #5 0x00007fdffb89ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x00007fdffb920d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 1991: #0 0x00007fdffb9139df __poll (libc.so.6 + 0xfa9df) #1 0x00007fdff641bd1d n/a (libQt5WaylandClient.so.5 + 0x72d1d) #2 0x00007fdffbee432a n/a (libQt5Core.so.5 + 0xe432a) #3 0x00007fdffb89ebb5 n/a (libc.so.6 + 0x85bb5) #4 0x00007fdffb920d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 2001: #0 0x00007fdffb916341 pselect (libc.so.6 + 0xfd341) #1 0x00007fdffac06524 n/a (libusbmuxd-2.0.so.6 + 0x2524) #2 0x00007fdffac078a9 n/a (libusbmuxd-2.0.so.6 + 0x38a9) #3 0x00007fdffb89ebb5 n/a (libc.so.6 + 0x85bb5) #4 0x00007fdffb920d90 n/a (libc.so.6 + 0x107d90) ELF object binary architecture: AMD x86-64 And baloo service: PID: 701 (baloo_file) UID: 1000 (rondo) GID: 1000 (rondo) Signal: 6 (ABRT) Timestamp: Sun 2023-02-26 16:06:59 CET (3 days ago) Command Line: /usr/lib/baloo_file Executable: /usr/lib/baloo_file Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service Unit: user@1000.service User Unit: kde-baloo.service Slice: user-1000.slice Owner UID: 1000 (rondo) Boot ID: cf312f47f003426fa2fde6651835f29b Machine ID: f894d2e603cd424bb9bcb2d128098414 Hostname: ComputerL Storage: /var/lib/systemd/coredump/core.baloo_file.1000.cf312f47f003426fa2fde6651835f29b.701.1677424019000000.zst (missing) Message: Process 701 (baloo_file) of user 1000 dumped core. Stack trace of thread 824: #0 0x00007ff8b6ea08ec n/a (libc.so.6 + 0x878ec) #1 0x00007ff8b6e51ea8 raise (libc.so.6 + 0x38ea8) #2 0x00007ff8b7bde37c _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x737c) #3 0x00007ff8b6e51f50 n/a (libc.so.6 + 0x38f50) #4 0x00007ff8b6ea08ec n/a (libc.so.6 + 0x878ec) #5 0x00007ff8b6e51ea8 raise (libc.so.6 + 0x38ea8) #6 0x00007ff8b6e3b53d abort (libc.so.6 + 0x2253d) #7 0x00007ff8b72ac19c n/a (liblmdb.so + 0x419c) #8 0x00007ff8b72ac1f9 n/a (liblmdb.so + 0x41f9) #9 0x00007ff8b72b0e06 n/a (liblmdb.so + 0x8e06) #10 0x00007ff8b72b2e13 n/a (liblmdb.so + 0xae13) #11 0x00007ff8b72b6401 mdb_cursor_put (liblmdb.so + 0xe401) #12 0x00007ff8b72b7c3f mdb_txn_commit (liblmdb.so + 0xfc3f) #13 0x00007ff8b7b60fbc _ZN5Baloo11Transaction6commitEv (libKF5BalooEngine.so.5 + 0x1afbc) #14 0x0000565534b4f8aa n/a (baloo_file + 0x248aa) #15 0x00007ff8b74e8251 n/a (libQt5Core.so.5 + 0xe8251) #16 0x00007ff8b74e432a n/a (libQt5Core.so.5 + 0xe432a) #17 0x00007ff8b6e9ebb5 n/a (libc.so.6 + 0x85bb5) #18 0x00007ff8b6f20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 706: #0 0x00007ff8b6f139df __poll (libc.so.6 + 0xfa9df) #1 0x00007ff8b5f6dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007ff8b5f150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #3 0x00007ff8b76d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #4 0x00007ff8b76866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #5 0x00007ff8b74e725f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe725f) #6 0x00007ff8b7ae9cba n/a (libQt5DBus.so.5 + 0x23cba) #7 0x00007ff8b74e432a n/a (libQt5Core.so.5 + 0xe432a) #8 0x00007ff8b6e9ebb5 n/a (libc.so.6 + 0x85bb5) #9 0x00007ff8b6f20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 708: #0 0x00007ff8b6f16341 pselect (libc.so.6 + 0xfd341) #1 0x00007ff8b6335524 n/a (libusbmuxd-2.0.so.6 + 0x2524) #2 0x00007ff8b63368a9 n/a (libusbmuxd-2.0.so.6 + 0x38a9) #3 0x00007ff8b6e9ebb5 n/a (libc.so.6 + 0x85bb5) #4 0x00007ff8b6f20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 701: #0 0x00007ff8b6f139df __poll (libc.so.6 + 0xfa9df) #1 0x00007ff8b5f6dc2f n/a (libglib-2.0.so.0 + 0xacc2f) #2 0x00007ff8b5f150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #3 0x00007ff8b76d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #4 0x00007ff8b76866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #5 0x00007ff8b7691219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #6 0x0000565534b39dab n/a (baloo_file + 0xedab) #7 0x00007ff8b6e3c790 n/a (libc.so.6 + 0x23790) #8 0x00007ff8b6e3c84a __libc_start_main (libc.so.6 + 0x2384a) #9 0x0000565534b3a245 n/a (baloo_file + 0xf245) ELF object binary architecture: AMD x86-64
I also have constant Powerdevil crashes after updating to 5.27.2. I don't know if my issue is exactly like this one but I pase here my bt in case it helps. I can replicate the crash all the times the moment I plug/unplug my laptop to the docking station. #0 __GI___pthread_sigmask (how=1, newmask=<optimized out>, oldmask=0x0) at pthread_sigmask.c:43 #1 0x00007fad7e05214d in __GI___sigprocmask (how=<optimized out>, set=<optimized out>, oset=<optimized out>) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x00007fad7f5061eb in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at /usr/src/debug/kcrash/kcrash-5.103.0/src/kcrash.cpp:414 #3 0x00007fad7f5087e6 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.103.0/src/kcrash.cpp:625 #4 0x00007fad7e051f50 in <signal handler called> () at /usr/lib/libc.so.6 #5 0x00007fad7f547479 in serialize_closure (buffer_count=<optimized out>, buffer=0x55c70f2b0f50, closure=0x55c70f2e9f40) at ../wayland-1.21.0/src/connection.c:1157 #6 wl_closure_send (connection=<optimized out>, closure=0x55c70f2e9f40) at ../wayland-1.21.0/src/connection.c:1225 #7 wl_proxy_marshal_array_flags (proxy=proxy@entry=0x55c70f28afd0, opcode=opcode@entry=0, interface=interface@entry=0x7fad75262440 <org_kde_kwin_dpms_interface>, version=version@entry=1, flags=flags@entry=0, args=args@entry=0x7fffcd196370) at ../wayland-1.21.0/src/wayland-client.c:859 #8 0x00007fad7f547afa in wl_proxy_marshal_flags (proxy=0x55c70f28afd0, opcode=0, interface=0x7fad75262440 <org_kde_kwin_dpms_interface>, version=1, flags=0) at ../wayland-1.21.0/src/wayland-client.c:791 #9 0x00007fad7525df5b in org_kde_kwin_dpms_manager_get (output=0x31, org_kde_kwin_dpms_manager=0x55c70f28afd0) at /usr/src/debug/libkscreen/build/src/libdpms/wayland-dpms-client-protocol.h:131 #10 QtWayland::org_kde_kwin_dpms_manager::get(wl_output*) (this=0x55c70f1f26d0, output=0x31) at /usr/src/debug/libkscreen/build/src/libdpms/qwayland-dpms.cpp:70 #11 DpmsManager::addScreen(QScreen*) (this=0x55c70f1f26c0, screen=<optimized out>) at /usr/src/debug/libkscreen/libkscreen-5.27.2/src/libdpms/waylanddpmshelper.cpp:118 #12 0x00007fad7e8bea71 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffcd196660, r=<optimized out>, this=0x7fad7002a800, this=<optimized out>, r=<optimized out>, a=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate<false>(QObject*, int, void**) (sender=0x7fffcd197040, signal_index=9, argv=0x7fffcd196660) at kernel/qobject.cpp:3923 #14 0x00007fad7ed41007 in QGuiApplication::screenAdded(QScreen*) (this=<optimized out>, _t1=<optimized out>) at .moc/moc_qguiapplication.cpp:389 #15 0x00007fad78527724 in QtWaylandClient::QWaylandDisplay::registry_global_remove(unsigned int) (this=0x55c70f167c00, id=47) at /usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddisplay.cpp:566 #16 0x00007fad792ce4f6 in ffi_call_unix64 () at ../src/x86/unix64.S:104 #17 0x00007fad792caf5e in ffi_call_int (cif=cif@entry=0x7fffcd1968a0, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=closure@entry=0x0) at ../src/x86/ffi64.c:673 #18 0x00007fad792cdb73 in ffi_call (cif=cif@entry=0x7fffcd1968a0, fn=<optimized out>, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7fffcd196970) at ../src/x86/ffi64.c:710 #19 0x00007fad7f544645 in wl_closure_invoke (closure=closure@entry=0x7fad6c009ca0, target=<optimized out>, target@entry=0x55c70f19d620, opcode=opcode@entry=1, data=<optimized out>, flags=1) at ../wayland-1.21.0/src/connection.c:1025 #20 0x00007fad7f544e03 in dispatch_event (display=display@entry=0x55c70f19d4d0, queue=0x55c70f19d5a0) at ../wayland-1.21.0/src/wayland-client.c:1595 #21 0x00007fad7f544ffc in dispatch_queue (queue=0x55c70f19d5a0, display=0x55c70f19d4d0) at ../wayland-1.21.0/src/wayland-client.c:1741 #22 wl_display_dispatch_queue_pending (display=0x55c70f19d4d0, queue=0x55c70f19d5a0) at ../wayland-1.21.0/src/wayland-client.c:1983 #23 0x00007fad78522bb6 in QtWaylandClient::QWaylandDisplay::flushRequests() (this=<optimized out>) at /usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddisplay.cpp:253 #24 0x00007fad7e8b1bb0 in QObject::event(QEvent*) (this=0x55c70f167c00, e=0x7fad68004df0) at kernel/qobject.cpp:1347 #25 0x00007fad7e88df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55c70f167c00, event=0x7fad68004df0) at kernel/qcoreapplication.cpp:1064 #26 0x00007fad7e88dfb3 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1462 #27 0x00007fad7e88ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55c70f194400) at kernel/qcoreapplication.cpp:1821 #28 0x00007fad7e8d4e88 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55c70f1a9420) at kernel/qeventdispatcher_glib.cpp:277 #29 0x00007fad7d51682b in g_main_dispatch (context=0x7fad70005010) at ../glib/glib/gmain.c:3454 #30 g_main_context_dispatch (context=0x7fad70005010) at ../glib/glib/gmain.c:4172 #31 0x00007fad7d56dcc9 in g_main_context_iterate.constprop.0 (context=0x7fad70005010, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4248 #32 0x00007fad7d5150e2 in g_main_context_iteration (context=0x7fad70005010, may_block=1) at ../glib/glib/gmain.c:4313 #33 0x00007fad7e8d8c8f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55c70f173480, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #34 0x00007fad7e8866ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7fffcd196f20, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #35 0x00007fad7e891219 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #36 0x00007fad7ed39fe2 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1870 #37 0x000055c70dff955b in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/powerdevil/powerdevil-5.27.2/daemon/powerdevilapp.cpp:178 Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: LENOVO Product Name: 20XYCTO1WW System Version: ThinkPad X1 Yoga Gen 6
I don't have any crashes when using X11.
Not sure but sounds very similar to my case, Powerdevil works for me too on X11, problem occurs on Wayland when HDMI signal is lost.
Good chance this is fixed with https://invent.kde.org/plasma/libkscreen/-/commit/00d8e90f821123f04fcb7ea39724a1f221a76f37 in Plasma 5.27.3. Can you test again with that once it's released? Or even better, by applying it as a patch on top of your libkscreen package if you're able to build software or packages from source. That would be awesome!
That patch doesn't fix the issue for me, I can still get a crash every time I plug or unplug the laptop from the docking station.
Darn. The same crash, or a different one?
*** Bug 466697 has been marked as a duplicate of this bug. ***
(In reply to Iyán Méndez Veiga from comment #7) > I don't have any crashes when using X11. I've hit them with X11 (and not Wayland) in a KVM guest. Ref: Bug 466697
(In reply to Nate Graham from comment #11) > Darn. The same crash, or a different one? Well, it's hard to tell. I have constant crashes from kded5, org_kde_powerdevil, kscreen_osd_service and drkonqi after the update. But the particular bt I pasted before it was still the same after applying the patch.
Same on my side... https://pastebin.com/Ci5vXAWY
I have good news! I just installed the new kernel 6.2.2, and with this version the Powedevil problem is solved, at least for me in Wayland, which was where it crashed! I hope it works for others too. Going through the kernel changelog, I can only find these reviews that I see that may have had something to do with it: commit 83d403e773a851c9447e4d1847a6f1df91604d43 Author: Stylon Wang <stylon.wang@amd.com> Date: Tue Jan 10 14:38:33 2023 +0800 drm/amd/display: Properly reuse completion structure commit 0cf8307adbc6beb5ff3b8a76afedc6e4e0b536a9 upstream. [Why] Connecting displays to TBT3 docks often produces invalid replies for DPIA AUX requests. It turns out the completion structure was not re-initialized before reusing it, resulting in immature wake up to completion. [How] Properly call reinit_completion() on reused completion structure. Cc: stable@vger.kernel.org Reviewed-by: Solomon Chiu <solomon.chiu@amd.com> Acked-by: Alan Liu <HaoPing.Liu@amd.com> Signed-off-by: Stylon Wang <stylon.wang@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: "Limonciello, Mario" <mario.limonciello@amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> commit 9c591e6a027053460b61d63c239df4391fbce98f Author: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> Date: Mon Jan 23 14:59:28 2023 -0500 drm/amd/display: Move DCN314 DOMAIN power control to DMCUB commit e383b12709e32d6494c948422070c2464b637e44 upstream. [Why] DOMAIN power gating control is now required to be done via firmware due to interlock with other power features. This is to avoid intermittent issues in the LB memories. [How] If the firmware supports the command then use the new firmware as the sequence can avoid potential display corruption issues. The command will be ignored on firmware that does not support DOMAIN power control and the pipes will remain always on - frequent PG cycling can cause the issue to occur on the old sequence, so we should avoid it. Reviewed-by: Hansen Dsouza <hansen.dsouza@amd.com> Acked-by: Qingqing Zhuo <qingqing.zhuo@amd.com> Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> commit 8417e002b7165bdde96ef6af48708ad8de6fe194 Author: Thomas Weißschuh <linux@weissschuh.net> Date: Mon Feb 20 06:46:12 2023 +0000 vc_screen: don't clobber return value in vcs_read commit ae3419fbac845b4d3f3a9fae4cc80c68d82cdf6e upstream. Commit 226fae124b2d ("vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF") moved the call to vcs_vc() into the loop. While doing this it also moved the unconditional assignment of ret = -ENXIO; This unconditional assignment was valid outside the loop but within it it clobbers the actual value of ret. To avoid this only assign "ret = -ENXIO" when actually needed. [ Also, the 'goto unlock_out" needs to be just a "break", so that it does the right thing when it exits on later iterations when partial success has happened - Linus ] Reported-by: Storm Dragon <stormdragon2976@gmail.com> Link: https://lore.kernel.org/lkml/Y%2FKS6vdql2pIsCiI@hotmail.com/ Fixes: 226fae124b2d ("vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF") Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Link: https://lore.kernel.org/lkml/64981d94-d00c-4b31-9063-43ad0a384bde@t-8ch.de/ Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> I don't know if any of these fixes could really solve the problem, but it's the only thing I see that makes any sense related to the Powerdevil problem. Now I only have to solve the KDE problems with the HDMI, if one day I get it....
Sorry, not true, the new kernel doesn't fix the Powerdevil problem... I explain what has happened. I have a bi-directional EDID emulator connected to the HDMI output. This small connector is used to fool the computer into thinking that it is still receiving the HDMI signal from the monitor even if the HDMI cable is disconnected or other computer is active on a KVM switch. It is mainly used with KVM switches since it allows you to switch between computers instantly since it does not have to recover or readapt the video signal on the monitor when you change computers since the EDID emulator has it saved. It also has another function and that is to be able to use the computer with the monitor disconnected for remote control sessions with applications such as VNC, AnyDesk, etc. That's why the test worked for me, because I didn't realize when I did it that I had this little connector connected and then even if I changed the computer on the KVM switch, the Powerdevil continued to detect the HDMI signal and that's why it didn't fail. You can buy one of these plugs, it will solve the problem of the Powerdevil and they are not expensive at all. What is clear with this test is that the failure is in the interruption of the HDMI signal, at the moment it is cut, the Powerdevil crashes. If the EDID emulator is connected and the computer is still receiving a 'ghost' HDMI signal (provided by the EDID emulator), the Powerdevil does not fail and you can switch between computers without problem. What is certain is that with this version of the kernel one of the errors that it had has been fixed. With the version prior to 6.2.2, if the KDE + Wayland computer was suspended while having the bi-directional EDID emulator, switched to the Windows computer, and then went back to the Linux computer and woke it up, the KDE + Wayland session was completely locked and it was impossible to recover it (in X11 it worked fine). After installing kernel 6.2.2 now this problem in Wayland seems to be fixed.
*** This bug has been marked as a duplicate of bug 466181 ***