GNOME Bugzilla – Bug 465355
crash in Gimmie:
Last modified: 2007-09-06 09:46:05 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-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: IndustrialTango 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 (168497 sec old) --------------------- Watching directory /home/kia/doc-amaya/html/d9/d7f (total watches = 2043) Watching directory /home/kia/doc-amaya/html/d9/d7e (total watches = 2044) Watching directory /home/kia/doc-amaya/html/d9/d7d (total watches = 2045) Watching directory /home/kia/doc-amaya/html/d9/d7c (total watches = 2046) Watching directory /home/kia/doc-amaya/html/d9/d7b (total watches = 2047) Watching directory /home/kia/doc-amaya/html/d9/d7a (total watches = 2048) Watching directory /home/kia/doc-amaya/html/d9/d79 (total watches = 2049) Watching directory /home/kia/doc-amaya/html/d9/d78 (total watches = 2050) Watching directory /home/kia/doc-amaya/html/d9/d77 (total watches = 2051) Watching directory /home/kia/doc-amaya/html/d9/d76 (total watches = 2052) Watching directory /home/kia/doc-amaya/html/d9/d75 (total watches = 2053) Watching directory /home/kia/doc-amaya/html/d9/d74 (total watches = 2054) Watching directory /home/kia/doc-amaya/html/d9/d73 (total watches = 2055) ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 154193
self.content.set_size_request(track_alloc.width, -1)
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 ***