Enemy Territory Quake Wars saves 32 bit TGA screenshots, and the alpha value of the pixels is set to 0x00 instead of 0xFF. Team Fortress 2 saves 24 bit TGA screenshots (before converting to jpeg), and the whole thing is black. I also tried Doom3, Prey, Quakespasm, Nexuiz, UT2004, Half-Life 1, and Garry's Mod but those are not affected. This is a regression, but I couldn't find an old version of mesa that worked. I went back as far as to 5ffa28df4e4cc224 (the first one that compiles with bison 3), and libdrm 2.4.44, but couldn't find a version that was good. When screenshots were good, I had mesa 9.2.2 installed, and I used 10.0-dev for running games. Now I have 10.1 installed. Maybe I need to roll back the installed libs?
Created attachment 98088 [details] etqw.tga.bz2
Possibly a duplicate of bug 77553. See also: http://lists.freedesktop.org/archives/mesa-dev/2014-April/058594.html
Bug 77553 mentions commit 234db609544ee521458ce8b648e70cffe2fda6f9 as the culprit, but my git checkout is definitely earlier than that, and mesa 10.1.0-5 in Debian Sid shouldn't contain it, either.
Now TF2 screenshots are good. I didn't change anything on my system, maybe it was a TF2 issue, and it was fixed by Valve. ETQW is still wrong.
I don't think this is a Mesa bug. I already noted this problem with ETQW back to July 2012 (maybe even earlier) and found a workaround. You can convert the picture to PNG thanks to ImageMagick, just run : $ convert -alpha off shot00016.tga shot00016.png With my RV770, I just tested mesa-10.3-rc2, mesa-9.2.5 and mesa-9.1.7. All of them gives bad TGA screenshots.
Some update on this: in TF2 only the first screenshot is black, but subsequent ones are good.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/507.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.