Bug 13546

Summary: fglrx lose desktop transparency and effects after update (regression between kernel-3.12.21-2 & 3.12.20)
Product: Mageia Reporter: Cesar Vargas <cvargas>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: elegant.pegasus, linux, thierry.vignaud
Version: 4   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: kernel-3.12.21-2.mga4 CVE:
Status comment:

Description Cesar Vargas 2014-06-19 04:28:27 CEST
Description of problem:

I installed updates x11-common packages and their dependencies, fglrx and dkms and reboot the system, transparency effects disappear in the graphical environment.

Version-Release number of selected component (if applicable):

fglrx-control-center 14.010.1006
fglrx-kernel-3.12.13-desktop-2.mga4
kernel-desktop-3.12.21-2.mga4
libx11-common-1.6.2
OS: Mageia 4 thornicroft
KDE4
KWin
WM Theme: Laptop
GTK3 Theme: oxygen-gtk
CPU: AMD E-300 APU with Radeon HD Graphics @ 1.3GHz
GPU: AMD AMD/ATI Wrestler [Radeon HD 6310]
RAM: 406MB / 3539MB

How reproducible:
install new updates
reboot system
No transparency, no effects

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 psyca 2014-06-19 10:48:25 CEST
It seems like the last update breaks something.
I cant start Steam anymore since kernelupdate 3.12.21-2. "glXChooseVisual failed".
Also the Desktop shuttering/if i move windows on the desktop it shutters.
AMD Radeon HD7770 OC with propitary driver.

If i choose to start with the older Driver/Kernel (3.12.20) everything works fine.

CC: (none) => linux

Thierry Vignaud 2014-06-19 17:41:16 CEST

CC: (none) => thierry.vignaud
Assignee: bugsquad => tmb
Summary: Packages updated X11--common and fglrx lose desktop transparency and effects => fglrx lose desktop transparency and effects after update (regression between kernel-3.12.21-2 & 3.12.20)
Source RPM: (none) => kernel-3.12.21-2.mga4

Comment 2 Chih Wei Yao 2014-06-25 10:25:39 CEST
Confirmed here with x86_64 system. When using the desktop effect in KWin, selecting OpenGL backend would cause crash of KWin, switching back to 3.12.20 then works normally.

CC: (none) => elegant.pegasus
Hardware: i586 => All

Comment 3 psyca 2014-10-19 01:30:17 CEST
Seems to be fixed for me (since longer time).
Comment 4 Samuel Verschelde 2015-09-21 13:21:43 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:58:41 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