Hello
after my notebook shut down (due to a low battery) when I was just using Knetworkmanager to add a new W-LAN connection, I can’t start Knetworkmanager anymore. Terminal output is:
~> knetworkmanager
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
KCrash: Application 'knetworkmanager' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/home/carsta/.kde4/socket-linux-gddt.site/kdeinit4__0
knetworkmanager(7583): Communication problem with "knetworkmanager" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.knetworkmanager was not provided by any .service files" "
Networkmanager is still working. Reinstallation of all (K)Networkmanager packages via Yast did not help.
I suggest that you try these two commands to see if this might be the problem. Open up a terminal session as a normal user and run these two sudo commands that will ask for the root user password. If you run them in close succession, you will only enter the root password once.
It still doesn’t work, terminal output for knetworkmanager now is:
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
KCrash: Application 'knetworkmanager' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/home/carsta/.kde4/socket-linux-gddt.site/kdeinit4__0
Thanks Carsta, it worked for me. However it deleted all my wireless connections, which was no big deal in this case. I simply added the local one and got reconnected.
[DELL Inspiron 6000, running SUSE 11.3 x86_32]. A friend has the same setup and reports the same problem - recurring from time to time. It can be invoked by closing the lid when SUSE is running or is shutting down. Perhaps the SUSE team can take steps to ensure the above files are not corrupted during power management actions?