You are not logged in.
After quite some time, I decided to give KDE a look.
KDE itself seems to work ok, but I can't start any (really any) KDE app. Everything is crashing.
okular(23131)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
KCrash: Application 'okular' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinitkdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
KCrash: Application 'dolphin' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
drkonqi(23336): Unable to find an internal debugger that can work with the KCrash backend
KCrash: Application 'drkonqi' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
drkonqi(23341): Unable to find an internal debugger that can work with the KCrash backend
KCrash: Application 'drkonqi' crashing...Qt: 4.8.4
KDE: 4.10.2
Okular: 0.16.2
Dolphin: 2.2The first error message mentions problems with dbus, but the workaround suggested there does nothing and, as far as I can tell, dbus is working properly:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Di 2013-05-07 05:30:43 CEST; 12h ago
Main PID: 405 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─405 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activationecho $(dbus-launch)DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Z3CtnhWU6e,guid=37226391a01b45a8b99764f3518929ce DBUS_SESSION_BUS_PID=23976Anyway, when I log out (using KDM or lxdm, doesn't make a difference) and switch to some other WM/DM (tried Openbox, Fluxbox and Xfce4 so far), I can start Okular and Dolphin and all other kde apps without a problem. I can also run things like firefox, chromium, thunderbird or gvim in KDE, but nothing that comes with KDE.
I'm not sure how to debug this. D-Bus looks like the obvious culprit, but it's working ok as far as I can tell. I randomly reinstalled kdelibs and some of the misbehaving kde apps with the futile hope that this would fix itself, but well... I also found some rather old threads (2010-ish) which describe similar symptons. There the problem was Pulseaudio, but the suggested solution (installing phonon-xine and making it the default backend) doesn't work. phonon-xine doesn't compile here, as phonon-xine is a rather old, unmaintained AUR package. I kinda doubt that a KDE installation in 2013 still depends on that... right?
Am I missing something obvious?
Last edited by SleepyFloyd (2013-05-08 11:33:34)
Offline
What does "ps ax | grep dbus" in KDE show?
Last edited by lucke (2013-05-07 17:16:39)
Offline
dbus 405 0.0 0.0 18448 2476 ? Ss 05:30 0:05 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
sleepy 23215 0.0 0.0 17332 484 ? Ss 17:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 23220 0.0 0.0 17464 1160 ? Ss 17:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 23531 0.0 0.0 17448 1112 ? Ss 17:56 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 23954 0.0 0.0 17332 480 ? Ss 18:20 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 23976 0.0 0.0 17332 484 ? Ss 18:20 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 24161 0.0 0.0 17332 484 ? Ss 18:32 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 24199 0.0 0.0 17332 484 ? Ss 18:33 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 24204 0.0 0.0 17332 484 ? Ss 18:33 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 26536 0.0 0.0 18008 816 ? S 19:36 0:00 dbus-launch --sh-syntax --exit-with-session
sleepy 26537 0.3 0.0 18948 2028 ? Ss 19:36 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 27339 0.0 0.0 14696 1112 pts/7 S+ 19:39 0:00 grep -Pi --color=auto dbusShould be there...
EDIT:
After a reboot:
dbus 426 0.2 0.0 18288 2292 ? Ss 19:54 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
sleepy 548 0.0 0.0 18008 816 ? S 19:55 0:00 dbus-launch --sh-syntax --exit-with-session
sleepy 549 0.9 0.0 18772 1996 ? Ss 19:55 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
sleepy 1227 0.0 0.0 14696 1116 pts/1 S+ 19:56 0:00 grep -Pi --color=auto dbusLast edited by SleepyFloyd (2013-05-07 17:57:53)
Offline
What's the ouput of:
groups sleepyOffline
What's the ouput of:
groups sleepy
lp wheel video audio optical storage power vboxusers lpadmin usersNothing special, I guess...
Offline
Please create a new user and see if this new user can start applications properly...
Offline
Kinda solved this thing: Deleted .kde4.
Doesn't make much sense as I didn't change anything from a fresh installation, but that did it. Heck, I couldn't even open the KDE control center without it crashing, so the newly created folder shouldn't be different from the old one, but hey, it's working now.
Changed the thread title, although there isn't much of a solution here. Deleting .kde4 (or creating a new user, as LordChaos suggested) seems to solve many KDE problems.
Offline