You are not logged in.
Pages: 1
Hello,
I've just found no application can connect to the session bus. If I open qdbusviewer-qt4 I can see this message: "Error: Cannot connect to D-Bus: Failed to connect to socket /tmp/dbus-8gNhrUNKWG: Connection refused". System bus is working OK.
The socket file " /tmp/dbus-8gNhrUNKWG" doesn't exist. I thought dbus session should be started by KDM (I use KDE 4.10).
Heres's a `ps aux | grep dbus' output:
dbus 374 0.0 0.0 18304 2232 ? Ss May27 0:06 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
cinan 28673 0.0 0.0 17324 428 ? Ss 19:44 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
cinan 29489 0.0 0.0 15908 624 ? S 19:53 0:00 dbus-launch --sh-syntax --exit-with-session
cinan 29490 0.0 0.0 18564 1988 ? Ss 19:53 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
Am I missing configuration files or something? Thanks for help. (I'm not using testing repo.)
Last edited by cinan (2013-05-28 18:05:22)
Offline
Are you using systemd? Waht's the output of
cat /proc/1/comm
Offline
Yes I use systemd.
Offline
When I first do ps ax | grep dbus, I get no results. After opening and closing qdbusviewer-qt4, I get similar output. However, it says it can connect to dbus.
$ ps ax | grep dbus
932 ? Ss 0:57 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
1983 ? S 0:00 dbus-launch --sh-syntax --exit-with-session
1984 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
1997 ? S 0:00 dbus-launch --sh-syntax --exit-with-session
1998 ? Ss 0:01 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
I have no files of the sort you expect in /tmp. Do you have files under ~/.dbus/? What about /run/dbus/?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Online
I think I've figured out when dbus starts failing. After reboot I've fired qdbusviewer-qt4 -- everything's ok, dbus is connected, etc. Then I've logged out and logged and in after this I have these problems. It may be a bug in KDM.
Last edited by cinan (2013-05-30 08:45:12)
Offline
Pages: 1