GNOME Bugzilla – Bug 487805
crash in Gimmie: viewing favourites
Last modified: 2007-10-22 22:30:00 UTC
What were you doing when the application crashed? viewing favourites Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (159 sec old) --------------------- to Thu Oct 18 08:26:11 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e0bd0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/ian/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80dead0: Received at threa (gnome-panel:6124): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 24 checking for valid crashreport now Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3800007 specified for 0x3800011 (Progress..). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3800007 specified for 0x3800011 (Progress..). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3800007 specified for 0x3800011 (Progress..). Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600056 (Tactical A) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 171072
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***