GNOME Bugzilla – Bug 450807
crash in Deskbar: This happened when loggi...
Last modified: 2007-06-26 18:37:34 UTC
What were you doing when the application crashed? This happened when logging into a gnome session after a restart of X. I seem to be getting it all the time since I've tried to set up the Deskbar for use with metatracker/trackerd. Greets. 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-lowlatency #2 SMP PREEMPT Thu Jun 7 20:23:03 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 (7 sec old) --------------------- alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d1910: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/tobi/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80d0568: Received (gnome-panel:17938): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:17938): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:17938): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:17938): Wnck-WARNING **: Unhandled action type (nil) checking for valid crashreport now (gnome-panel:17938): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 25 -------------------------------------------------- Traceback (most recent call last):
+ Trace 143487
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 ***
Oops, sorry, I didn't even mean to report this bug. It was dispatched more or less automatically, without me paying particular attention. Sorry for taking up your valuable time.