You are not logged in.
Hi.
I want to use meld for merging pacnew files. It works as a regular user but as root it errors out with the following message:
(meld:19778): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "/usr/bin/meld", line 138, in <module>
main()
File "/usr/bin/meld", line 129, in main
from meld.meldapp import app
File "/usr/lib/meld/meld/meldapp.py", line 199, in <module>
app = MeldApp()
File "/usr/lib/meld/meld/meldapp.py", line 113, in __init__
self.prefs = preferences.MeldPreferences()
File "/usr/lib/meld/meld/preferences.py", line 265, in __init__
super(MeldPreferences, self).__init__("/apps/meld", self.defaults)
File "/usr/lib/meld/meld/util/prefs.py", line 93, in __init__
self._gconf.add_dir(rootkey, gconf.CLIENT_PRELOAD_NONE)
glib.GError: No D-BUS daemon running
I think that dbus is running. Executing
systemctl start dbus
does not help.
Any clue what can help?
EDIT: I use standalone openbox and slim.
Last edited by SoleSoul (2013-02-10 12:12:09)
Offline
What does
$ systemctl status dbus.service
say?
Arch_x64 on Thinkpad Edge E520 (Intel Core i5, 4 GB RAM, 128 GB Crucial M4 SSD) + ITX-Desktop (Asrock H77M-ITX, Intel Core i3-2120T, 8GB RAM, 64 GB Samsung 830 SSD)
Offline
The output of
$ systemctl status dbus.service
is:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Sun 2013-02-10 12:33:10 IST; 1h 35min ago
Main PID: 194 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─194 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-...
Feb 10 12:33:10 fort systemd[1]: Started D-Bus System Message Bus.
Feb 10 12:33:52 fort dbus-daemon[194]: dbus[194]: [system] Activating via systemd: service name='org...ice'
Feb 10 12:33:52 fort dbus[194]: [system] Activating via systemd: service name='org.freedesktop.Poli...vice'
Feb 10 12:33:53 fort dbus-daemon[194]: dbus[194]: [system] Successfully activated service 'org.freed...it1'
Feb 10 12:33:53 fort dbus[194]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 10 12:45:11 fort dbus-daemon[194]: dbus[194]: [system] Activating via systemd: service name='org...ice'
Feb 10 12:45:11 fort dbus[194]: [system] Activating via systemd: service name='org.freedesktop.UDis...vice'
Feb 10 12:45:11 fort dbus-daemon[194]: dbus[194]: [system] Successfully activated service 'org.freed...ks2'
Feb 10 12:45:11 fort dbus[194]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 10 13:25:55 fort systemd[1]: Started D-Bus System Message Bus.
I found a workaround. Running
dbus-launch meld
as root does work.
I still don't know why this is needed but I can live with that.
Thanks.
Last edited by SoleSoul (2013-02-10 12:11:14)
Offline
Same problem here (xfce4 and slim)
Funny thing is, it worked without the dbus-launch workaround last time I checked (about two monts ago).
Offline