GNOME Bugzilla – Bug 439904
crash in Deskbar:
Last modified: 2007-05-20 11:06:15 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-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Darkilouche Icon Theme: Tangerine 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 (13 sec old) --------------------- Initializing gnome-mount extension Initializing nautilus-open-terminal extension Impossibile aprire il file .desktop «/usr/share/applications/opera.desktop» per l'icona di avvio: Nessun file o directory Impossibile aprire il file .desktop «file:///home/marco/Desktop/bar-00744727fb.desktop» per l'icona di avvio: Nessun file o directory Bucket count (max is 524288) is 458716 and Record Count is 443487 preferred bucket count is 443487 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 ** (gnome-screensaver:5766): WARNING **: salvaschermo già in esecuzione in questa sessione (gnome-panel:5583): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 29 -------------------------------------------------- Traceback (most recent call last):
+ Trace 135145
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 ***