GNOME Bugzilla – Bug 435035
RuntimeError loading Glade file
Last modified: 2009-04-22 11:41: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-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola 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 (6 sec old) --------------------- Traceback (most recent call last):
+ Trace 131772
start_game()
app = main.Application()
self.ui = UI(self)
gtkui.GtkUI.__init__(self)
self._gui = loadGladeFile('glchess.glade')
return gtk.glade.XML(os.path.join(GLADE_DIR, name), root, domain = DOMAIN)
-------------------------------------------------- Traceback (most recent call last):
*** Bug 440233 has been marked as a duplicate of this bug. ***
Closing as have had no duplicates and is in an external library. The RuntimeError exception is too generic so it does not make sense for us to catch it.
Please attach your version of /usr/share/games/glchess/glchess.glade, to confirm it is a valid file. Thanks.
*** Bug 499110 has been marked as a duplicate of this bug. ***
*** Bug 512340 has been marked as a duplicate of this bug. ***
Created attachment 109598 [details] [review] Fix our sys.path
Josselin Mouette <joss@debian.org> patched their installation of Gnome Games to fix the sys.path usage. It looks good to me. Posted it here.
This code cannot be removed unless the glChess .py files are installed in the system path (as is the case in Debian/most distributions). If they are installed elsewhere (e.g. I install my builds on gnome-games into ~/build) this allows glChess to run properly. Are you saying you get this RuntimeError exception from the Glade libraries? We need to investigate why this is occuring. At the worst putting an extra line (even if it is invalid) into sys.path should not cause any crashes.
Note the path went from being static to dynamic in this revision: http://svn.gnome.org/viewvc/gnome-games?view=revision&revision=5726 And the variable changed form in this revision: http://svn.gnome.org/viewvc/gnome-games?view=revision&revision=7137 (I'm not automake expert)
Perhaps this patch was meant for bug #528953 instead?
Yes, I put it on the wrong bug. For this bug, I am seeing glchess crash because it's trying to load its glade files from the build directory instead of the install path. I'll investigate further.
(removing gnome-target, because this isn't a GNOME showstopper)
*** Bug 535586 has been marked as a duplicate of this bug. ***
Works again in 2.22.2.1 (broken in 2.22.2)
*** Bug 535293 has been marked as a duplicate of this bug. ***
this is fixed in latest version of glchess in ubuntu hardy: gnome-games (1:2.22.2.1-0ubuntu1) hardy-proposed; urgency=low * New upstream version: GLChess - Fix our sys.path usage -- Sebastien Bacher <seb128@canonical.com> Fri, 30 May 2008 10:13:38 +0200 can we mark this bug as FIXED (again)?
*** Bug 535930 has been marked as a duplicate of this bug. ***
*** Bug 536048 has been marked as a duplicate of this bug. ***
It seems that I inadvertently fixed this as a side effect of more sane sys.path usage. Closing as requested.
*** Bug 537334 has been marked as a duplicate of this bug. ***
*** Bug 537332 has been marked as a duplicate of this bug. ***
*** Bug 537504 has been marked as a duplicate of this bug. ***
*** Bug 538158 has been marked as a duplicate of this bug. ***
*** Bug 538086 has been marked as a duplicate of this bug. ***
*** Bug 537238 has been marked as a duplicate of this bug. ***
*** Bug 538097 has been marked as a duplicate of this bug. ***
*** Bug 538327 has been marked as a duplicate of this bug. ***
*** Bug 538326 has been marked as a duplicate of this bug. ***
*** Bug 538265 has been marked as a duplicate of this bug. ***
*** Bug 538465 has been marked as a duplicate of this bug. ***
*** Bug 538885 has been marked as a duplicate of this bug. ***
*** Bug 538928 has been marked as a duplicate of this bug. ***
*** Bug 539181 has been marked as a duplicate of this bug. ***
*** Bug 539412 has been marked as a duplicate of this bug. ***
*** Bug 539520 has been marked as a duplicate of this bug. ***
*** Bug 539514 has been marked as a duplicate of this bug. ***
Is still occurring in 2.22.2.1...
*** Bug 539731 has been marked as a duplicate of this bug. ***
*All* of the duplicates are from Ubuntu. I am nearly certain this has something to do with the user installing GLChess 1.0 from their Universe and then going back to Gnome Games. Can one of you who filed a dup. bug confirm that you installed GLChess separately at some point?
*** Bug 539764 has been marked as a duplicate of this bug. ***
Ubuntu's seb128 is uploading a copy of gnome-games-data that conflicts with glchess. That should prevent glchess from hanging around in an unconfigured state and causing all kinds of problems. Hopefully that fixes this.
*** Bug 539802 has been marked as a duplicate of this bug. ***
*** Bug 540265 has been marked as a duplicate of this bug. ***
*** Bug 540266 has been marked as a duplicate of this bug. ***
*** Bug 540536 has been marked as a duplicate of this bug. ***
*** Bug 540573 has been marked as a duplicate of this bug. ***
*** Bug 540630 has been marked as a duplicate of this bug. ***
*** Bug 540626 has been marked as a duplicate of this bug. ***
*** Bug 540624 has been marked as a duplicate of this bug. ***
(In reply to comment #41) > Ubuntu's seb128 is uploading a copy of gnome-games-data that conflicts with > glchess. > That should prevent glchess from hanging around in an unconfigured state and > causing all kinds of problems. Hopefully that fixes this. 176 dups so far. Seb128, can you please add a comment here when this has been committed in Ubuntu?
I just checked and gnome-games is now set as both Conflicts and Replaces for glchess. Given that the bugs have stopped and the frequency they were coming in at before I think it's safe to assume this bug is finally gone. Yippee :)
*** Bug 533207 has been marked as a duplicate of this bug. ***
*** Bug 550745 has been marked as a duplicate of this bug. ***
*** Bug 549089 has been marked as a duplicate of this bug. ***
*** Bug 567379 has been marked as a duplicate of this bug. ***
*** Bug 570854 has been marked as a duplicate of this bug. ***
*** Bug 579792 has been marked as a duplicate of this bug. ***