1

systemd - dbus gets killed

view story
linux-howto

https://bbs.archlinux.org – Ok I "solved" this a while ago. MPD is trying to start avahi and that fails and causes dbus to crash... I don't know if the problem is that it can't find avahi-daemon.service, or something else.I don't need avahi so now I have this in /etc/mpd.confzeroconf_enabled                "no"EDIT: tried again without this line after an update. It's still failing to start avahi, but not crashing dbus anymore :Sep 11 12:48:11 rhaego dbus-daemon[286]: dbus[286]: [system] Activating via systemd: service name='org.freedeskt (HowTos)

Danial's picture
Submitted by Danial on 09/11/2012

Stories similar to systemd - dbus gets killed

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

dbus is in your daemons array, so you should not need to start it manually.  If for some reason you think you should, then use `rc.d restart dbus`.  If a service is not running the restart command will simply start it, but if it is already running, restart will stop it, then start it again.You will, however, need a dbus-session (different from the dbus daemon).  If you get dbus erro

Gksudo problem via systemd 17 weeks 1 day ago

Dear all,

I installed gksudo (@Fedora 18 x64), because i want to use to some apps.

I have this problem at the boot time according the system log.

Code: an 21 22:39:39 evr-laptop dbus-daemon[677]: dbus[677]: [system] Activating via systemd: service name='org.gnome.Gksu' unit='gksu.service' Jan 21 22:39:39 evr-laptop dbus[677]: [system] Activating via systemd: service name='org.gnome.

At first a pacman -Syu halted with[2012-12-07 12:56] userdel: user dbus is currently used by process 202 [2012-12-07 12:56] groupdel: can't remove primary user for user "dbus" Process 202 is dbus 202 0.0 0.0 3092 1416 ?

from  journalctl -b, I get some warning messages like this.Oct 26 12:52:48 myhost dbus-daemon[359]: dbus[359]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'Oct 26 12:52:48 myhost dbus[359]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'Oct 26 12:52:48 myhost dbus-daemon[3

Stefan Husmann wrote:I do not get the point.The point is that the dbus is very slow so my boot time is too slow, same that windows 8.Dec 15 14:01:35 isty dbus[315]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 15 14:01:40 isty dbus-daemon[315]: dbus[315]: [system] Activating via systemd: service name='org.freedesktop.UDisks' unit='udisks.serv

^ 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

Understanding systemd services 39 weeks 6 hours ago

Hi. I switched to a pure systemd setup, now I'm not sure which daemons are set up to run at boot. Before it was very simple because all I had to do is look in rc.conf.Someone on irc (sudokode - thanks) suggested "systemctl disable <tab> <tab>". It is a nice trick but I'm sure it is not needed, right?

Quote:

# sudo tail -f /var/log/messages Feb 18 18:58:56 Zeus dbus-daemon[624]: dbus[624]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Feb 18 18:58:56 Zeus dbus[624]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Feb 18 18:58:56 Zeus dbus-daemon[624]: Launching FprintObject Feb 18 18:58:56 Zeus dbu