Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9282 - Incorrect fglrx_dri.so path

Attached to Project: Arch Linux
Opened by Anthony Nguyen (Navi) - Monday, 21 January 2008, 03:46 GMT
Last edited by Greg (dolby) - Sunday, 18 May 2008, 23:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Travis Willard (Cerebral)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
For DRI, X looks to /usr/X11R6/lib64/modules/dri/ for fglrx_dri.so. However, catalyst-utils installs it to /usr/lib/xorg/modules/dri/fglrx_dri.so.

Additional info:
* package version(s)
- catalyst-utils 7.12-1
* config and/or log files etc.
- http://pastebin.archlinux.org/24525
This task depends upon

Closed by  Greg (dolby)
Sunday, 18 May 2008, 23:36 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Monday, 21 January 2008, 07:33 GMT
Can you print the output of "export | grep X11R6"? I think there's some environment path set for the xorg loadable module path. This one could be in your xorg.conf aswell.
Comment by Travis Willard (Cerebral) - Friday, 09 May 2008, 21:16 GMT
added JGC - this doesn't seem like an fglrx issue - we shouldn't be using /usr/X11R6/ anywhere anymore.
Comment by Jan de Groot (JGC) - Saturday, 10 May 2008, 13:57 GMT
This is an fglrx issue though: it's libGL that actually loads these DRI modules when DRI is requested. As fglrx ships its own libGL, it's something in the libGL shipped with fglrx. I don't know if this is hardcoded in libGL included with fglrx or if it's an environment variable set, I haven't seen any response since january on my question about this, so I assume this is not a bug anymore and can get closed.
Comment by Travis Willard (Cerebral) - Saturday, 10 May 2008, 14:06 GMT
Oh geez, I didn't even notice how long this bug's been open. Traditionally fglrx used an environment variable, and as such I've got a profile.d script that sets it to the appropriate value packaged with catalyst-utils.

Perhaps the original submitter didn't get the profile.d script sourced after first installing catalyst-utils, and noticed the issue.

It would be nice to know if it's still happening, or at least be able to see the value of echo $LIBGL_DRIVERS_PATH on their system
Comment by Travis Willard (Cerebral) - Saturday, 10 May 2008, 14:09 GMT
I'll give it a week, and if we don't get a response, I'll close it. They can always request a re-open

Loading...