GNOME Bugzilla – Bug 436592
crash in Deskbar: first boot in machine
Last modified: 2007-05-07 17:14:03 UTC
What were you doing when the application crashed? first boot in machine 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: Glossy Icon Theme: Tango 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 --------------------- Watching directory /home/jgodoy/hamachi-0.9.9.9-20-lnx (total watches = 2) Watching directory /home/jgodoy/Desktop (total watches = 3) Watching directory /home/jgodoy/gtwitter-0.2.4 (total watches = 4) Watching directory /home/jgodoy/Wallpapers (total watches = 5) Watching directory /home/jgodoy/hamachi-0.9.9.9-20-lnx/tuncfg (total watches = 6) Watching directory /home/jgodoy/gtwitter-0.2.4/data (total watches = 7) Watching directory /home/jgodoy/gtwitter-0.2.4/gtwitter (total watches = 8) Watching directory /home/jgodoy/gtwitter-0.2.4/gtwitter/bin (total watches = 9) Watching directory /home/jgodoy/gtwitter-0.2.4/gtwitter/gtk-gui (total watches = 10) Watching directory /home/jgodoy/gtwitter-0.2.4/gtwitter/bin/Release (total watches = 11) starting indexing... indexing #1 - /home/jgodoy/Desktop flushing all words Finished indexing. Waiting for new events... Connected to daemon in 16018 milliseconds. -------------------------------------------------- Traceback (most recent call last):
+ Trace 132880
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 ***