GNOME Bugzilla – Bug 448436
crash in Deskbar:
Last modified: 2007-06-18 09:43:44 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-notify.c:349 (alarm_msg_received) - 0x80d9780: Received at thread b33fab90 alarm-queue.c:2008 (alarm_queueBucket count (max is 524288) is 141260 and Record Count is 289001 preferred bucket count is 289001 Optimizing word index - this may take a while... preferred bucket count is 289001 no of buckets per division is 72250 Please wait while optimization of indexes takes place... Index has file size 39630727 and bucket count of 141260 of which 121380 are used... (gnome-panel:6103): 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 -------------------------------------------------- Traceback (most recent call last):
+ Trace 141612
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 448147 ***
*** Bug 448691 has been marked as a duplicate of this bug. ***