Bug 12623 - nvidia driver causes GLX issues when present
Summary: nvidia driver causes GLX issues when present
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 02:12 CET by Doug Laidlaw
Modified: 2015-09-21 13:25 CEST (History)
2 users (show)

See Also:
Source RPM: nvidia
CVE:
Status comment:


Attachments

Description Doug Laidlaw 2014-02-06 02:12:36 CET
(Split from Bug 12108.)

Having nvidia driver present on the system, even though not the active driver, causes message:

"No GLX extension on display 0:0"

and consequent inability to display graphics.  In xscreensaver, the only hack that still works is the default Mageia one.  Even 2D hacks won't start.

Totally removing 

dkms-nvidia-current
nvidia-current kernel (and the -latest file)
nvidia-current-doc
x11-driver-video-nvidia-current

fixes the problem.

Haven't tested removing those one at a time.

Reproducible: 

Steps to Reproduce:
Comment 1 Doug Laidlaw 2014-02-12 23:21:24 CET
This particular issue seems fixed by the latest nvidia download in Cauldron, although it still won't work as a driver.
Manuel Hiebel 2014-02-16 18:07:47 CET

CC: (none) => anssi.hannula, tmb

Comment 2 Doug Laidlaw 2014-07-02 18:31:15 CEST
I installed Mga4 64-bit, and had no problems.

For other reasons, I reverted to 32-bit.

The GLX error doesn't show, but xscreensaver still fails.
Comment 3 Samuel Verschelde 2015-09-21 13:18:06 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 4 Doug Laidlaw 2015-09-21 13:25:30 CEST
Seems to be history.

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


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