GNOME Bugzilla – Bug 451163
crash in Deskbar:
Last modified: 2007-06-26 17:35:29 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-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Mist 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 --------------------- alarm-queue.c:2008 (alarm_queueBucket count (max is 524288) is 141260 and Record Count is 306376 preferred bucket count is 306376 Optimizing word index - this may take a while... preferred bucket count is 306376 no of buckets per division is 76594 Please wait while optimization of indexes takes place... Index has file size 43947432 and bucket count of 141260 of which 122636 are used... (gnome-panel:5994): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24 No se puede abrir el archivo de escritorio file:///home/eckelon/Desktop/%20.desktop para el lanzador del panel: No existe el fichero ó directorio No se puede abrir el archivo de escritorio file:///home/eckelon/Desktop/%C2%B5Torrent.desktop para el lanzador del panel: No existe el fichero ó directorio (QFA)Talkback error: Can't initialize. Starting calendar alarm service observer added No handlers could be found for logger "dbus.proxies" -------------------------------------------------- Traceback (most recent call last):
+ Trace 143781
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 ***