Bug 1733196 - After screenshot Chrome is flickering
Summary: After screenshot Chrome is flickering
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 30
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-25 11:39 UTC by Frank Ansari
Modified: 2019-08-05 08:30 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
Example screenshot how it looks like (313.09 KB, image/png)
2019-07-25 11:39 UTC, Frank Ansari
no flags Details


Links
System ID Priority Status Summary Last Updated
GNOME Gitlab GNOME/mutter/merge_requests/687 None None None 2019-08-05 08:30:43 UTC

Description Frank Ansari 2019-07-25 11:39:33 UTC
Created attachment 1593376 [details]
Example screenshot how it looks like

Description of problem:
When I take a screenshot (Alt-Print) the Chrome browser starts flickering. The complete screen is scrambled. Either by restarting Chrome or by making the Chrome area smaller (not maximizing) I get get rid of this.

This happens only when taking a screenhot of the current windows - when doing a screenshot of the whole screen I don't have this problem.

Also I only noticed this issue when taking screen shots inside of the Chrome browser.

Version-Release number of selected component (if applicable):
gnome-screenshot-3.32.0-1.fc30.x86_64
Chrome Version 75.0.3770.100 (Official Build) (64-bit)

How reproducible:
Open the Chrome browser. Take a screenshot with Alt-Print or open screenshot and take a screenshot of the current window inside of the Chrome browser.

Steps to Reproduce:
1.
2.
3.

Actual results:
Screenshot of current window results in flickering and scrambled screen.

Expected results:
Screenshots should not have such side effects.

Additional info:
I use Fedora 30 Silverblue.


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