© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Having fglrx installed replaces the open-source libGL with ATI's libGL, so you can't have both at once.
$ dpkg -S /usr/lib/libGL.so*
libgl1-mesa-dev: /usr/lib/libGL.so
libgl1-mesa-glx: /usr/lib/libGL.so.1
diversion by xorg-driver-fglrx from: /usr/lib/
diversion by xorg-driver-fglrx to: /usr/lib/
xorg-driver-fglrx, libgl1-mesa-glx: /usr/lib/
Removing fglrx removes the diversions, putting the mesa version back.
I see you already fixed your "i810" -> "intel" problem.
I've retitled this bug to what it's really about, and removed the hw-specific and regression tags. This package has always worked this way, by moving aside the mesa libGL. The NVidia binary drivers work the same way. And it's a "dll hell" problem, not a hw-specific problem at all.
This could either be marked as invalid, or left around forever to mark this as a known issue. Unless /usr/lib/libGL is replaced with a wrapper library that can use whatever's available, I don't see how this could ever be solved. I think it does belong assigned to fglrx-installer, because it's replacing libGL with a libGL that doesn't support mesa anymore.
That sucks that a system with heterogeneous GPUs, some of which use non-mesa drivers, can't do 3D on all heads without a chroot or ld.so tricks/env vars.