GNOME Bugzilla – Bug 481466
crash in Deskbar: Installing Ubuntu 7.10
Last modified: 2007-09-29 16:11:22 UTC
What were you doing when the application crashed? Installing Ubuntu 7.10 Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-07-30 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- evolution-alarm-notify-Message: Setting timeout for 619 1191024000 1191023381 evolution-alarm-notify-Message: Sat Sep 29 01:00:00 2007 evolution-alarm-notify-Message: Sat Sep 29 00:49:41 2007 libnotify-Message: Unable to get session bus: Failed to connect to socket /tmp/dbus-pOEuxnVNC3: Connection refused /bin/sh: /usr/bin/esd: not found /bin/sh: /usr/bin/esd: not found ERROR: tracker_dbus_init() could not get the session bus process 6020: arguments to dbus_connection_register_object_path() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5280. This is normally a bug in some application using the D-Bus library. /bin/sh: /usr/bin/esd: not found /bin/sh: /usr/bin/esd: not found /bin/sh: /usr/bin/esd: not found /bin/sh: /usr/bin/esd: not found -------------------------------------------------- Traceback (most recent call last):
+ Trace 166300
self.load (f)
mod_instance = getattr (mod, handler) ()
bus = dbus.SessionBus()
mainloop=mainloop)
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 366899 ***