Comment 0 for bug 1622544

Revision history for this message
Travis Appleby (auravulpes) wrote : Zazam secondary monitor won't are screenshot correctly

So after trying to screenshot an image on my secondary screen
I noticed that there were 2 bugs I found with Kazam v1.4.5

The first one i will explain here and the other
on a separate report as they are separate bugs..

With this one in particular, there is an issue with capturing using the "area" setting
on the secondary monitor, Fullscreen on both screens work fine and return with a full
image with good results (apart from the graphical glitch now and then..) and taking a
screenshot using area on my primary display works fine, however using area capture on the
second monitor results in the output file being empty, uncolored and completely transparent..

Had to use my phone in order to show the screens and results..
I apologize if some images are too bright or blurry..

My 2 Monitors, an ACER and a Gateway, unsure what models :/
http://i.imgur.com/gmyKUv2.jpg

Fullscreen Screenshot Monitor 1 (Primary):
Capturing = http://i.imgur.com/7NqFE2m.jpg
Result = http://i.imgur.com/0D2KhH3.jpg

Fullscreen Screenshot Monitor 2 (Secondary):
Capturing = http://i.imgur.com/zXfoAIJ.jpg
Result = http://i.imgur.com/5qzkt0i.jpg

Area Screenshot Monitor 1:
Capturing = http://i.imgur.com/XblO1Na.jpg
Result = http://i.imgur.com/EGTiMEd.jpg

Area Screenshot Monitor 2:
Capturing = http://i.imgur.com/JVdXNNO.jpg
Result = http://i.imgur.com/64ftg7u.jpg

It should be noted that i couldn't capture this part, but upon trying to
area capture the second screen, when the capture happens, there is a small
white flicker on the primary monitor, usually in the corner.. Unsure if that
has to do with this issue but it is likely as it may be that it's still trying
to capture on my primary monitor but the "capture box" is on the second screen
instead of recording that it is perhaps recording the transparent areas of the
main monitor but with the offset from the secondary monitor's area capture box
relative to the resolution of the main screen..

In other words it's possibly capturing where the second screen is, but
still capturing using the primary display screen, but that's just my theory..

Anyways, this is my report on this bug, and i hope
it can be resolved/fixed for a future version..

~auravulpes