Bug 1729613 - Weird screen corruption in Chrome when playing videos and taking Alt+scrnshot
Summary: Weird screen corruption in Chrome when playing videos and taking Alt+scrnshot
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 30
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Lyude
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-07-12 21:27 UTC by Nico Pache
Modified: 2020-05-26 16:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-05-26 16:10:42 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
FreeDesktop.org 111140 0 None None None 2019-07-15 22:52:49 UTC

Description Nico Pache 2019-07-12 21:27:56 UTC
If chrome is in fullscreen mode and im logged into wayland, then it flickers with a checker patterned corruption, when playing videos or taking a alt+screenshot. 

prints: [10213:10213:0712/172530.549503:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 10 times!
to console

Comment 1 Ray Strode [halfline] 2019-07-12 21:30:58 UTC
Lyude says she wants to look at this so assigning to her.

It's some sort of corruption at swap buffers time.  The back buffer is getting garbled behind chrome's back and then it stays corrupted until surface resize.

might end up being a kernel issue or mutter issue.

Comment 2 Lyude 2019-07-15 22:42:00 UTC
Hi! There wasn't much info added to this bug since most of the discussion around it happened at the Red Hat office. Some more details:

The easiest way to reproduce this seems to be:

- Install chromium
- Play some video. Personally, I recommend https://www.youtube.com/watch?v=BqnG_Ei35JE
- Put the video into full screen
- Take a snapshot of *only the current window* using alt + print screen
- Shield your eyes and prepare for flicker. See an example using a high speed camera at https://people.freedesktop.org/~lyudess/archive/07-15-2019/VID_20190712_172307.mp4

I've confirmed this bug is present on both the HD 620 (using a ThinkPad T480s) and the HD 530 (using a ThinkPad P50's integrated GPU). It seems to be Intel specific, as I can't reproduce it elsewhere. I've also tested the latest mesa version (as of writing, 0ba508d7a3b6a006b5b8db1e865d33efc8d0abd5) and a drm-tip kernel (bbf4d95db6732b16547dc9d849701ccf4189aa0d) and have confirmed the issue is still present there. Will open an upstream bug for this in a moment.

Comment 3 Ben Cotton 2020-04-30 21:33:19 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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.

Comment 4 Ben Cotton 2020-05-26 16:10:42 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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

Thank you for reporting this bug and we are sorry it could not be fixed.

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