1

Problem with systemd blame, with python2-dbus python2-cairo installed

view story
linux-howto

https://bbs.archlinux.org – are dbus.service and dbus.socket running?systemctl status dbus.service systemctl status dbus.socketif yes, have you tried re-installing systemd-analyze, not only the python2 packages? Xylankant https://bbs.archlinux.org/profile.php?id=48144 2012-09-06T22:34:26Z (HowTos)

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

Stories similar to Problem with systemd blame, with python2-dbus python2-cairo installed

miky76 wrote:when I try to add any deamons to systemctl, I get always the same errors [root@artemide ~]# systemctl enable dbus Operation failed: Invalid argument [root@artemide ~]# systemctl status dbus Failed to get D-Bus connection: No connection to service manager. [root@artemide ~]# systemctl start dbus Failed to get D-Bus connection: No connection to service manager. [root@artemide ~]#can an

[awesome] Dbus error 13 weeks 2 days ago

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

I had very similar or maybe the same problem.My error was:localhost dbus[324]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.

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

falconindy wrote:That's because you're looking at the session bus and not the system bus.Sorry u'r right...dbus 992 0.0 0.0 17300 1164 ? Ss Jan08 0:06 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

glemt9 https://bbs.archlinux.org/profile.php?id=54651

2013-01-10T09:21:23Z

Try adding "dbus-launch" to your ~/.xinitrc:[...] exec dbus-launch startfluxbox

DSpider https://bbs.archlinux.org/profile.php?id=28388

2012-10-12T20:25:19Z

Its related to the dbus upgrade, downgrade your dbus to dbus-core to 1.6.0-4. Download it to a directory from here:http://arm.konnichi.com/core/os/x86_64/ … pkg.tar.xzThen cd into said directory and run pacman -U dbus-core-1.6.0-4-x86_64.pkg.tar.xzThen reboot and all should be good =]

glitch666 https://bbs.archlinux.org/profile.php?id=29611

2012-06-29T06:53:59Z

systemd - dbus gets killed 35 weeks 4 days ago

Ok I "solved" this a while ago. MPD is trying to start avahi and that fails and causes dbus to crash...

Nothing to do with dbus...netsurf needs rebuilt for the libwebp update.   Do "pacman -Su --ignore libwebp" until this is fixed.

Allan https://bbs.archlinux.org/profile.php?id=11253

2012-12-11T06:52:31Z