GNOME Bugzilla – Bug 454195
crash in Deskbar: crash at startup
Last modified: 2007-07-07 21:18:52 UTC
What were you doing when the application crashed? crash at startup Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Tux_G2_orange 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 (10 sec old) --------------------- LOADED : /usr/share/applications/totem.desktop LOADED : /usr/share/applications/rhythmbox.desktop LOADED : /home/alex/.gnome2/panel2.d/default/launchers/gnome-terminal.desktop APPLET : /usr/lib/awn/applets/taskman.desktop APPLET : /usr/lib/awn/applets/separator.desktop APPLET : /usr/lib/awn/applets/switcher.desktop APPLET : /usr/lib/awn/applets/trash.desktop Bucket count (max is 524288) is 393196 and Record Count is 370027 preferred bucket count is 370027 starting database closure for thread main Database closed for thread main starting database closure for thread main Database closed for thread main Checking tracker DB version...Current version is 15 and needed version is 13 Initializing gnome-mount extension -------------------------------------------------- Traceback (most recent call last):
+ Trace 146065
self.load (f)
mod_instance = getattr (mod, handler) ()
self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
follow_name_owner_changes=follow_name_owner_changes)
_dbus_bindings.UInt32(0))
reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
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 403752 ***