GNOME Bugzilla – Bug 426672
crash in Deskbar:
Last modified: 2007-04-09 22:26:51 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (38 sec old) --------------------- initialising the indexer Opening index /home/musicman/.Tracker/databases/Files Bucket count (max is 524288) is 73708 and Record Count is 24445 preferred bucket count is 24445 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 Initializing gnome-mount extension Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml (gnome-panel:6052): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 30 Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml -------------------------------------------------- Traceback (most recent call last):
+ Trace 125287
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 428033 has been marked as a duplicate of this bug. ***