As the title says: Each time I boot up my laptop (ASUS N61jv, Tumbleweed) the kded5 crashes. I cannot automatically report this crash since no address has been registered for this program that would allow this (used to work in plasma 4). Is this a known issue? How can I get rid of this?
**i | **kactivities5 | KDE Plasma Activities support | Paket
**i | **kactivities5-devel | KDE Plasma Activities support | Paket
**i | **kactivities5-imports | KDE Plasma Activities support | Paket
**i | **libkactivities6 | Development files and headers for kactivities | Paket
Application: kded5 (kded5), signal: Segmentation fault
Using host libthread_db library “/lib64/libthread_db.so.1”.
[Current thread is 1 (Thread 0x7f573ed92780 (LWP 1762))]
Thread 2 (Thread 0x7f5731d5f700 (LWP 1763)): #0 0x00007f573e6ed4cd in poll () at /lib64/libc.so.6 #1 0x00007f573877a322 in () at /usr/lib64/libxcb.so.1 #2 0x00007f573877bdef in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x00007f57342b2c69 in () at /usr/lib64/qt5/plugins/platforms/libqxcb.so #4 0x00007f573c27f9ef in () at /usr/lib64/libQt5Core.so.5 #5 0x00007f573bc40484 in start_thread () at /lib64/libpthread.so.0 #6 0x00007f573e6f5a4d in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7f573ed92780 (LWP 1762)):
[KCrash Handler] #5 0x00007f57253fd790 in () #6 0x00007f573c269dc3 in QInternal::activateCallbacks(QInternal::Callback, void**) () at /usr/lib64/libQt5Core.so.5 #7 0x00007f573c459fa2 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #8 0x00007f573c49196e in QObjectPrivate::setParent_helper(QObject*) () at /usr/lib64/libQt5Core.so.5 #9 0x00007f573c491f10 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5 #10 0x00007f573c496679 in QSocketNotifier::~QSocketNotifier() () at /usr/lib64/libQt5Core.so.5 #11 0x00007f573cd9ead7 in () at /usr/lib64/libQt5DBus.so.5 #12 0x00007f5739eb2013 in () at /lib64/libdbus-1.so.3 #13 0x00007f5739eb074e in () at /lib64/libdbus-1.so.3 #14 0x00007f5739eb07c9 in () at /lib64/libdbus-1.so.3 #15 0x00007f5739eafc57 in () at /lib64/libdbus-1.so.3 #16 0x00007f5739e9baa2 in () at /lib64/libdbus-1.so.3 #17 0x00007f573cd99ba2 in () at /usr/lib64/libQt5DBus.so.5 #18 0x00007f573cd90e92 in () at /usr/lib64/libQt5DBus.so.5 #19 0x00007f573cd90f19 in () at /usr/lib64/libQt5DBus.so.5 #20 0x00007f573e644c39 in __run_exit_handlers () at /lib64/libc.so.6 #21 0x00007f573e644c85 in () at /lib64/libc.so.6 #22 0x00007f573d927c10 in KDBusService::KDBusService(QFlags<KDBusService::StartupOption>, QObject*) () at /usr/lib64/libKF5DBusAddons.so.5 #23 0x00007f573e9bc244 in kdemain(int, char**) (argc=1, argv=0x7fff28c2de08) at /usr/src/debug/kded-5.10.0/src/kded.cpp:799 #24 0x00007f573e62f8c5 in __libc_start_main () at /lib64/libc.so.6 #25 0x00000000004007f9 in _start () at …/sysdeps/x86_64/start.S:118
What does that mean exactly?
It runs if you run it a second time?
What is quite unexpected is kdeinit4. Isn’t that supposed to be replaced?
No. That’s part of kdelibs4, which you need for running any KDE4 application.
But you probably shouldn’t have polkit-kde-authentication-agent-1 (that’s the KDE4 version). Uninstall that and install polkit-kde-authentication-agent-5 instead.
The crash could be caused by some kded module (powerdevil e.g.) requesting polkit privileges.
I meant (speculation): If the QObject in the stacktrace is in a valid state, then the issue could come from Thread 1 and Thread 2 accessing a shared resource via the callback at the end of the stacktrace. In that case that access would be lacking a mutex lock resp. a std::lock_guard.
But your hint regarding the polkit agent sounds like a good idea. I’ll try that. But it is strange that it is even on the system as this has been a install from the plasma5 switch snapshot of TW and I certainly did not install it by hand…
You actually do have polkit-kde-authorication-agent-5 installed. The path of the command is /usr/lib64/libexec, which is the KF5 version (the KDE4 version is installed to /usr/lib64/kde4/libexec). Sorry I haven’t looked good enough…
And on second thought it should not matter at all. Even the KDE4 version should work fine with Plasma5, I had that setup for months…
kded4 or kdeinit4 running should not cause any problem either. Although it should probably not be running right after login, especially if it is a clean session.
I have to say that I have no further idea at the moment other than the “zypper dup”.
You suggested that I try to create a whole new account and check if it works. Just that you know: I recycled the /home/<user> directory. Could that cause the problem (with old config files lying around)?
So at least it is a user-specific problem.
Since it is kded5 that’s crashing, I would start with removing ~/.config/kded5rc, and wiping out ~/.cache/ should not cause any harm either. That contains KF5’s system cache of installed .desktop files and plugins, including kded modules.
Interesting aside: Susegreeter wanted to introduce me to KDE4…
Yeah. The text has not been changed yet in KF5’s SuSEgreeter.