GNOME Bugzilla – Bug 434402
crash in Deskbar: This happend after the f...
Last modified: 2007-04-29 22:09:44 UTC
What were you doing when the application crashed? This happend after the first reboot after system upgrade from 6.10 to 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: Human Icon Theme: Human 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 (6 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80c05f0: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Sat Apr 28 00:00:00 2007 to Sat Apr 28 00:00:00 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80c5b40: Received at thread b24f8b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80c2dd0 alarm-notify.c:337 (alarm_msgport_replied) - 0x80c3cf0: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Sat Apr 28 00:00:00 2007 to Sat Apr 28 00:00:00 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - (gnome-panel:6277): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -13 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 131301
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 ***