GNOME Bugzilla – Bug 411222
crash in Deskbar: Start up
Last modified: 2007-04-02 12:56:02 UTC
What were you doing when the application crashed? Start up Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.91 2007-02-12 (Ubuntu) BugBuddy Version: 2.17.3 System: Linux 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled 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) --------------------- alarm-queue.c:560 (load_alarms_for_today) - From Fri Feb 23 15:29:11 2007 to Fri Feb 23 15:29:11 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d18a8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:3Bucket count (max is 524288) is 114676 and Record Count is 108990 preferred bucket count is 108990 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 -------------------------------------------------- Traceback (most recent call last):
+ Trace 113231
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 the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 403752 ***
*** Bug 424024 has been marked as a duplicate of this bug. ***
*** Bug 425188 has been marked as a duplicate of this bug. ***