Upgrading from 6.06 to Hardy, something installed GL libs to /usr/lib/xorg

Bug #224223 reported by toobitz
10
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Michael Vogt
Hardy
Won't Fix
Undecided
Unassigned
xserver-xorg-video-ati (Ubuntu)
Invalid
Undecided
Unassigned
Hardy
Won't Fix
Undecided
Unassigned

Bug Description

Hardware: IBM Thinkpad T43p
Video card: 01:00.0 VGA compatible controller: ATI Technologies Inc M24GL [Mobility FireGL V3200] (rev 80)
Kernel: Linux ubuntu 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux
Distribution: Ubuntu 8.04 LTS (Hardy)

I've been using the Open Source ATI driver on Gutsy as well as Compiz for desktop effects which worked flawlessly. After upgrading to Hardy, compiz won't start anymore i.e. Extra Visual Effects can't be enabled anymore (message: "Desktop effects could not be enabled").

When setting SKIP_CHECKS=yes and starting compiz from within a terminal, it yields the following:

Checking for Xgl: not present.
Found laptop using ati driver.
Found laptop using radeon driver.
Detected PCI ID for VGA: 01:00.0 0300: 1002:3154 (rev 80) (prog-if 00 [VGA controller])
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: not present.
SKIP_CHECKS is yes, so continuing despite problems.
Checking for nVidia: not present.
Checking for FBConfig: present.
Checking for Xgl: not present.
/usr/bin/compiz.real (core) - Fatal: GLX_EXT_texture_from_pixmap is missing
/usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
/usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :0.0
Window manager warning: "" found in configuration database is not a valid value for keybinding "toggle_shaded"
Window manager warning: "Disabled" found in configuration database is not a valid value for keybinding "switch_windows"

Attachments:
- output of "LIBGL_DEBUG=verbose glxinfo"
- xorg.conf
- Xorg.0.log

If I need to provide more information I'm happy to do so!

Revision history for this message
toobitz (kil-gnu) wrote :
Revision history for this message
toobitz (kil-gnu) wrote :

Attachment: xorg.conf

Revision history for this message
toobitz (kil-gnu) wrote :

Attachment: Xorg.0.log

Revision history for this message
toobitz (kil-gnu) wrote :

I don't really see why this is a duplicate of bug 201330 - in that bug, setting SKIP_CHECKS=yes before starting Compiz does the trick whereas in my case it does not as my bug report clearly states... or am I missing something here?

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Sorry, my mistake.

Revision history for this message
Travis Watkins (amaranth) wrote :

libGL error: unable to find driver: r300_dri.so

That bit in glxinfo means this is either a driver problem or a user problem. Right now no 3D application on your system will work, not just compiz.

Revision history for this message
toobitz (kil-gnu) wrote :

OK, I figured it out, I assume it was my own mistake, but I'm not entirely sure. Here's what I found out:

My $LD_LIBRARY_PATH was set to "/usr/lib/xorg". This directory held the following files:

lrwxrwxrwx 1 root root 26 2007-10-23 19:12 /usr/lib/xorg/libGL.so -> /usr/lib/xorg/libGL.so.1.2
lrwxrwxrwx 1 root root 26 2007-10-23 19:12 /usr/lib/xorg/libGL.so.1 -> /usr/lib/xorg/libGL.so.1.2
-rw-r--r-- 1 root root 783362 2007-10-23 19:12 /usr/lib/xorg/libGL.so.1.2

Now these files are also under "/usr/lib":

lrwxrwxrwx 1 root root 10 2008-04-30 09:48 /usr/lib/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root 12 2008-04-30 09:48 /usr/lib/libGL.so.1 -> libGL.so.1.2
-rw-r--r-- 1 root root 394924 2008-04-06 00:06 /usr/lib/libGL.so.1.2

As one can see, the file size of libGL.so.1.2 does not match so these are not the same libs. Furthermore, the files under "/usr/lib" belong to the package libgl1-mesa-glx but the files under "/usr/lib/xorg" do not belong to any package. So while the package was correctly installed, the setting from $LD_LIBRARY_PATH was overriding them and the wrong libs from "/usr/lib/xorg" were used, hence the strange error.

Now it is very well possible that I caused this whole mess by myself via a manual install of something (although I did not install the mesa libs by myself at any time) but I dist-upgraded this computer regurarly since Ubuntu 6.06, so... I thought I'd write my experiences down here in case somebody else is experiencing the same problem.

Revision history for this message
Bryce Harrington (bryce) wrote :

mvo, could you post your comments on this one?

Is it possible that toobitz may have installed something 3rd-partyish some time between 6.06 and now, that put the GL libs there?

Changed in compiz:
assignee: nobody → mvo
Bryce Harrington (bryce)
Changed in xserver-xorg-video-ati:
status: New → Incomplete
Revision history for this message
Kjell Braden (afflux) wrote :

Not a compiz bug.

Changed in compiz:
status: New → Invalid
Revision history for this message
Brian Murray (brian-murray) wrote : Ubuntu needs you!

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

Revision history for this message
Bryce Harrington (bryce) wrote :

Not an issue for Intrepid. I'll open a Hardy task instead.

Changed in xserver-xorg-video-ati:
status: Incomplete → Invalid
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix".

Changed in compiz (Ubuntu Hardy):
status: New → Won't Fix
Changed in xserver-xorg-video-ati (Ubuntu Hardy):
status: New → Won't Fix
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.