GNOME Bugzilla – Bug 436054
crash in Deskbar: X-Server starting, (usin...
Last modified: 2007-05-05 16:45:08 UTC
What were you doing when the application crashed? X-Server starting, (using XGL + Beryl), Deskbar crashed immediatly after Gnome-Panel, background graphics and so on appeared - without any user input 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: 70000000 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 (9 sec old) --------------------- File loaded in 507,000000 ms initialising the indexer Opening index /home/xpac/.Tracker/databases/Files Bucket count (max is 524288) is 130996 and Record Count is 145340 preferred bucket count is 145340 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 evolution-alarm-notify-Message: Setting timeout for 58125 1178409600 1178351475 evolution-alarm-notify-Message: Sun May 6 02:00:00 2007 evolution-alarm-notify-Message: Sat May 5 09:51:15 2007 -------------------------------------------------- Traceback (most recent call last):
+ Trace 132508
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 ***