Description of problem: In Mageia 3 and 4, GTK+ programs can cause freezing when using the Nouveau drivers. The screen goes white with a few colored stripes; the keyboard isn't responsive either (you can't restart the X server with the keyboard). This occurs in both 32-bit and 64-bit versions. This can occur: 1. When opening more than two new tabs from external programs in Iceape. 2. It can also occur when opening new tabs from external programs in Firefox, but that tends to take longer (for example, on the 42nd new tab rather than the 3rd). The more consistent way, is to open and close Firefox 3 times. On the 4th time of starting it, this will occur. 3. In various other GTK+ programs in a less predictable manner. For example, this has occurred for me with Epiphany and Quadrapassel, but I haven't been able to reproduce. This doesn't occur with the Nouveau drivers in Mageia 2 and below, nor with the proprietary Nvidia drivers. I tried to install the old Nouveau drivers from Mageia 2, but I got an error about a wrong API version. It also doesn't occur in non-GTK+ alternative programs. For example, I've tried Arora for days and this hasn't happened yet (it just sucks up nearly all my system's resources). Version-Release number of selected component (if applicable): The versions of the X11 Nouveau drivers that come with Mageia 3 and 4 (1.0.6 and 1.0.10, respectively), I suppose. How reproducible: Almost without fail Steps to Reproduce: 1. Open a few external links in tabs in Iceape 2. Open and close Firefox a few times Reproducible: Steps to Reproduce:
Created attachment 5192 [details] A photo I took of my screen after this happens
CC: (none) => thierry.vignaud, tmbSource RPM: (none) => kernel, x11-driver-video-nouveauWhiteboard: (none) => MGA3TOO
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/
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 => RESOLVEDResolution: (none) => OLD