Description of problem: This started to appear after upgrade to Fedora 25. Intel SNA video driver and Xfce with compiz. All workarounds in ccsm disabled (also tried various combinations without success. Rendering artifacts disappear after alt+tab or printscreen (thus I had to take a photo). Firefox doesn't seam to be affected. Maybe other applications are also affected, but I haven't time to check. It doesn't happen with e.g. metacity. Version-Release number of selected component (if applicable): compiz-0.8.12.3-3.fc25.x86_64 seamonkey-2.40-9.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Start seamonkey 2. Go to e.g. google.com 3. Type any string and hit enter 4. Scroll up and down Actual results: Rendering artifacts Expected results: No artifacts Additional info: I also tried to disable HW acceleration in Seamonkey but it didn't help.
Created attachment 1236390 [details] Rendering artifacts Double text, missing text, corrupted scrollbar.
Created attachment 1236391 [details] Corrupted scrollbar
I also encountered different artifacts in xchat - last message/line is usually unreadable.
Can you please report this directly to github? Personal i do not use compiz any more since Mate session use gtk3 (lovely) and this breakage by gtk+ in latest gtk3 version. https://github.com/compiz-reloaded/compiz/issues/40 caused by https://bugzilla.gnome.org/show_bug.cgi?id=768415 https://git.gnome.org/browse/gtk+/commit/?id=2c7b21718f18ab743cd79784ae28cad582f58503 Sorry, i don't have the energy any more to fight against windmills.
I think also that something is change in xorg since gnome use wayland as default. nouveau driver caused also reports. f25 release is really experimental for me.
(In reply to Wolfgang Ulbrich from comment #4) > Can you please report this directly to github? > NP, I will do. > Personal i do not use compiz any more since Mate session use gtk3 (lovely) > and this breakage by gtk+ in latest gtk3 version. > https://github.com/compiz-reloaded/compiz/issues/40 > caused by > https://bugzilla.gnome.org/show_bug.cgi?id=768415 > https://git.gnome.org/browse/gtk+/commit/ > ?id=2c7b21718f18ab743cd79784ae28cad582f58503 > Hmm, I am not sure whether it's the same issue. The moving windows, nor the desktop doesn't show any artifacts for me. After cca. 48 hours of heavy usage, it seems the problem manifests only in Seamonkey (menubar, iconbar, scrollbar, and also rendered web content). No problem with other apps and it also seems to work all correctly with Metacity. I am not sure regarding the Xchat - the problem there seems to disappear after switching on of some workarounds in ccsm. Hopefully I will do bisecting. It's Xorg, not Wayland. > Sorry, i don't have the energy any more to fight against windmills. > That's really sad to hear, your work was light in the darkness :)
Github report: https://github.com/compiz-reloaded/compiz/issues/56
(In reply to Jaroslav Škarvada from comment #6) > Xchat - the problem there seems to disappear after switching on of some > workarounds in ccsm. No, it still there.
It seems the problem was fixed by recent xorg update: xorg-x11-server-Xorg-1.19.1-1.fc25 I am going to test it more and if OK I will close this bug and upstream bug.
The problem is back with Xorg-1.19.1-2.fc25. It doesn't seem to be caused by gtk, but by xf86-video-intel DDX driver. The Xorg-1.19.1-1.fc25 switched to xf86-video-modesetting driver and the problem wasn't reproducible but Xorg-1.19.1-2.fc25 switched back to xf86-video-intel in f25 (probably due to some problem with Chrome) and the problem is back. I verified it by switching between xf86-video-intel and xf86-video-modesetting by hand. I am going to bisect the xf86-video-intel driver to find out whether it's really problem with the driver (I am curious :), but it seems so. However, the xf86-video-intel will be probably dropped in f26+ in favour of xf86-video-modesetting, so maybe this problem will go away without any our intervention :)
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.