I'm not sure whether this is a dupe of #1468 , but it seems to be somehow different.
When taking screenshots of a certain area, the area will be covered by a blue mask as a visual effect, and the mask is often captured together with the screenshot.
For example,

I haven't seen that before. What screenshot tool are you using? Also what version of Cinnamon and which video driver and version are you running?
@rjanja I'm using Fedora which comes with GNOME so gnome-screenshot is used.
Oh, forgot to paste the version numbers...
I'm using Cinnamon 2.6.13 and the official Nvidia driver 352.41
Driver issue sounds plausible, had a lot of problems with the official nvidia driver on my main machine. I'll try to reproduce there the next time I'm at home, will take about two weaks though...
A bit late, just retried with gnome-screenshot-3.20.2 on Arch Linux, still not reproducible.
I also don't think that this is somehow related to cinnamon
Does this still occur on your setup with latest cinnamon 3.0.x?
@ManIVIctorious your keeping me busy while I drink my morning coffee ;)
Well, different time zones ;), I'll now take my evening meal, good day
@JosephMcc, can we close the issue?
First sorry if its not cinnamon issues. But this bugs also occur within
ubuntu 16.04 + gnome classic. Reproduce:
```

I have this on two computers as well, a laptop and desktop, both with nvidia (gtx970, gtx1070 and gt940m). It doesnt happen all of the time, but often enough to be annoying. Cinnamon 3.6.7 Gnome-Screenshot version 3.18.0
I have this exact issue on Arch Linux, Gnome 3.28.2 with Wayland
Changed to Antergos, have this issue again with Cinnamon 3.8.9 and gnome-screenshot 3.30.0
Have this issue on Cinnamon 3.6.7 and gnome-screenshot 3.25.0, reproduces randomly
Same here with cinnamon 3.8.9-1 and gnome-screenshot 3.30.0-1, it doesn't happen all the time but at least 80%. Can we please reopen this issue?
Most helpful comment
Same here with cinnamon 3.8.9-1 and gnome-screenshot 3.30.0-1, it doesn't happen all the time but at least 80%. Can we please reopen this issue?