Bug 466697

Summary: Permanent crashes of Powerdevil at launch in a VNC session
Product: [Plasma] Powerdevil Reporter: Laurent Mirguet <laurent>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: aleixpol, kde, me, nate, tagwerk19
Priority: NOR    
Version: 5.27.2   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: logs from journalctl

Description Laurent Mirguet 2023-03-02 08:40:36 UTC
Created attachment 156909 [details]
logs from journalctl

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

The powerdevil process crashes at launch... and restart permanently. This generates gigabytes of logs. And I don"t know how to disable powerdevil completely (as I don't think I need it).

I'm using KDE in a Tigervnc session, on an always-on server.
Version is 5.27.2.
X server is Xvnc (Tigervnc version)

One of the main messages I received is : org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"

Attached are my logs from journalctl
Comment 1 David Edmundson 2023-03-02 09:51:56 UTC
Pasting inline:

           Stack trace of thread 10809:
                                         #0  0x00007fb5b0aafe5c __pthread_kill_implementation (libc.so.6 + 0x8ce5c)
                                         #1  0x00007fb5b0a5fa76 raise (libc.so.6 + 0x3ca76)
                                         #2  0x00007fb5b0a497fc abort (libc.so.6 + 0x267fc)
                                         #3  0x00007fb5b0cd7e80 _ZSt21__glibcxx_assert_failPKciS0_S0_ (libstdc++.so.6 + 0xd7e80)
                                         #4  0x00007fb58f386347 _ZNK7KScreen4Dpms11isSupportedEv (libKF5ScreenDpms.so.8 + 0x9347)
                                         #5  0x00007fb5b1f8136f _ZN10PowerDevil10ActionPool4initEPNS_4CoreE (libpowerdevilcore.so.2 + 0x1736f)
                                         #6  0x00007fb5b1f88ded _ZN10PowerDevil4Core14onBackendReadyEv (libpowerdevilcore.so.2 + 0x1eded)
                                         #7  0x00007fb5b12d0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96)
                                         #8  0x00007fb59c248afa _ZN23PowerDevilUPowerBackend18initWithBrightnessEb (powerdevilupowerbackend.so + 0x12afa)
                                         #9  0x00007fb5b12d0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96)
                                         #10 0x00007fb59c23ff53 _ZN23PowerDevilUPowerBackend24brightnessSupportQueriedEb (powerdevilupowerbackend.so + 0x9f53)
                                         #11 0x00007fb5b12d0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96)
                                         #12 0x00007fb5b1e003d9 _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x5e3d9)
                                         #13 0x00007fb5b1e05e3b _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x63e3b)
Comment 2 tagwerk19 2023-03-02 17:32:11 UTC
I see the same in a couple of 'just updated' F37 systems (KVM guests). A crash dump every 6 or so seconds. I'll see if I can compare details.

Would be nice to know how to stop it :-)

I haven't found "an obvious way" of disabling the service; nothing in the System Settings > Startup and Shutdown > Autostart or Background services.

Seems to happen when I log in with X11, seems OK with Wayland

Flagging Confirmed (although in my case not via VNC), I think as this is a seemingly indefinite crash loop it's worth a HI importance...
Comment 3 Aleix Pol 2023-03-02 17:40:03 UTC

*** This bug has been marked as a duplicate of bug 466181 ***
Comment 4 Nate Graham 2023-03-02 17:43:44 UTC

*** This bug has been marked as a duplicate of bug 466620 ***
Comment 5 tagwerk19 2023-03-02 17:59:25 UTC
(In reply to tagwerk19 from comment #2)
> I'll see if I can compare details.
Cut and Paste from journalctl

Stack trace of thread 2858:
    #0  0x00007f34db019e5c __pthread_kill_implementation (libc.so.6 + 0x8ce5c)
    #1  0x00007f34dafc9a76 raise (libc.so.6 + 0x3ca76)
    #2  0x00007f34dafb37fc abort (libc.so.6 + 0x267fc)
    #3  0x00007f34da6d7e80 _ZSt21__glibcxx_assert_failPKciS0_S0_ (libstdc++.so.6 + 0xd7e80)
    #4  0x00007f34c4e71347 _ZNK7KScreen4Dpms11isSupportedEv (libKF5ScreenDpms.so.8 + 0x9347)
    #5  0x00007f34dba7a36f _ZN10PowerDevil10ActionPool4initEPNS_4CoreE (libpowerdevilcore.so.2 + 0x1736f)
    #6  0x00007f34dba81ded _ZN10PowerDevil4Core14onBackendReadyEv (libpowerdevilcore.so.2 + 0x1eded)
    #7  0x00007f34dacd0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96)
    #8  0x00007f34c5d1eafa _ZN23PowerDevilUPowerBackend18initWithBrightnessEb (powerdevilupowerbackend.so + 0x12afa)
    #9  0x00007f34dacd0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96)
    #10 0x00007f34c5d15f53 _ZN23PowerDevilUPowerBackend24brightnessSupportQueriedEb (powerdevilupowerbackend.so + 0x9f53)
    #11 0x00007f34dacd0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96)
     ...

Plasma: 5.27.2
Frameworks: 5.103.0
QT: 5.15.8
Kernel: 6.1.14.200.fc37.x86_64 (64-bit)
Comment 6 tagwerk19 2023-03-03 07:04:44 UTC
(In reply to tagwerk19 from comment #2)
> ... a couple of 'just updated' F37 systems (KVM guests) ...
Crashes (in X11) if the VM has the QXL video. Switch to Virtio and it goes away...

I think the crashes are independent of the:
    ... org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
At least, I get that message whether starting with QXL or Virtio
Comment 7 tagwerk19 2023-03-04 07:28:41 UTC
Possibly should be reopened as it affects a different group of systems (X11 and not Wayland, there's a backtrace included in Bug 466808)...
Comment 8 Nate Graham 2023-03-06 16:25:51 UTC

*** This bug has been marked as a duplicate of bug 466181 ***
Comment 9 Laurent Mirguet 2023-03-19 16:06:29 UTC
I confirm that this is fixed with Plasma 5.27.3

Thank you very much!
Comment 10 Nate Graham 2023-03-27 18:39:07 UTC
Yay, thanks for following up!