GNOME Bugzilla – Bug 442989
crash in Deskbar: booting again
Last modified: 2007-06-01 17:59:58 UTC
What were you doing when the application crashed? booting again 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 Wed May 23 01:46:23 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 --------------------- Index has file size 46009339 and bucket count of 130996 of which 120758 are used... Initializing gnome-mount extension ** Message: <information> You are now connected to the wireless network 'sparks'. (gnome-panel:5178): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -16 and height 24 Unable to open desktop file file:///home/me/Desktop/Tilp.desktop for panel launcher: No such file or directory Optimization has failed due to existing record Unable to open desktop file file:///home/me/Desktop/TI-89%20Emulator.desktop for panel launcher: No such file or directory 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 updating database stats...please wait... -------------------------------------------------- Traceback (most recent call last):
+ Trace 137314
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 the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 403752 ***