Bug 370279 – dev-util/meld-1.5.1 fails to start due to failed contact to configuration server

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Juergen Rose 2011-06-06 13:30:57 UTC]

Very often I can't start meld as root because I get:
 GetIOR failed: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/gconfd-2 received signal 6.

It happens, if I do 'su -' in a gnome-terminal window followed by 'meld' or if start with 'xterm -e su -' as well.

In both cases I can start meld with '/usr/libexec/gconfd-2 & meld'. But the last solution does not help if meld is called in a script. Even '/usr/libexec/gconfd-2 & example-script' usually does not help, if the script needs some minutes until the first call of meld, because the gconfd-2 process runs only some seconds if no other programm interacts with the gconfd-2 process.
So if I run 'dispatch-conf' with 'diff="meld '%s' '%s'"' in /etc/dispatch-conf.conf it fails with GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/gconfd-2 received signal 6. But '/usr/libexec/gconfd-2 & dispatch-conf' usually works, if I answer all questions without waiting.

Nevertheless it is a nasty behaviour.

[Comment 1 Juergen Rose 2011-06-08 15:29:56 UTC]

Today meld fails to start for root with a new error message:

Traceback (most recent call last):
  File "/usr/bin/meld", line 137, in <module>
    main()
  File "/usr/bin/meld", line 128, in main
    from meld.meldapp import app
  File "/usr/lib64/meld/meld/meldapp.py", line 203, in <module>
    app = MeldApp()
  File "/usr/lib64/meld/meld/meldapp.py", line 111, in __init__
    self.prefs = preferences.MeldPreferences()
  File "/usr/lib64/meld/meld/preferences.py", line 257, in __init__
    super(MeldPreferences, self).__init__("/apps/meld", self.defaults)
  File "/usr/lib64/meld/meld/util/prefs.py", line 94, in __init__
    self._gconf.add_dir(rootkey, gconf.CLIENT_PRELOAD_NONE)
glib.GError: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory)


Indeed, /var/lib/dbus is a empty directory.

Should I file a separated bug for this?

[Comment 2 Pacho Ramos 2011-06-08 17:40:28 UTC]

I think that error is due latest dbus bump

[Comment 3 Pacho Ramos 2011-06-10 11:19:31 UTC]

What is you dbus version?

[Comment 4 Juergen Rose 2011-06-10 12:33:24 UTC]

I have dbus-1.4.10. After restarting dbus (/etc/init.d/dbus restart) the issue of Comment 1 disapeared.

[Comment 5 Pacho Ramos 2011-06-10 12:36:53 UTC]

You are back to original problem then, no? In that case please take a look on bug #370259 as it looks like a bit similar

[Comment 6 Juergen Rose 2011-06-10 14:30:15 UTC]

I am probably back to the original problem. But the original problem happens often but not permanently and it happens on the local computer and during ssh sessions on remote computers as well. So I suppose, that it is not the same issue as bug #370259. Often I can solve the issue by log out from my gdm session and log in again.

[Comment 7 Pacho Ramos 2011-07-15 12:24:54 UTC]

Are you still suffering this on a fully updated system? (I think dbus was updated since then)

[Comment 8 Juergen Rose 2011-07-15 12:40:03 UTC]

I have the feeling that I did not suffer from the issue the last two weeks.

[Comment 9 Pacho Ramos 2011-07-15 16:51:02 UTC]

Will close for now then as dbus was updated recently, but feel free to reopen if it reappears