GNOME Bugzilla – Bug 481204
crash in Deskbar: trying to load drivers f...
Last modified: 2007-09-28 08:55:02 UTC
What were you doing when the application crashed? trying to load drivers from CD in hard drive with existing istallation (same versions) 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 --------------------- Initializing expo options...done Initializing move options...done Initializing neg options...done Initializing place options...done Initializing resize options...done Initializing resizeinfo options...done Initializing snap ERROR: while reading file /usr/share/tracker/sqlite-stored-procs.sql on line 170 /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 /bin/sh: /usr/bin/esd: not found ERROR: tracker_dbus_init() could not get the session bus process 11656: 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. -------------------------------------------------- Traceback (most recent call last):
+ Trace 166109
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 ***