GNOME Bugzilla – Bug 483483
crash in Gimmie: using gimmie while 3-4 p...
Last modified: 2007-10-06 12:10:11 UTC
What were you doing when the application crashed? using gimmie while 3-4 programs were opening. 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-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango 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 (24 sec old) --------------------- xscreensaver: 16:30:52: 0: for window 0x400001d (file-roller / File-roller) xscreensaver: 16:31:13: 0: unrecognised ClientMessage "_NET_WM_STATE" received xscreensaver: 16:31:13: 0: for window 0x4200065 (gksu / Gksu) xscreensaver: 16:31:13: 0: unrecognised ClientMessage "_NET_WM_STATE" received xscreensaver: 16:31:13: 0: for window 0x4200065 (gksu / Gksu) xscreensaver: 16:31:14: 0: unrecognised ClientMessage "_NET_WM_STATE" received xscreensaver: 16:31:14: 0: for window 0x4200065 (gksu / Gksu) xscreensaver: 16:31:15: 0: unrecognised ClientMessage "_NET_WM_STATE" received xscreensaver: 16:31:15: 0: for window 0x4200065 (gksu / Gksu) xscreensaver: 16:31:15: 0: unrecognised ClientMessage "_NET_WM_STATE" received xscreensaver: 16:31:15: 0: for window 0x4400003 (gnome-keyring-ask / Gnome-keyring-ask) DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 xscreensaver: 16:32:14: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received xscreensaver: 16:32:14: 0: for window 0x4600092 (synaptic / Synaptic) xscreensaver: 16:32:15: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received xscreensaver: 16:32:15: 0: for window 0x120060e (nautilus / Nautilus) -------------------------------------------------- Traceback (most recent call last):
+ Trace 167795
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 ***