You are not logged in.
After x amount of time dolphin and 80% of my programs will just stop working. If i try running Dolphin in terminal I get:
Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport $(dbus-launch)
The only solution is to log out / reboot. It could happen with something as simple as just opening the start menu and hitting Dolphin, clicking a firefox link, etc. It seems completely random. My system is pretty much a basic arch + Kde install with very few AUR packages installed.
Happens maybe 5 times a day?
I even created a new user account fresh but it still happens there after about a day.
How can I diagnose this?
output of systemctl status --user dbus.service
first 1500 lines of 'journalctl -b'
Last edited by zeebzz (2017-07-27 19:07:26)
Offline
ps aux | grep dbus
echo $DBUS_SESSION_BUS_ADDRESS
stat ${DBUS_SESSION_BUS_ADDRESS#*path=}
dbus-send --print-reply --session --dest=org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.DBus.Introspectable.Introspect
Offline
ps aux | grep dbus echo $DBUS_SESSION_BUS_ADDRESS stat ${DBUS_SESSION_BUS_ADDRESS#*path=} dbus-send --print-reply --session --dest=org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.DBus.Introspectable.Introspect
if you meant for me to paste the output
i think i did it wrong though, trying again as individual commands...
ps aux | grep dbus output:
https://pastebin.com/mXNZXQbU
[zach@zeeb]: ~>$ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1001/bus
[zach@zeeb]: ~>$ stat ${DBUS_SESSION_BUS_ADDRESS#*path=}
File: /run/user/1001/bus
Size: 0 Blocks: 0 IO Block: 4096 socket
Device: 2bh/43d Inode: 12772 Links: 1
Access: (0666/srw-rw-rw-) Uid: ( 1001/ zach) Gid: ( 1001/ zach)
Access: 2017-07-27 16:41:37.685734377 -0230
Modify: 2017-07-27 16:41:37.552401039 -0230
Change: 2017-07-27 16:41:37.552401039 -0230
Birth: -
dbus-send --print-reply --session --dest=org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.DBus.Introspectable.Introspect output:
^ im rebooted and things are working for now by the way, but its only a matter of time until it breaks again
Last edited by zeebzz (2017-07-27 19:38:51)
Offline
There's nothing wrong with that dbus setup, but I take you ran the commands when everything was working anyway?
It's interesting to see the difference when it doesn't.
You're free to post the outputs, but first and foremost you're encouraged to look at them yourself ;-)
Offline
whats the next step I should take when it breaks again?
Next time my system breaks and I can't open dolphin etc..what should I do?
thx
Offline
Run those commands... they provide different information about the status of the session dbus which dolphin claims to be broken.
Offline
alright, last time it broke i ran journalctl -d and it was over 3000 lines long, didnt know what to look for, didnt see anything obviously broken, but i'll look and paste the log when it happens next..
Offline
AAAAAAND it just happened.
>open a link
>SUDDENLY Error - Kio Client - Unable to create io-slave. Cannot talk to klauncher. Not connected to D-Bus server
NOW dolphin wont work, 80% of my system until reboot..
that didnt take long....suggestions..??
Offline
suggestions..??
Please paste the output of journalctl around the moment when that happened. Or better, all of `journalctl -b`.
Also (more generally), for pasting shorter snippets of console output/code, you can embed them here using code tags instead of linking to an external site—it's generally easier for other users here to read it, and more future-proof (i.e. the links won't disappear some day).
Otherwise, we would appreciate it if you used something else than pastebin.com (see this Wiki section as a reference).
Offline
ok hope this is useful, this is the entire journalctl -b
the error happened about 10 mins ago? since my last post.
https://paste.ee/p/zi3VM <--- broken formatting
so, for example, if i click a link from a program I get this prompt:
'Error - Kio Client
Unable to create io-slave. Cannot talk to klauncher. Not connected to D-bus server"
Last edited by zeebzz (2017-07-27 20:51:05)
Offline
oh wow that was easy, try this:
http://ix.io/yJQ <--- i think thats missing just a few dozen lines, not much
Last edited by zeebzz (2017-07-27 20:52:06)
Offline
Are you using Wallpaper Slideshow?
https://bbs.archlinux.org/viewtopic.php?id=228033
https://bugs.kde.org/show_bug.cgi?id=381000
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Are you using Wallpaper Slideshow?
https://bbs.archlinux.org/viewtopic.php?id=228033
https://bugs.kde.org/show_bug.cgi?id=381000
Yes i am!!! im using KDE wallpaper slideshow on my second monitor, set to change wallpaper every 30 seconds... is this really why??
Offline
Well the similarities between yours and hfenigma's journal are what made me ask, and you've confirmed that you are also using it, so I would say it's quite likely.
Disable it, and see if you can reproduce the problem.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
hasn't happened since turning off the Wallpaper Slideshow in KDE wallpaper settings.
Is this going to get addressed/fix in next kde update?
Offline
Follow the linked bug report, as of the current state of knowledge, this is a regression in QT 5.9 so it's more likely that a fix will come from there, depending on how the discussions go
Offline
Ok. It isn't the wallpaper switcher. It just happened again at complete random.
Im completely clueless now. Please help?
Offline
I deleted .kde4 in hopes of fixing it, but I already tried a new user, dont think thats gonna do much good..
Offline
I simply tried "Open containing folder" in SoulseekQT and dolphin refused to launch. Now I get the redundant 'Session bus not found' error.
I wouldn't blame SoulseekQT, it seems to happen with any program at random..
Offline
If I try to run it as sudo in terminal I get this:
[zach@zeeb]: ~>$ kdesu dolphin
klauncher not running... launching kdeinit
No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit5: Communication error with launcher. Exiting!
"KLauncher could not be reached via D-Bus. Error when calling kdeinit_exec_wait:\nNot connected to D-Bus server\n"
Offline
sudo systemctl start dbus ---> STILL HAPPENS
Offline
output of systemctl
Offline
The kdesu issue has nothing to do with anything, that is the expected behavior of kdesu. Also, learn edit posts instead of endlessly bumping your thread, this is not irc
Last edited by arojas (2017-07-30 17:05:35)
Offline
For clarification: this *only* affects dolphin and it is *not* an approach to run dolphin as different user (or even root)?
Are there stale dolphin processes when this happens? What if you kill them away?
Offline