Alternative OpenGL lib's not updated when using closed drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have two computers, both are now running run Kubuntu 13.04 x86-64 editions (the desktop also has Ubuntu Studio 13.04 x86-64), both use closed source drivers (laptop has nVidia 9600M GS adapter, desktop has AMD Radeon HD 6770). Before upgrading, both system's and three *buntu's ran fine with all OpenGL lib's being pointed to correctly. After upgrading, the video library paths got cleared leaving me with virtually all my wine games seg faulting as well as native Linux games and programs (Skype 4.1, Doom 3, Quake Arena, etc). The problem really highlights it's self if the software wants to use OpenGL drivers.
I found a temperary fix by adding the video paths to these files:
/etc/ld.
/usr/lib32/fglrx (On the desktop)
/usr/lib32/
/etc/ld.
/usr/lib/fglrx #(On the desktop)
/usr/lib/
I tried updating the alternatives before I edited these files, and I just got a message back on the terminal saying there were no alternative's to configure.
This workaround works, but will need to be changed if these paths change at any time. Now this shouldn't pose a problem for FireGL Catalyst drivers, but it will pose problems for the nVidia drivers since the driver series and type (ie 313 series Updates driver) is noted in the directory.
After these two simple mod's, all my OpenGL programs (both native 64-bit and 32-bit Linux apps, and Wine programs) worked flawlessly.
This does not effect the open source nVidia and AMD drivers, the issue only shows up when using the closed nVidia and AMD binary blob's on *buntu 13.04.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1182677/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]