GNOME Bugzilla – Bug 446920
crash in Deskbar: Changing Amarok visualiz...
Last modified: 2007-06-13 00:29:07 UTC
What were you doing when the application crashed? Changing Amarok visualizations. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaVerdeOlivo Icon Theme: Buuf 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 (16 sec old) --------------------- Loading prepared queries... File loaded in 0.000000 ms initialising the indexer Opening index /home/pcmacman/.Tracker/databases/Files (gnome-panel:373): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 Loading image "/home/pcmacman/Firefox_wallpaper.png" Loading image "/home/pcmacman/Firefox_wallpaper.png" Bucket count (max is 524288) is 73708 and Record Count is 85040 preferred bucket count is 85040 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 140480
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 ***