[Hardy] Segfault in XGetXCBConnection when starting compiz.real

[Tristan Schmelcher]

Binary package hint: compiz-core

I upgraded all my compiz packages to the latest hardy version today to see if there were new features, but instead compiz dies with a segmentation fault for me whenever I try and start it. Version info:

$ apt-show-versions | grep compiz
compiz-gnome/hardy uptodate 1:0.7.0-0ubuntu2
python-compizconfig/hardy uptodate 0.6.99+git20080214-0ubuntu1
compizconfig-settings-manager/hardy uptodate 0.6.99+git20080213-0ubuntu1
compiz-plugins/hardy uptodate 1:0.7.0-0ubuntu2
compiz-fusion-plugins-extra/hardy uptodate 0.6.99+git20080213-0ubuntu2
libcompizconfig0/hardy uptodate 0.6.99+git20080214-0ubuntu1
compiz-fusion-plugins-main/hardy uptodate 0.6.99+git20080214-0ubuntu2
compizconfig-backend-gconf/hardy uptodate 0.6.99+git20080210-0ubuntu1
compiz-core/hardy uptodate 1:0.7.0-0ubuntu2
compiz/hardy uptodate 1:0.7.0-0ubuntu2
compiz-core-dbgsym/hardy uptodate 1:0.7.0-0ubuntu2
$ uname -a
Linux ****** 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

My computer is a Dell XPS M1710 laptop with an NVIDIA GeForce 7900 Go GS, using the 169.09 drivers.

If compiz is started from the System -> Appearance -> Visual Effects tab, I simply get "Desktop effects could not be enabled".

If started from a terminal by typing "compiz", I get this:

$ compiz
Checking for Xgl: not present.
Detected PCI ID for VGA: 01:00.0 0300: 10de:0298 (rev a1) (prog-if 00 [VGA])
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Comparing resolution (1920x1200) to maximum 3D texture size (4096): Passed.
Checking for nVidia: present.
Checking for FBConfig: present.
Checking for Xgl: not present.
Starting gtk-window-decorator
Segmentation fault (core dumped)

Looking at the script, it is compiz.real that is segfaulting. I have attached a backtrace obtained with gdb (not really sure if I did it properly though). The segfault occurs in XGetXCBConnection.

[Michael Vogt (mvo)]

Thanks for your bugreport.

Do you get a crash file in /var/crash when this happens? If so, could you please geneate a apport report with it. Please run /usr/share/apport/apport-gtk

[rosencreuz (rosencreuz)]

I have the same problem (as far as I can see). I don't have any crash file regarding compiz in /var/crash. This problem started with the last update of the compiz. Until that compiz was working.

[Tristan Schmelcher (tschmelcher)]

I do get a crash file. I have run apport as requested and it has opened a new bug with the extra info. I am marking this one as a duplicate.

[rosencreuz (rosencreuz)]

I don't have the problem anymore after todays update. Here's my versions.

$ apt-show-versions |grep compiz
compiz-gnome/hardy uptodate 1:0.7.0-0ubuntu3
python-compizconfig/hardy uptodate 0.6.99+git20080214-0ubuntu1
compizconfig-settings-manager/hardy uptodate 0.6.99+git20080213-0ubuntu1
compiz-plugins/hardy uptodate 1:0.7.0-0ubuntu3
compiz-fusion-plugins-extra/hardy uptodate 0.6.99+git20080213-0ubuntu2
libcompizconfig0/hardy uptodate 0.6.99+git20080215-0ubuntu1
compiz-fusion-plugins-main/hardy uptodate 0.6.99+git20080214-0ubuntu2
compizconfig-backend-gconf/hardy uptodate 0.6.99+git20080210-0ubuntu1
compiz-core/hardy uptodate 1:0.7.0-0ubuntu3
compiz/hardy uptodate 1:0.7.0-0ubuntu3