GNOME Bugzilla – Bug 429862
crash in Deskbar:
Last modified: 2007-04-22 13:27:38 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sat Apr 14 00:54:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Gion 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 (22 sec old) --------------------- Opening index /home/shamay/.Tracker/databases/Files ** (gnome-cups-icon:5936): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:5936): WARNING **: IPP request failed with status 1280 Initializing gnome-mount extension Bucket count (max is 524288) is 73708 and Record Count is 56625 preferred bucket count is 56625 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:5900): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 127863
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)
*** Bug 429860 has been marked as a duplicate of this bug. ***
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 ***
*** Bug 432218 has been marked as a duplicate of this bug. ***