GNOME Bugzilla – Bug 447263
crash in Gimmie:
Last modified: 2007-09-08 22:12:58 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-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: mac-osx-controls Icon Theme: OSX 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 (60433 sec old) --------------------- (avant-window-navigator:5977): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:5977): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:5977): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. fixme:htmlhelp:HtmlHelpW HH case HH_PRETRANSLATEMESSAGE not handled. ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 140734
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 ***