Version: (using KDE 4.1.3) OS: Linux Installed from: SuSE RPMs opensuse 2.6.27.21-0.1-default x86_64 AMD Turion 64 X2 I got the following stack trace when resuming from a hibernate: Application: KDE Daemon (kded4), signal SIGSEGV 0x00007fd4fc69ecb0 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fd5027b7750 (LWP 3460))] Thread 1 (Thread 0x7fd5027b7750 (LWP 3460)): [KCrash Handler] #5 0x00007fd4ff9b5121 in QMetaObject::cast(QObject*) const () from /usr/lib64/libQtCore.so.4 #6 0x00007fd4ffcbaf31 in Solid::Device::asDeviceInterface(Solid::DeviceInterface::Type const&) const () from /usr/lib64/libsolid.so.4 #7 0x00007fd4f777bbd3 in HalPower::updateBatteryStats() () from /usr/lib64/kde4/solid_hal_power.so #8 0x00007fd4f7784960 in HalPower::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/kde4/solid_hal_power.so #9 0x00007fd4ff9c4454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #10 0x00007fd4ffcc2e33 in Solid::Battery::chargePercentChanged(int, QString const&) () from /usr/lib64/libsolid.so.4 #11 0x00007fd4ffcc3234 in Solid::Battery::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libsolid.so.4 #12 0x00007fd4ff9c4454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #13 0x00007fd4ffce1fa3 in ?? () from /usr/lib64/libsolid.so.4 #14 0x00007fd4ffce2804 in ?? () from /usr/lib64/libsolid.so.4 #15 0x00007fd4ffce29fe in ?? () from /usr/lib64/libsolid.so.4 #16 0x00007fd4ff9c4454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #17 0x00007fd4ffce9232 in ?? () from /usr/lib64/libsolid.so.4 #18 0x00007fd4ffce99f4 in ?? () from /usr/lib64/libsolid.so.4 #19 0x00007fd4ffce9b92 in ?? () from /usr/lib64/libsolid.so.4 #20 0x00007fd4ff4074cf in ?? () from /usr/lib64/libQtDBus.so.4 #21 0x00007fd4ff40e61f in ?? () from /usr/lib64/libQtDBus.so.4 #22 0x00007fd4ff9bf105 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #23 0x00007fd4fe8201bd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #24 0x00007fd4fe827f8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #25 0x00007fd501b8cd6b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #26 0x00007fd4ff9b0091 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #27 0x00007fd4ff9b0d3a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #28 0x00007fd4ff9d8863 in ?? () from /usr/lib64/libQtCore.so.4 #29 0x00007fd4fb2700fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #30 0x00007fd4fb2738cd in ?? () from /usr/lib64/libglib-2.0.so.0 #31 0x00007fd4fb273a8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #32 0x00007fd4ff9d84ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #33 0x00007fd4fe8b09bf in ?? () from /usr/lib64/libQtGui.so.4 #34 0x00007fd4ff9ae9a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #35 0x00007fd4ff9aeb2d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #36 0x00007fd4ff9b0ffd in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #37 0x00007fd5023c8742 in kdemain () from /usr/lib64/libkdeinit4_kded4.so #38 0x00007fd4fc61b586 in __libc_start_main () from /lib64/libc.so.6 #39 0x0000000000400859 in _start ()
4.1.3 is considered a bit old now. If you experience this regularly, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdebase4-runtime-debuginfo" and "kdebase4-workspace-debuginfo" packages. Thanks
Hi Dario Thanks for the info. I've upgraded to the latest KDE, please close this issue, I'll re-open it if it occurs again. Thanks Thom
Considering this one as fixed until Thom reopens if it occurs again. Reassigning to control::powermanager too as it was probably crashing in this component.