Application: org_kde_powerdevil (5.27.0) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.11-200.fc37.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 37 (Workstation Edition) DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: The relevant stack trace/dump is attached. I haven't done anything different or special compared to what I used to do in the previous revision. The only "unique" thing that I'm doing is logging in remotely via x2go to a "x" plasma session. Thx much! Brendan The crash can be reproduced every time. -- Backtrace: Application: KDE Power Management System (org_kde_powerdevil), signal: Aborted [KCrash Handler] #4 0x00007fb002eafe5c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x00007fb002e5fa76 in raise () at /lib64/libc.so.6 #6 0x00007fb002e497fc in abort () at /lib64/libc.so.6 #7 0x00007fb0030d7e80 in __gnu_debug::_Safe_sequence_base::_M_get_mutex() () at /lib64/libstdc++.so.6 #8 0x00007fafe96c3d37 in () at /lib64/libKF5ScreenDpms.so.8 #9 0x00007fb0042b436f in PowerDevil::ActionPool::init(PowerDevil::Core*) () at /lib64/libpowerdevilcore.so.2 #10 0x00007fb0042bbded in PowerDevil::Core::onBackendReady() () at /lib64/libpowerdevilcore.so.2 #11 0x00007fb0036d0e96 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #12 0x00007fafea56eada in PowerDevilUPowerBackend::initWithBrightness(bool) () at /usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so #13 0x00007fb0036d0e96 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #14 0x00007fafea565fd3 in PowerDevilUPowerBackend::brightnessSupportQueried(bool) () at /usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so #15 0x00007fb0036d0e96 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #16 0x00007fb0041333d9 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #17 0x00007fb004138e3b in KJob::finishJob(bool) () at /lib64/libKF5CoreAddons.so.5 #18 0x00007fb0036d0e96 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #19 0x00007faff002a863 in KAuth::DBusHelperProxy::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.0] () at /usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so #20 0x00007faff002af41 in KAuth::DBusHelperProxy::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so #21 0x00007fb0040670bb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector<int> const&, int) () at /lib64/libQt5DBus.so.5 #22 0x00007fb0036c8134 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #23 0x00007fb00369d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #24 0x00007fb0036a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #25 0x00007fb0036eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #26 0x00007fb002119cbf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #27 0x00007fb00216f598 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #28 0x00007fb002116f40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #29 0x00007fb0036ee5fa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #30 0x00007fb00369bf3a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #31 0x00007fb0036a4002 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #32 0x0000564847437a45 in main () [Inferior 1 (process 1069144) detached] Reported using DrKonqi
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #8 0x00007fafe96c3d37 in () at /lib64/libKF5ScreenDpms.so.8 Could you please install debug symbols for kscreen, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks again!
Actually looks like it's Bug 466181, which was just fixed today. *** This bug has been marked as a duplicate of bug 466181 ***