XCB errors in OpenGL applications caused by fglrx 11.8

Bug #877445 reported by Gregor Riepl
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
fglrx-installer-updates (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This applies to both fglrx and fglrx-updates, as they are currently both installing Catalyst 11.8.

When running certain OpenGL based applications in Ubuntu 11.10, they will crash with the following error:

[xcb] Extra reply data still left in queue
[xcb] This is most likely caused by a broken X extension library
[xcb] Aborting, sorry about that.
../../src/xcb_io.c:575: _XReply: Assertion `!xcb_xlib_extra_reply_data_left' failed.

Notably, wine is causing issues like this. Both official wine1.2 and wine1.3 from the ubuntu-wine PPA are affected.
Using winedbg, I have traced one cause of the error back to one of the libraries that come with fglrx. Can't seem to reproduce it now, though. Probably because certain debug symbols are missing.

I've tested Catalyst 11.9 from the AMD website last night (fglrx 8.892), and managed to get wine working with that.
It is still unclear to me if the issue lies in a library incompatibility (wrong libGL being picked, lib32 issue, etc.) or a bug in Catalyst. I used the installer script and made sure everything is in place manually.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: fglrx-updates 2:8.881-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Tue Oct 18 15:07:24 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=en_GB:en_US:en
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: fglrx-installer-updates
UpgradeStatus: Upgraded to oneiric on 2011-10-16 (1 days ago)

Revision history for this message
Gregor Riepl (onitake) wrote :
Revision history for this message
Gregor Riepl (onitake) wrote :

I experimented a bit more.
After removing libGL junk from /usr/lib32 and reinstalling ia32-libs, it seems wine is now picking up a libGL.so.1 that actually works. Most likely, it's the one from mesa (libgl1-mesa-glx). That one doesn't have this nasty XCB bug.
Is there a way to determine which libGL wine loads? ldd is not a great help here...

As for 64bit programs, they link against /usr/lib/fglrx/libGL.so.1 - and that works fine too.

Revision history for this message
tarek (tarek-allaoua) wrote :

Hi,
Ubunut 11.10 with Catalyst 11.8 and 11.9.
I have had the same crashes while playing with Imangination technologies OpenGLES 2.0 SDK.
examining strace output i have seen that my applications call libGL.so from /usr/lib32 open("/usr/lib32/libGL.so", O_RDONLY) which is a symlink to mesa/libGL.so.1 and not /usr/lib32/fglrx/libGL.so.1 !!
An ln -s /usr/lib32/fglrx/libGL.so.1 /usr/lib32/libGL.so fixed the problem, It worth a try. All my OpenGL applications are running perfectly right now :)

Good day.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fglrx-installer-updates (Ubuntu):
status: New → Confirmed
Revision history for this message
zed (zerohed) wrote :

Thanks to your help, I managed to find a fix (with a little tweak)
http://ubuntuforums.org/showthread.php?t=1870917

What I did:

sudo mv libGL.so libGL.so.bak
sudo ln -s /usr/lib32/fglrx/libGL.so.1 /usr/lib32/libGL.so

sudo mv libGL.so.1 libGL.so.1.bak
sudo ln -s /usr/lib32/fglrx/libGL.so.1 /usr/lib32/libGL.so.1

The fix didn't stick, so, I moved libGL.so.1.2 and linked it:

cd /usr/lib32/
sudo mv libGL.so.1.2 ~/libGL.so.1.2.bak
sudo ln -s /usr/lib32/fglrx/libGL.so.1 /usr/lib32/libGL.so.1.2

I'm not sure, but I think it has something to do with ati mobility chip sets, I had to do this fix with my PC which had: Radeon HD 3450.
However my other PC with Radeon HD 5450 had no problems.

Sheado reported that he had issue with /usr/lib instead of /usr/lib32.

Thanks again.

Revision history for this message
Kitsab (kitsab) wrote :

Hi,

I can confirm this issue. I've got the same problem thanks to zed, according his guide I was able to fix it.
 For me this issue appears after installing a new graphic acceleartor driver for my ATI Radeon (Catalyst 11.11). I also did some changes in unity and cpmpiz and tried to fix it with "unity --reset" and "dpkg-reconfiruge compiz".

Best regards

Kitsab

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.