Bug 359184

Summary:	Preview not working for small screenshots
Product:	[Applications] Spectacle	Reporter:	Elvis Angelaccio <elvis.angelaccio>
Component:	General	Assignee:	Boudhayan Gupta <me>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	francescortiz, peter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Elvis Angelaccio 2016-02-09 13:51:54 UTC

The preview of the screenshot is blank when the screenshot itself is "small", with respect to the screen size. However I can drop/export/save the screenshot just fine.

Reproducible: Always

Steps to Reproduce:
1. Take a small screenshot, e.g. using Rectangular region or a very small Active Window

Actual Results:  
Preview is blank.

Expected Results:  
Preview widget shows the screenshot as expected.

Comment 1 Elvis Angelaccio 2016-02-09 16:44:50 UTC

Note that I filed the bug from my desktop with proprietary Nvidia drivers.
I cannot reproduce it on my laptop with Intel graphics...

Comment 2 Boudhayan Gupta 2016-02-09 16:57:00 UTC

I only have an Intel GPU; I can't fix the bug if I can't repro it.

Comment 3 Elvis Angelaccio 2016-02-09 17:37:18 UTC

(In reply to Boudhayan Gupta from comment #2)
> I only have an Intel GPU; I can't fix the bug if I can't repro it.

I see. Well I can try to have a look at the code myself. Could you give me a hint about where should I start?

Comment 4 Boudhayan Gupta 2016-02-09 20:37:56 UTC

If when you save the picture a correct image is saved, then the image is being captured by the XCB backend correctly, in which case I strongly suspect this is a Qt bug, to do with the Qt Graphics View framework.

Comment 5 Francesc Ortiz 2016-03-13 11:03:56 UTC

Same problem. Additional details: whenever you resize the window to a size where the preview doesn't need to be downscaled, the preview is gone. If you downsize the window, the preview appears again. The image is always saved correctly.

Comment 6 Peter Wu 2016-10-06 22:58:05 UTC

See also bug 362450