Bug 12855 - Wrong Link To fglrx_dri.so Causes KDE Desktop Crashes & Video Corruption With ATI 6870 PCIe Card
Summary: Wrong Link To fglrx_dri.so Causes KDE Desktop Crashes & Video Corruption With...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-23 03:10 CET by John Smith
Modified: 2015-10-27 06:57 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description John Smith 2014-02-23 03:10:50 CET
Problems appeared as pages flashing in Chrome, sudden KDE crashes returning you to login. Also other video corruption, and reproducible when you hit Find on the Chrome menu the search box was invisible/incomplete while at Facebook, but not on all pages or other sites.

Running google-chrome from Konsole gave:

libGL error: open uki failed (Operation not permitted)
libGL error: reverting to (slow) indirect rendering

Also:

[john@localhost ~]$ LIBGL_DEBUG=verbose glxinfo > /dev/null
libGL: AtiGetClientDriverName: 13.25.5 fglrx (screen 0)
libGL error: OpenDriver: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]


The problems and the above "no such file error" went away by adding a link:

ln -s /usr/lib64/dri /usr/X11R6/lib64/modules

There were many small problems but Chrome gave the clues needed to fix it. This was a fresh install of Mageia 4 64 bit. 

I want to thank you guys while I'm here and I'm glad I could contribute something. It is posted in the forum to help other users, wouldn't want to scare them off.

Doktor said he didn't know if it was a Mageia or ATI package issue so I reported it. He don't use fglrx.

Life is good again!
Comment 1 Thomas Backlund 2014-02-23 04:11:01 CET
How did you install / configure fglrx ?

CC: (none) => tmb

Comment 2 John Smith 2014-02-23 05:57:56 CET
I installed the Proprietary driver, when ask, I said yes. I used the 64 bit DVD ISO. I didn't change anything until after I noticed the problem and had the error as shown. After finding the error I downloaded and installed the driver from the AMD site, and uninstalled it. It was called "amd-catalyst-13.12-linux-x86.x86_64.zip". It did make a link, and it linked to the whole folder at /usr/lib64/dri.

Trying to see if the Mageia driver had just installed wrong I re-installed it and the link was still missing, so I added the link and it has worked fine since then. On initial install I had no out of the ordinary reboots or any other problems.

One thing, Catalyst Control Center (Administrative) didn't want to run after initial install from DVD. It was a problem with amdccclesu. After Googling I just changed the link in the menu to make it work, linking direct to ccc with admin privileges, and not using amdccclesu. 

After uninstalling the Mageia fglrx the link to Catalyst Control Center (Administrative) in the menu works but it is exactly like it installed without modification this time. I may have had a glitched install. No one ever posted in the forum that they had the same problem, so I have nothing to compare to except the link was missing when I re-installed the driver from MCC.
Comment 3 John Smith 2014-02-23 06:12:20 CET
The last paragraph above should read "After re-installing the Mageia fglrx the link to Catalyst Control Center (Administrative) in the menu works but it is exactly like it installed without modification this time".
Comment 4 Samuel Verschelde 2015-09-21 13:19:49 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 5 Marja Van Waes 2015-10-27 06:57:07 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.