GNOME Bugzilla – Bug 461123
crash in Chess: mahir@jt-laptop:~$ glche...
Last modified: 2007-07-28 01:24:27 UTC
What were you doing when the application crashed? mahir@jt-laptop:~$ glchess Traceback (most recent call last):
+ Trace 151084
start_game()
app = main.Application()
self.ui = UI(self)
self.controller = gtkui.GtkUI(self)
tooltip.tip_window.ensure_style()
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: MurrinaRinsei 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 (33 sec old) --------------------- (gnome-panel:7104): Gtk-CRITICAL **: gtk_drag_set_icon_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed (gnome-panel:7104): Gtk-CRITICAL **: gtk_drag_set_icon_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed (gnome-panel:7104): Gtk-CRITICAL **: gtk_drag_set_icon_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed (gnome-panel:7104): Gtk-CRITICAL **: gtk_drag_set_icon_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed (gnome-panel:7104): Gtk-CRITICAL **: gtk_drag_set_icon_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed (gnome-panel:7104): Gtk-CRITICAL **: gtk_drag_set_icon_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed ** (gnome-panel:7104): WARNING **: panel-applet-frame.c:1278: failed to load applet OAFIID:BigBoard_Applet: Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_2/prefs;background=pixmap:16782709,-1,-1;orient=down;size=x-small;locked_down=false -------------------------------------------------- Traceback (most recent call last):
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 ***