FS#48913 - [mutter] Display corruption after resuming from suspend

Attached to Project: Arch Linux
Opened by Marco Scannadinari (marcoms) - Tuesday, 12 April 2016, 17:31 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 26 October 2016, 08:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
After resuming from suspend, the screen might have inverted colours or "noisy" output. Running Alt+F2 -> "r" -> Return, or switching to another TTY and back again fixes it. Perhaps it might be a gnome-shell bug or even mesa? I didn't have this bug when using fglrx, though now I use radeon.

Additional info:
* gnome-shell 3.20.0-2
* mesa 11.2.0-1
* mesa-libgl 11.2.0-1


Steps to reproduce:
1. Wait for suspend timeout OR run "systemctl suspend"
2. Resume from suspend
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 26 October 2016, 08:45 GMT
Reason for closing:  No response
Comment by Marco Scannadinari (marcoms) - Tuesday, 12 April 2016, 17:40 GMT
This might be a gnome-shell issue, I tested suspending on both i3 and twm, and there was no corruption. Also, I think I only get inverted colours when it is suspended by the timeout, and the other corruption (in the attachment) I get when I manually run "systemctl suspend"
Comment by patrick (potomac) - Wednesday, 13 April 2016, 00:19 GMT
I notice also a corruption display ( plasma 5, radeon HD4650 pcie, radeon driver ) since a recent upgrade ( maybe mesa or Xorg ),

when the corruption occurs what I see is a permanent white pixel on coordinates "0,0", the first pixel on the screen, even if the image is black,

but if I immediatly switch to another shell ( ctrl-alt-f2 ) and then go back to the X session then it fixes the corruption, no permanent white pixel on coordinates "0,0",

so the bug can occur randomly, not only after resuming from suspend, it can happen anytime
Comment by Marco Scannadinari (marcoms) - Wednesday, 13 April 2016, 07:33 GMT
That seems like a unique issue that you should report.. This one always occurs after suspend and corrupts the whole screen, and isn't random like in your case.
Comment by Marco Scannadinari (marcoms) - Wednesday, 13 April 2016, 13:40 GMT
I have managed to take a picture of the other kind of corruption that occurs after a timeout suspend. The photo is attached.
Comment by Marco Scannadinari (marcoms) - Wednesday, 13 April 2016, 13:41 GMT
Here is a photo of the original picture. The colours appear to be inverted, or something like that.
Comment by Jan de Groot (JGC) - Thursday, 13 October 2016, 09:21 GMT
Is this still an issue with 3.22?

Loading...