Need some assistance diagnosing a kded/plasma crash on logon
Tags:
None
Registered Member 
|
Ok, that makes sense  I wasn't seeing the LDAP references, but the traces all look very similar to me (and I'd been through a lot of them prior to posting here, without much luck in finding patterns). It was all blurring together a bit
|
Administrator
|
The output indicates that the system bus is severing the connection of KDE applications when they attempt to make queries to system services.
Of note, this is occurring with UDisks and UPower. I strongly suspect this is also happening with the Network Management code (which will be attempting to communicate with NetworkManager). That could explain the crashes. Can you please check system logs (likely in /var/log, although if this is a systemd system you may need to use the relevant journald tools as well) to see if the system bus is giving any reason for why it is doing this?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
[quote="bcooksley"]The output indicates that the system bus is severing the connection of KDE applications when they attempt to make queries to system services.
Of note, this is occurring with UDisks and UPower. I strongly suspect this is also happening with the Network Management code (which will be attempting to communicate with NetworkManager). That could explain the crashes. Can you please check system logs (likely in /var/log, although if this is a systemd system you may need to use the relevant journald tools as well) to see if the system bus is giving any reason for why it is doing this?[/quote] I'm not seeing anything useful here - I've got system logs for two scenarios, the first is booting from an ISO in a VM (virtualbox), and the other is a PXE Booted image. Names have been changed to protect the innocent... VM syslog:
PXE Boot
|
|
Apr 3 08:54:06 ubuntu whoopsie[1712]: Could not get the Network Manager state:
Apr 3 08:54:06 ubuntu whoopsie[1712]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Apr 3 00:53:43 ubuntu ck-launch-session: error connecting to ConsoleKit Apr 3 00:53:45 ubuntu pulseaudio[2396]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Open a konsole, run "qdbus --system" and check the output (can you access the system bus at all and is there a networkmanager service?) Could you run "plasma-desktop" at this later point btw.? |
|
Registered Member
|
Hi, sorry for the late reply again, got a bit swamped last week - here's the output
|
|
You cannot connect to the system bus -> major issue (affecting more than just KDE)
What's the output of
|
|
Registered Member
|
Is there a permission system associated with dbus? Cause it seems to be running:
For comparison, a working system (auto logged in as ubuntu/999 live user)
|
|
Administrator
|
Yes, there is a permission system associated with D-Bus. It's rules are usually located at /etc/dbus-1/. These directories should always be identical though.
Could you check system logs (/var/log/messages, etc) to see if anything from dbus-daemon is mentioned?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
apparently the working system invokes (the session) dbus via ck-launch, while the other doesn't, what matches
I assume Ubuntu moved from ConsoleKit to logind in that version? The session is the likely incorrectly started, trying ConsoleKit but would actually require logind.
|
|
Registered Member
|
You're talking well out of my depth of understanding what services ConsoleKit or logind actually provide in relation to authentication, but here's some output  On the problem machine:
On the working machine:
|
Bookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar
