GNOME Bugzilla – Bug 443293
crash in Deskbar: Starting Gnome. Just ins...
Last modified: 2007-06-02 22:01:32 UTC
What were you doing when the application crashed? Starting Gnome. Just installed libdeskbar-tracker 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: 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 --------------------- from egg.trayicon import TrayIcon File loaded in 790.000000 ms initialising the indexer Opening index /home/user/.Tracker/databases/Files Bucket count (max is 524288) is 114676 and Record Count is 111956 preferred bucket count is 111956 (gnome-panel:5241): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 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 ** Message: <information> You are now connected to the wireless network 'sitecom'. -------------------------------------------------- Traceback (most recent call last):
+ Trace 137577
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 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. *** This bug has been marked as a duplicate of 403752 ***