GNOME Bugzilla – Bug 459134
crash in Deskbar: Nothing, crash while boo...
Last modified: 2007-07-22 09:47:53 UTC
What were you doing when the application crashed? Nothing, crash while booting linux, just GNOME was loaded 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 Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: nuoveXT.2.1 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 (11 sec old) --------------------- (gnome-keyring-ask:5661): Gtk-WARNING **: Theme directory 64x64/filesystems of theme nuoveXT.2.1 has no size field (gnome-keyring-ask:5661): Gtk-WARNING **: Theme directory 72x72/filesystems of theme nuoveXT.2.1 has no size field (gnome-keyring-ask:5661): Gtk-WARNING **: Theme directory 96x96/filesystems of theme nuoveXT.2.1 has no size field 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> Ahora está conectado a la red inalámbrica WRT54GL. -------------------------------------------------- Traceback (most recent call last):
+ Trace 149685
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 ***