Version: 4.6 (using KDE 4.6.3) OS: Linux After selecting the wicd backend kded4 crashes with the following output: carlos@io ~ $ kded4 ntrack backend selected and created: ntrack-libnl1.so Object::connect: No such signal WicdNetworkManager::wwanEnabledChanged(bool) Object::connect: No such signal WicdNetworkManager::wwanHardwareEnabledChanged(bool) KCrash: Attempting to start /usr/bin/kded4 from kdeinit sock_file=/home/carlos/.kde4/socket-io/kdeinit4__0 kded(4217): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " KCrash: Application 'kded4' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/arlos/.kde4/socket-io/kdeinit4__0 QSocketNotifier: Invalid socket 14 and type 'Read', disabling... I might get you a backtrace if it's needed (just that I need to rebuild everything.) Reproducible: Always
I suspect the pre-0.9 nm bump is the cause of this. Removing kdeplasma-applets-networkmanagement and subsequently networkmanager fixed this for me.
I can confirm that removing networkmanager and its plasmoid solves the crash. What do I need to delete to reset NM so that I can reinstall it?
The error reads like the wicd backend needs to be updated for the new nm abi. If so, you should be able to restore nm by downgrading it to a real 0.8 version.
I'm afraid that makes no sense to me, how Wicd depends on NetworkManager in any way?
not wicd itself, but the solid backend (WicdNetworkManager:: is defined there).
Ok, I don't quite follow but I'll do it for now.
Is this still happening?