GNOME Bugzilla – Bug 439022
crash in Deskbar:
Last modified: 2007-05-17 07:58:58 UTC
What were you doing when the application crashed? 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: Glider 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 --------------------- [7] /usr/bin/../lib/kadu/modules/ext_info.so(ext_info_init+0x40) [0xb612c1e0] [8] /usr/bin/kadu(_ZN14ModulesManager14activateModuleERK7QString+0x21a) [0x815e7ca] [9] /usr/bin/kadu(_ZN14ModulesManagerC1Ev+0x574) [0x815fcd4] [10] /usr/bin/kadu(_ZN14ModulesManager10initModuleEv+0x1a) [0x815ffba] [11] /usr/bin/kadu(main+0xf5f) [0x814fcbf] [12] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7411ebc] [13] /usr/bin/kadu(_ZN7QWidget17setUpdatesEnabledEb+0x3d) [0x80b5591] ======= END OF BACKTRACE ====== Bucket count (max is 524288) is 122852 and Record Count is 121711 preferred bucket count is 121711 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 134540
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 for tracker. *** This bug has been marked as a duplicate of 403752 ***