Description of problem: When browsing the Mate user's guide, sometimes the window body blanks (text not visible), and occasionally, the system freezes (for a minute or so) - only the mouse is live. When the window is blanked the text is "still there", you just can't see it - moving the mouse over the window, the mouse shape will change when you are over an invisible button. Version-Release number of selected component (if applicable): mate-user-guide.noarch 1.16.0-1.fc25 How reproducible: Fairly - usually within a minute or two of trying to cause the problem, or just trying to browse the user's guide. Switching to another window, and switching back sometimes seems to trigger it. The problem has happened from time to time over the last 5 days (when I migrated to F25). Steps to Reproduce: 1. From Pluma, select help, to view the pluma user's guide 2. Browse the help. Sometimes just scrolling down (using the mouse and scroll bar) in help seems to trigger it. I have not discovered any way to consistently force the problem to occur. Switching to another window, then switching back, seems to cause it. Switching to pluma, then switching tabs, then switching back may cause it, but not consistently. It may be that just opening the user's guide, then switching to another screen for a few minutes will trigger it. Actual results: Sometimes the help window body blanks out. You have to close help, and re-open it to see the help text. If the system freezes (except for the mouse movement), switching to a console doesn't work - or rather it may work, after a minute or so, when the system "comes back". Expected results: Browse user's guide without problems. Additional info: The blanking of the window body is reminiscent of the current bug with the blank screensaver. The journal doesn't show any problems. The following .xsession-errors message is suspicious, but it only occurs once, and this problem has occurred maybe half a dozen times during the last hour: /usr/share/help/C/creating-marco-themes/index.docbook:4: I/O warning : failed to load external entity "/usr/share/help/C/creating-marco-themes/docbookx.dtd" ]> ^
Another instance: I opened the user's guide, and let the machine sit for 5 minutes or so. Then I went back to check on it. The user's guide text was still visible. I had a couple of notifications on the screen, so I moved the mouse to clear the notifications. As the cusor swept across the window, the text blanked out.
It appears that this may be another problem related to xorg-x11-drv-nouveau. When I turn off hardware acceleration, it appears to solve this problem. So, I'm not sure if the bug component should be "mate-users-guide", "xorg-x11-drv-nouveau", or something else in between.
(In reply to Don Swaner from comment #2) > It appears that this may be another problem related to xorg-x11-drv-nouveau. > When I turn off hardware acceleration, it appears to solve this problem. > So, I'm not sure if the bug component should be "mate-users-guide", > "xorg-x11-drv-nouveau", or something else in between. The application itself is the yelp browser which use a context mate-user-guide or gnome-user-guide. I am happy with using origin nvidia driver, so i don't see all those issues and can't say if it is a yelp or nouveau issue.
I've been using nouveau for many years and never had problems either. Now I've got 3 issues that seem to be nouveau issues: 1) mediawriter freezing; 2) eom not displaying some images; 3) yelp window blanking and/or freezing. I'm not sure who should close and/or reassign the 2 mate bugs to nouveau (or open a new nouveau bug), you (the assigned developer) or me (the end user reporting the bug)?
You should be able to reassign a report to another component as reporter. But i will do that for you and reassign it to nouveau because of your list.
Output of /sbin/lspci | grep -e VGA 00:05.0 VGA compatible controller: NVIDIA Corporation C51 [GeForce 6150 LE] (rev a2). When hardware acceleration is turned off, mediawriter, eom, and yelp work without problems.
In a gnome desktop, with "nouveau.noaccel=1" boot parm, eog (Gnome Image Viewer) works fine. With acceleration on, some images do not display (as per Mate eom). Also, with acceleration turned on, sometimes gnome-shell aborts while starting up.
With hardware acceleration ON, using eom (Eye of Mate), trying to view image /usr/share/backgrounds/f25/extras/milky-way-over-mangart-mountain.jpg, the image does not display and the following errors are recorded in the journal: ... PROODF25.LINUX2C.home kernel: nouveau 0000:00:05.0: Xorg[770]: fail ttm_validate ... PRODF25.LINUX2C.home kernel: nouveau 0000:00:05.0: Xorg[770]: validating bo list ... PRODF25.LINUX2C.home kernel: nouveau 0000:00:05.0: Xorg[770]: validate: -12
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.