^ There should be a dbus session for each user that is logged into your computer along with the one for root.The users session-bus is started at login, I belive by your login manager.If you already have another notification daemon running and it works you have a session bus for that user since all notifications are sent over dbus.You can check if you have a session-bus after you are logged in by c
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 ?
Ok I "solved" this a while ago. MPD is trying to start avahi and that fails and causes dbus to crash...
What program starts the per user session dbus-daemon process in GNOME 2 and GNOME 3 (presumably via dbus-launch)? I would like to know because I would like to add a directory to the list of directories that dbus-daemon checks for .service files.
(Obviously if it's a sh program, "sh" isn't the answer I'm looking for ;-)
How could I have answered this question for myself efficiently?
I'm running a fresh Fedora 17 minimal installation with Mate desktop. I have wicd-1.7.2.1-1.fc17.i686 installed.
On startup after gui login I see this message:
"Could not connect to wicd's D-Bus interface. Check the wicd log for error messages."
/var/log/wicd contains nothing un-toward, not surprising because xicd is not running.
Thanks for the reply, Trilby!Trilby wrote:I've never used lxdm, but I suspect you need to add dbus-launch to the exec line of your window manager.To test this, first check a process monitor like hop or pstree. You should have three processes with dbus in the name: 2 dbus-daemon processes (one for user "dbus" and one for your user), and 1 dbus-launch.I think that you are sugges
Hi guys,my newly configured awesome desktop got this issue when I try to start an application using d-bus :(terminator:947): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-5AMlNl46V1: Connection refusedBut systemctl status dbus.service says dbus is active and running.I don't know what's wrong, do you have any idea ?Thanks
capta
Hi all
I hope someone can help me with this one.
A dbus-daemon process hogs a major part of my cpu cycles. I've been trying to find a solution all over but didn't manage so I'm turning to the collected knowledge-base here.
See below cut from top and ps aux | grep dbus-daemon
I'm on a opensuse 11.1 and kde 4.3 system.
Thanks
After my Upgrade from F15 to F17 I'm seeing alot of these messages , just wondering if they are significant and/or how do I fix it?
Code:
Sep 2 14:27:35 mythbox dbus-daemon[711]: dbus[711]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Sep 2 14:27:35 mythbox udisksd[1889]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Sep 2 14:2