After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 780744 - Screenshot by window gives images with red and blue values swapped
Screenshot by window gives images with red and blue values swapped
Status: RESOLVED DUPLICATE of bug 779234
Product: mutter
Classification: Core
Component: general
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2017-03-30 21:55 UTC by Tianhao Chai
Modified: 2017-05-19 12:48 UTC
See Also:
GNOME target: ---
GNOME version: 3.23/3.24


Attachments
GIMP palette screenshot that has red and blue swapped (52.90 KB, image/png)
2017-03-30 21:55 UTC, Tianhao Chai
Details

Description Tianhao Chai 2017-03-30 21:55:29 UTC
Created attachment 349018 [details]
GIMP palette screenshot that has red and blue swapped

How to reproduce: Use either gnome-screenshot or Alt+PrintScreen key combination to take a screenshot of a window under focus.

Expecting: A regular screenshot of the window area

What Actually happened: Every pixel in screenshot image has BLUE and RED color values swapped as shown in attached image, as if using an big-endian encoding while I'm actually using little-endian x86_64. The actual orange (255, 128, 0) become light blueish (0, 128, 255) in image.

bug first enountered on Mar 28, 2017, right after I upgraded,

Current system:
gnome 3.24.0
Linux kernel 4.10.7
NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) with dkms driver version 378.13
Comment 1 Florian Müllner 2017-03-30 22:04:27 UTC
(In reply to Tianhao Chai from comment #0)
> Current system:
> gnome 3.24.0

Are you sure that mutter is at version 3.24.0? This sounds like an issue in 3.23.91 that was fixed by commit 95e9fa1 (in 3.23.92) ...
Comment 2 Tianhao Chai 2017-03-30 22:16:37 UTC
(In reply to Florian Müllner from comment #1)
> (In reply to Tianhao Chai from comment #0)
> > Current system:
> > gnome 3.24.0
> 
> Are you sure that mutter is at version 3.24.0? This sounds like an issue in
> 3.23.91 that was fixed by commit 95e9fa1 (in 3.23.92) ...

running `mutter --version` gives 3.24.0
Comment 3 Tianhao Chai 2017-03-30 23:49:04 UTC
I tried compiling mutter with that commit reverted. Problem still exists.
Comment 4 Jonas Ådahl 2017-03-31 01:20:33 UTC
Its probably still bug 779234 though. There is another regression probably related to assumptions about the format of a texture (see bug).
Comment 5 Tianhao Chai 2017-04-01 15:57:02 UTC
(In reply to Florian Müllner from comment #1)
> (In reply to Tianhao Chai from comment #0)
> > Current system:
> > gnome 3.24.0
> 
> Are you sure that mutter is at version 3.24.0? This sounds like an issue in
> 3.23.91 that was fixed by commit 95e9fa1 (in 3.23.92) ...

With that commit reverted, all screenshots (including fullscreen and region select) are in BGRA. That commit did fixed something, now fullscreen screenshot and screenshot over selected region is working normally, but that didn't fix for screenshot over selected window.
Comment 6 Otto Allmendinger 2017-04-27 13:13:59 UTC
I have the same issue. 

mutter 3.24.1
NVIDIA Corporation GK107 [GeForce GT 640] (rev a1)
nvidia 378.13-5


I noticed it in my screenshot extension:
https://github.com/OttoAllmendinger/gnome-shell-screenshot/issues/29
Comment 7 William Di Luigi 2017-05-02 20:07:54 UTC
I have this issue with GNOME 3.24.1

I wonder why it slipped into 3.24.1 if it was known very well into 3.24
Comment 8 Joshua Strobl 2017-05-19 10:04:35 UTC
Can confirm that issue is still present as of Mutter 3.24.2 and GNOME Shell 3.24.2.
Comment 9 Florian Müllner 2017-05-19 10:23:46 UTC
(In reply to Joshua Strobl from comment #8)
> Can confirm that issue is still present as of Mutter 3.24.2

Yes, nobody claimed otherwise. A more useful thing to confirm would be whether the last commit from bug 779234 fixes the issue (as it should).
Comment 10 Joshua Strobl 2017-05-19 11:09:40 UTC
Alright, no need to have an attitude.
Comment 11 Tianhao Chai 2017-05-19 11:13:27 UTC
(In reply to Florian Müllner from comment #9)
> (In reply to Joshua Strobl from comment #8)
> > Can confirm that issue is still present as of Mutter 3.24.2
> 
> Yes, nobody claimed otherwise. A more useful thing to confirm would be
> whether the last commit from bug 779234 fixes the issue (as it should).

see comment 5.
I cannot reproduce this bug on my Surface Pro 3 with Intel integrated graphics. This might has something to do with nvidia drivers.
Comment 12 Jonas Ådahl 2017-05-19 12:48:06 UTC
(In reply to Tianhao Chai from comment #11)
> (In reply to Florian Müllner from comment #9)
> > (In reply to Joshua Strobl from comment #8)
> > > Can confirm that issue is still present as of Mutter 3.24.2
> > 
> > Yes, nobody claimed otherwise. A more useful thing to confirm would be
> > whether the last commit from bug 779234 fixes the issue (as it should).
> 
> see comment 5.
> I cannot reproduce this bug on my Surface Pro 3 with Intel integrated
> graphics. This might has something to do with nvidia drivers.

I'm pretty sure this is the same as bug 779234, so I'm closing this as a duplicate. That bug was recently fixed, so if it doesn't fix the issue reported here, please reopen.

*** This bug has been marked as a duplicate of bug 779234 ***