GNOME Bugzilla – Bug 461963
crash in Chess: building gcc. distchecki...
Last modified: 2007-08-02 00:59:40 UTC
What were you doing when the application crashed? building gcc. distchecking kaffe. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.5 2007-07-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 (71889 sec old) --------------------- (update-notifier:5170): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (update-notifier:5170): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (update-notifier:5170): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (update-notifier:5170): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (update-notifier:5170): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (update-notifier:5170): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (update-notifier:5170): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 151702
start_game()
app = main.Application()
self.ui = UI(self)
self.controller = gtkui.GtkUI(self)
tooltip.tip_window.ensure_style()
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 459740 ***