GNOME Bugzilla – Bug 442352
Exception inside gobject bindings
Last modified: 2007-06-04 00:27:07 UTC
What were you doing when the application crashed? nothing ! Just launched the game while Beryl was running Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20.11 #1 SMP Thu May 17 22:03:40 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 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 (222 sec old) --------------------- beryl: Couldn't bind redirected window 0x12069aa to texture beryl: pixmap 0x1e007fd can't be bound to texture beryl: Couldn't bind redirected window 0x12069aa to texture beryl: pixmap 0x1e007fd can't be bound to texture beryl: Couldn't bind redirected window 0x12069aa to texture beryl: pixmap 0x1e007fd can't be bound to texture beryl: Couldn't bind redirected window 0x12069aa to texture beryl: pixmap 0x1e007fd can't be bound to texture beryl: Couldn't bind redirected window 0x12069aa to texture beryl: pixmap 0x1e007fd can't be bound to texture beryl: Couldn't bind redirected window 0x12069aa to texture beryl: pixmap 0x1e007fd can't be bound to texture beryl: Couldn't bind redirected window 0x12069aa to texture ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 136835
start_game()
import main
import gtkui
from gtkui import GtkView, GtkUI
import gobject
if [ "\$1" = "remove" ]; then
Looks like your python-gobject install is corrupted (the line generating the error is shell script not python). Please try from the command line: $ python >>> import gobject If the same errors are reported there is a problem with your python-gobject package and you will need to raise a bug with Ubuntu. Re-installing with: # apt-get install --reinstall python-gobject may fix the problem. But that leaves the question how did that file get corrupted?
Hi, I have seen after this bug that I had a lot of problemes with my ext3 partition (file system nearly corrupted ... a real big mess in fact) The fsck might have caused the problem ... In fact, my gnome instal was completely broken (bug everywhere :() so I reinstalled it and from noow, everything seems to work back again ;) Thanks for your interest to my problem :D
No problem, closing.