Bug 436340 - KDE Power management system crashes on screen sleep
Summary: KDE Power management system crashes on screen sleep
Status: RESOLVED UPSTREAM
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.21.4
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-29 07:27 UTC by olav.d.stornes
Modified: 2021-12-03 15:16 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Related crash log (1.83 KB, text/vnd.kde.kcrash-report)
2021-04-29 07:27 UTC, olav.d.stornes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description olav.d.stornes 2021-04-29 07:27:35 UTC
Created attachment 137998 [details]
Related crash log

SUMMARY
When idle for a few minutes (when "Dim screen" should be triggered), a crash notification is shown and the screen stays on. This also happens if i have locked the desktop 

When not logged in, the screen dims as expected.

STEPS TO REPRODUCE
1. Log into pc
2. Wait for the screen to dim
3. Receive a crash

OBSERVED RESULT
Screen stays on for an indefinite time

EXPECTED RESULT
Screen should dim

SOFTWARE/OS VERSIONS
EndeavourOS: 5.11.16-zen1-1-zen 
(available in About System)
KDE Plasma Version: 5.21.4 
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

I've attempted to downgrade powerdevil to 5.21.2, which did not solve it.
Comment 1 Nate Graham 2021-04-30 16:00:27 UTC
Application: KDE Power Management System (org_kde_powerdevil), signal: Aborted

[KCrash Handler]
#4  0x00007f4998477ef5 in raise () at /usr/lib/libc.so.6
#5  0x00007f4998461862 in abort () at /usr/lib/libc.so.6
#6  0x00007f4998461747 in _nl_load_domain.cold () at /usr/lib/libc.so.6
#7  0x00007f4998470646 in  () at /usr/lib/libc.so.6
#8  0x00007f4990a47c57 in  () at /usr/lib/libddcutil.so.4
#9  0x00007f4990a3c530 in ddca_open_display2 () at /usr/lib/libddcutil.so.4
#10 0x00007f4991e03855 in  () at /usr/lib/qt/plugins/kf5/powerdevil/powerdevilupowerbackend.so
#11 0x00007f4991e04622 in  () at /usr/lib/qt/plugins/kf5/powerdevil/powerdevilupowerbackend.so
#12 0x00007f4998ad29e6 in  () at /usr/lib/libQt5Core.so.5
#13 0x00007f4998ad6a7b in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
#14 0x00007f4998ac80cf in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#15 0x00007f4998a9b68a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#16 0x00007f4998af3515 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5
#17 0x00007f4998af3dc2 in  () at /usr/lib/libQt5Core.so.5
#18 0x00007f4996aad02c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#19 0x00007f4996b00b59 in  () at /usr/lib/libglib-2.0.so.0
#20 0x00007f4996aaa781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#21 0x00007f4998af4191 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#22 0x00007f4998a99fec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#23 0x00007f4998aa24a4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#24 0x000055f12e2c71eb in  ()
#25 0x00007f4998462b25 in __libc_start_main () at /usr/lib/libc.so.6
#26 0x000055f12e2c725e in _start ()
[Inferior 1 (process 2213) detached]
Comment 2 Nate Graham 2021-04-30 16:01:52 UTC
Seems like it is crashing in ddcutil:

> #9  0x00007f4990a3c530 in ddca_open_display2 () at /usr/lib/libddcutil.so.4
I would recommend reporting this to the developers at https://github.com/rockowitz/ddcutil/issues
Comment 3 olav.d.stornes 2021-04-30 21:44:55 UTC
(In reply to Nate Graham from comment #2)

Thanks you for answering. I will investigate further towards ddcutil
Comment 4 dvogel 2021-05-03 14:14:03 UTC
(In reply to Nate Graham from comment #2)
> Seems like it is crashing in ddcutil:
> 
> > #9  0x00007f4990a3c530 in ddca_open_display2 () at /usr/lib/libddcutil.so.4
> I would recommend reporting this to the developers at
> https://github.com/rockowitz/ddcutil/issues

If the implementation is still in the state I did it back then, there's a big chance ddcutil's API evolved... I unfortunately don't really have the time to update this right now.