[kde 4.6] dbus issues and plasma crashes

anish · 2011-01-28 04:02:07

my kdm.log is full of
klauncher(6730) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(6724)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"

When dbus is running fine. Also, I get guaranteed plasma crash when I logout/shutdown. soprano did not fix anything for me

panosk · 2011-01-28 08:47:12

Right after the update, I had some crashes too when I logged in/logged out. Try any or all of these:

- Open the Session Management module from Startup and Shutdown in System Settings and check the option "Start with empty session" on the "On Login" section.
- Check your rc.conf and make sure you have dbus in your daemons array. You can also delete the hal entry from this array.
- Uninstall any plasmoids you have installed from aur or elsewhere
- Follow the announcement recommendation and delete ~/.kde4 /tmp/kde-* and /var/tmp/kdecache-*.
- Delete all plasma-related files (~/.kde4/share/config/plasma*)
- Overwrite kdmrc with kdmrc.pacnew (you will find them in /usr/share/config/kdm/). In that case, you' ll have to reconfigure your login screen theme or other customizations you've done.

ilpianista · 2011-01-28 09:58:01

great TODO list panosk, but I think that a rebuild of extra-plasmoid should be fine

panosk · 2011-01-28 10:51:31

bash wrote:

great TODO list panosk, but I think that a rebuild of extra-plasmoid should be fine

Well, in my case, it wasn't enough. Some plasmoids from the extragear package in aur were constantly crashing plasma, so I rebuilt it. However, I was still getting some random crashes on log in/log out, so I tried all of the above until crashes had gone

drm00 · 2011-01-28 13:44:31

I have the same issue (even when I'm logged in with a completely new user):

$ tail -4 /var/log/kdm.log
klauncher(3382) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(3343)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"

At the same time, dbus-daemon takes 50% of my cpu and nepomukserver takes ~35%:

 PID  USER  ~ %CPU %MEM TIME+ COMMAND                                                                                                                
 3493 lol ~ 50.4  0.1 5:48.96 dbus-daemon                                                                                                            
 3733 lol ~ 36.5  0.5 4:16.65 nepomukserver

I don't know what to do, is there some config-file in /usr that has changed? Should I delete all files from /usr/share/config?

Regards,
drm

panosk · 2011-01-28 13:55:10

drm00 wrote:

I have the same issue (even when I'm logged in with a completely new user):

$ tail -4 /var/log/kdm.log
klauncher(3382) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(3343)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"

Well, just checked and I have the same entries in kdm.log....

At the same time, dbus-daemon takes 50% of my cpu and nepomukserver takes ~35%:
 PID  USER  ~ %CPU %MEM TIME+ COMMAND                                                                                                                
 3493 lol ~ 50.4  0.1 5:48.96 dbus-daemon                                                                                                            
 3733 lol ~ 36.5  0.5 4:16.65 nepomukserver
I don't know what to do, is there some config-file in /usr that has changed? Should I delete all files from /usr/share/config?
Regards,
drm

On the other hand, the dbus and nepomukserver problem went away with the latest soprano update.

anish · 2011-01-28 18:32:05

Will try all of that out. I also noticed that using flip switch for alt+tab causes some screen corruption, and ends up with desktop effects being suspended. I see this in dmesg:
Jan 28 00:05:43 cerveza kernel: NVRM: Xid (0001:00): 13, 0003 00000000 00008597 00001b0c 1000f010 00000040

I'm using nvidia 260.19.36-2 on a static 2.6.37 kernel, those are the only 2 packages on my system from testing (besides nvidia-utils) o'course

Last edited by anish (2011-01-29 05:23:27)

anish · 2011-01-29 05:24:46

Nope, none of that made any difference for me. Any else notice their .xsession-errors full of random stuff ?

lynix · 2011-02-01 16:15:50

I'm having the same trouble (no login possible, "No DBUS session-bus found"). Interesting thing is that I don't run KDE - I'm using awesome (and kdm just for login).
So I think plasmoid settings etc. can't cause the error...

Ah and yes, my .xsession-errors is very verbose, but I'm used to that (never understood why KDE applications drop so much debugging info).

Last edited by lynix (2011-02-01 16:17:42)

anish · 2011-02-01 23:16:07

the plasma issue just got fixed in tip. https://bugs.kde.org/show_bug.cgi?id=264076
Flip switch issue being tracked at https://bugs.kde.org/show_bug.cgi?id=261323

@lynix login might be a different issue, I have no trouble logging in.

Arch Linux

#1 2011-01-28 04:02:07

[kde 4.6] dbus issues and plasma crashes

#2 2011-01-28 08:47:12

Re: [kde 4.6] dbus issues and plasma crashes

#3 2011-01-28 09:58:01

Re: [kde 4.6] dbus issues and plasma crashes

#4 2011-01-28 10:51:31

Re: [kde 4.6] dbus issues and plasma crashes

#5 2011-01-28 13:44:31

Re: [kde 4.6] dbus issues and plasma crashes

#6 2011-01-28 13:55:10

Re: [kde 4.6] dbus issues and plasma crashes

#7 2011-01-28 18:32:05

Re: [kde 4.6] dbus issues and plasma crashes

#8 2011-01-29 05:24:46

Re: [kde 4.6] dbus issues and plasma crashes

#9 2011-02-01 16:15:50

Re: [kde 4.6] dbus issues and plasma crashes

#10 2011-02-01 23:16:07

Re: [kde 4.6] dbus issues and plasma crashes

Board footer