From e742f63e9c56cc2c913fa8cfda7a9d583a2c2aa2 Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Wed, 27 Jan 2010 16:26:01 +0100 Subject: abrtd: proper fix to autostart problem Signed-off-by: Denys Vlasenko --- src/Gui/CCDBusBackend.py | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'src/Gui/CCDBusBackend.py') diff --git a/src/Gui/CCDBusBackend.py b/src/Gui/CCDBusBackend.py index b99e6f8e..1ab0e3a8 100644 --- a/src/Gui/CCDBusBackend.py +++ b/src/Gui/CCDBusBackend.py @@ -99,11 +99,9 @@ class DBusManager(gobject.GObject): # Autostart hack # Theoretically, this is not needed, the first dbus call # should autostart daemon if needed. In practice, - # without this code autostart is not reliable. Apparently - # dbus fails to check that the first call after autostart - # does not fail because daemon did not finish its initialization yet. - # (strace says abrt-gui -> dbus_daemon transfer is ok, - # I suspect dbus_daemon -> freshly_started_abrtd isn't) + # without this code autostart is not reliable. + # Update: fixed the problem on daemon side, + # but retaining this code for now. More stability won't hurt us... try: (always_true, rc) = self.bus.start_service_by_name(ABRTD_DBUS_NAME, flags=0) # rc is either self.bus.START_REPLY_SUCCESS or self.bus.START_REPLY_ALREADY_RUNNING -- cgit