GNOME Bugzilla – Bug 445040
crash in Deskbar: Starting up Gnome when n...
Last modified: 2007-06-07 21:10:18 UTC
What were you doing when the application crashed? Starting up Gnome when network connection was down. I've also installed tracker-handle since last reboot. 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: Clearlooks Icon Theme: Tango 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 (17 sec old) --------------------- File loaded in 665.000000 ms initialising the indexer Opening index /home/tronda/.Tracker/databases/Files Bucket count (max is 524288) is 229324 and Record Count is 228143 preferred bucket count is 228143 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 (gnome-panel:5576): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height 24 Initializing nautilus-open-terminal extension seahorse nautilus module initialized Initializing gnome-mount extension -------------------------------------------------- Traceback (most recent call last):
+ Trace 139002
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 ***