GNOME Bugzilla – Bug 440658
crash in Deskbar: deskbar crashes while lo...
Last modified: 2007-05-23 16:41:58 UTC
What were you doing when the application crashed? deskbar crashes while loading (I have tracker handler installed) It works fine when I add the tracker, but when I restart the system It crashes 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-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 --------------------- Using Sqlite version 3.3.13 Loading prepared queries... File loaded in 0,000000 ms initialising the indexer Opening index /home/demimismo/.Tracker/databases/Files Bucket count (max is 524288) is 147428 and Record Count is 146384 preferred bucket count is 146384 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:6130): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 135658
self.load (f)
mod_instance = getattr (mod, handler) ()
self.proxy_obj = self.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 for tracker. *** This bug has been marked as a duplicate of 403752 ***