GNOME Bugzilla – Bug 429525
crash in Gimmie:
Last modified: 2007-04-22 22:23:13 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-14-generic #2 SMP Thu Apr 12 22:53:19 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy 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 (3601 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x3800002 (Welcome to). ** (gnome-system-monitor:12051): WARNING **: SELinux was found but is not enabled. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400018 (tilda) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (gnome-system-monitor:12719): WARNING **: SELinux was found but is not enabled. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400018 (tilda) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400018 (tilda) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: last_focus_time (8492820) is greater than comparison timestamp (8492816). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACT -------------------------------------------------- Traceback (most recent call last):
+ Trace 127586
self.scroll.connect("size-request", lambda w, req: self._scroll_get_best_size(w, req))
upper = min(upper, int(self.get_screen().get_height() * 0.7))
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 417988 ***