GNOME Bugzilla – Bug 450466
crash in Deskbar: Simplesmente estava inic...
Last modified: 2007-06-23 22:02:00 UTC
What were you doing when the application crashed? Simplesmente estava iniciando o computador Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3167.fc7 #1 SMP Thu May 17 23:05:53 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Smooth-Desert Icon Theme: YattaBlues 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 --------------------- Initializing nautilus-search-tool extension seahorse nautilus module initialized Bucket count (max is 524288) is 294908 and Record Count is 266733 preferred bucket count is 266733 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 ** (nautilus:3338): WARNING **: Não foi encontrada descrição para o tipo MIME "x-directory/smb-share" (o arquivo é "C%24"), por favor notifique a lista de discussão do gnome-vfs. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! -------------------------------------------------- Traceback (most recent call last):
+ Trace 143214
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 ***