https://bugs.kde.org/show_bug.cgi?id=453931
--- Comment #3 from Nicolas Fella <nicolas.fe...@gmx.de> --- What seems to happen is that the ksystemstats DBus service disappears, which sets off a chain of events that eventually leads to this crash #17 0x00007f2501d0bdf5 in QDBusServiceWatcher::serviceUnregistered (this=<optimized out>, _t1=...) at .moc/moc_qdbusservicewatcher.cpp:235 leads to #13 KSysGuard::SensorDaemonInterface::reconnect (this=0x7f24f816d070 <KSysGuard::SensorDaemonInterface::instance()::instance>) at /usr/src/debug/libksysguard5-5.24.5-1.2.x86_64/sensors/SensorDaemonInterface.cpp:41 leads to #8 0x00007f2501d0ddb3 in QDBusConnectionPrivate::signalNeedsConnecting (this=this@entry=0x7f24ec004e80, _t1=..., _t2=...) at .moc/moc_qdbusconnection_p.cpp:357 leads to #11 0x00007f2501cc6eeb in QDBusConnectionPrivate::addSignalHook (this=0x7f24ec004e80, key=..., hook=...) at qdbusintegrator.cpp:2298 leads to #10 QDBusConnectionPrivate::getNameOwnerNoCache (this=this@entry=0x7f24ec004e80, serviceName=...) at qdbusintegrator.cpp:2563 which is where it goes wrong in Qt code. But no idea what exactly is wrong there. Manually killing systemstats doesn't make anything crash here -- You are receiving this mail because: You are watching all bug changes.
