GNOME Bugzilla – Bug 438211
crash in Gimmie:
Last modified: 2007-05-23 22:33:49 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-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: Clearlooks 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 (68 sec old) --------------------- deleting file /home/ste/Desktop/scribes-0.3.2.4/conftest.er1 deleting file /home/ste/Desktop/scribes-0.3.2.4/conftest.c File /home/ste/Desktop/scribes-0.3.2.4/conftest.er1 has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.err has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.c has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.c has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.c has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.er1 has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.err has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.c has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.c has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.c has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.er1 has finished changing File /home/ste/Desktop/scribes-0.3.2.4/conftest.err has finished changing checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last):
+ Trace 134017
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 ***