Hallo Michael! Michael Biebl wrote:
> What kind of destkop enviroment do you use, Actual KDE 4 from SID > how do you start your X session? by standard KDM > Do you have a dbus session bus running (what's the output of ps aux | grep > dbus-daemon). Yes, of course: $ ps aux | grep dbus-daemon 104 1152 0.0 0.0 23644 1388 ? Ss 17:22 0:00 /usr/bin/dbus-daemon --system root 1408 0.0 0.0 23256 796 ? Ss 17:22 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session jo 1571 0.1 0.0 24164 1764 ? Ss 17:22 0:02 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session jo 2052 0.0 0.0 9604 888 pts/2 R+ 17:42 0:00 grep dbus- daemon My system has been running network-manager-kde successfully for some years now. I doubt that the problem might have something to to with recent libqt4 update from 4.6.2-5 to 4.6.3-1. However, a downgrade of related packages of libqt4-dbus to 4.6.2-5 now did not solve the problem. I need to check further, if you believe that it might help. > Do other apps using dbus work? Hmmm, how can I check this? I don't see any other problems on my computer, other than with knetworkmanager. > What's the output of ck-list-sessions? Session1: unix-user = '1000' realname = 'Jo' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2010-06-12T15:22:35.989951Z' login-session-id = '4294967295' Session2: unix-user = '0' realname = 'root' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/pts/1' remote-host-name = '' is-local = TRUE on-since = '2010-06-12T15:23:30.277546Z' login-session-id = '4294967295' idle-since-hint = '2010-06-12T15:24:03.002810Z' > Does it help, if you logout/login? No. Also manually restarting dbus, so $ /etc/init.d/dbus restart and/or restarting NetworkManager by $ /etc/init.d/network-manager and starting knetworkmanager results in the same error message: "Cannot find D-Bus ..." > I don't see severity grave justified so downgrading to appriopratly. Actually, I do see the severity grave since this bug renders the network- manager on kde unusable. Are you able to reproduce the bug? Or, can I provide further infos? Johannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org