GNOME Bugzilla – Bug 427861
crash in Deskbar: log in
Last modified: 2007-04-12 13:46:14 UTC
What were you doing when the application crashed? log in Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Silicon 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 (10 sec old) --------------------- Loading prepared queries... File loaded in 640.000000 ms initialising the indexer Opening index /home/temcat/.Tracker/databases/Files Bucket count (max is 524288) is 245668 and Record Count is 241053 preferred bucket count is 241053 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 (gnome-panel:5463): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 Unable to open desktop file /usr/share/applications/Thunderbird.desktop for panel launcher: No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 126273
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 412771 ***
*** Bug 428942 has been marked as a duplicate of this bug. ***