GNOME Bugzilla – Bug 431609
crash in Deskbar: démarrage. Premier boot ...
Last modified: 2007-04-24 02:56:07 UTC
What were you doing when the application crashed? démarrage. Premier boot après passage à la 7.04 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: Clearlooks Icon Theme: Tango 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 (17 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80d6f70: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) webcal://www.google.com/calendar/ical/74igpit57a4b3l994ta12q8874%40group.calendar.google.com/private-0e43808389d62b5baad070aa4fa5baa8/basic.ics - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80d8c10: Received at thread b35d6b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d2d70 alarm-queue.c:560 (load_alarms_for_today) - From Fri Apr 20 09:59:21 2007 to Fri Apr 20 09:59:21 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d8c10: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (Initializing gnome-mount extension (gnome-panel:5851): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -6 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 129225
self.load (f)
mod_instance = getattr (mod, handler) ()
self.proxy_obj = self.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 403752 ***