GNOME Bugzilla – Bug 404517
crash in Deskbar:
Last modified: 2007-02-15 16:48:32 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.90 2007-01-23 (Ubuntu) BugBuddy Version: 2.17.3 System: Linux 2.6.20-6-lowlatency #2 SMP PREEMPT Wed Jan 31 20:55:57 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 (25 sec old) --------------------- alarm-notify.c:393 (cal_opened_cb) file:///home/aleander/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarmInitializing nautilus-open-terminal extension Initializing gnome-mount extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Bucket count (max is 524288) is 360428 and Record Count is 333855 preferred bucket count is 333855 ** Message: drive = 0 ** Message: volume = 0 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 13 and needed version is 13 -------------------------------------------------- Traceback (most recent call last):
+ Trace 108104
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 402429 ***
*** Bug 407688 has been marked as a duplicate of this bug. ***
*** Bug 408107 has been marked as a duplicate of this bug. ***