GNOME Bugzilla – Bug 439983
crash in Deskbar: crash on session startup
Last modified: 2007-05-20 17:27:13 UTC
What were you doing when the application crashed? crash on session startup 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 (9 sec old) --------------------- alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80dabd0: Received at thread b3da0b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d7580 alarm-notify.c:337 (alarm_msgport_replied) - 0x80d8240: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Sun May 20 19:17:59 2007 to Sun May 20 19:17:59 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80dd6b0: Received at thread b3da0b90 alarm-queue.c:2008 (al (gnome-panel:26936): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 23 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00028 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 135196
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 for tracker. *** This bug has been marked as a duplicate of 403752 ***