GNOME Bugzilla – Bug 438748
crash in Deskbar: Restarting
Last modified: 2007-05-16 01:18:04 UTC
What were you doing when the application crashed? Restarting 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: Clearlooks 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 --------------------- preferred bucket count is 154375 Application Engine : Scanning /usr/local/share/applications (affinity:5517): GLib-CRITICAL **: g_dir_read_name: assertion `dir != NULL' failed (affinity:5517): GLib-CRITICAL **: g_dir_close: assertion `dir != NULL' failed Application Engine : Scanning /usr/share/applications 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 Application Engine : Scanning /usr/share/applications/screensavers ** Message: <information> You are now connected to the wireless network 'MSHOME'. -------------------------------------------------- Traceback (most recent call last):
+ Trace 134372
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 for tracker. *** This bug has been marked as a duplicate of 403752 ***