Compiz+fglrx breaks 3d apps

[Psy[H[]]

Binary package hint: compiz

Radeon HD2400, fglrx from restricted repo, up to date karmic.

Compiz, either currently running or once launched in current X session, breaks 3d applications:
tested with stellarium (segfault), urbanterror (heavy fps drop), sauerbraten (heavy fps drop, garbled textures).

Even if compiz no longer running, normal 3d functionality can only be restored by restarting X.

Also tested: metacity with enabled compositing, xcompmgr - caused no problems. So it is explicitly fglrx+compiz problem.

It also differs from nvidia situation where any active compositing, regardless of its source, causes heavy fps drop, but 3d restores back to normal once compositing is turned off.

ProblemType: Bug
Architecture: i386
Date: Thu Nov 5 22:42:33 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: ASUSTeK Computer Inc. A8SR
NonfreeKernelModules: fglrx
Package: xorg-driver-fglrx 2:8.660-0ubuntu4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=25fa5637-7969-48c6-b8f3-06a4a4b8b057 ro quiet splash
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu9
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: fglrx-installer
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:4381): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:4442): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:4415): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24
 (nautilus:4416): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 05/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: A8SR
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr301:bd05/14/2008:svnASUSTeKComputerInc.:pnA8SR:pvr1.0:rvnASUSTeKComputerInc.:rnA8SR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: A8SR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

[Psy[H[] (vovik-wfa)]

...with 10.2 drivers X restart is no longer required. 3d functionality is restored right after compiz is turned off.

[Psy[H[] (vovik-wfa)]

...no, i've made mistake. X restart is still required after compiz usage.

sauerbraten exits with error: cannot find shader definitions

[Psy[H[] (vovik-wfa)]

bug presents in current Lucid

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Psy[H[],

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 475793

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 475793 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/475793

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Psy[H[] (vovik-wfa)]

I've tested it on lucid with current updates, with both fglrx from ubuntu repo and latest 10.5 catalyst.
On both the problem still exist.
Although i've managed to run sauerbraten several times on 10.5 with compiz running. But another several times it again crashed with "cannot find shader definitions" error, had to restart X to make it work again.
Minor texture glitches are also present.

[Kristian Kißling (kkissling)]

I might add some information: if you start sauerbraten with option "-f0" it actually starts. But I don't know what "-f0" really does. Otherwise I can confirm this error "cannot find shader...".