Arch Linux

reygoch

Member

Registered: 2015-02-11

Posts: 9

Corrupted screen on wakeup (gnome / gdm)

Hi,

When I suspend my laptop by closing the lid, and open it again, login screen is totally corrupted and I need to suspend it again by pressing power button and wake it up again by power button to fix the screen.

It is not that I get artifacts and small glitches like I've seen some posts describe, I get white/gray noise stretched from top to bottom of a screen like a barcode. This was happening on my previous laptop as well which had ATI radeon video card.

Is this some kind of bug in GDM/Gnome or is it misconfiguration on my part? Intel drivers are installed properly as far as I can tell.

---

While I'm at it, it seems like Chrome is sometimes not refreshing the screen after I switch tabs or snap him from full screen to the left or right. I've read it's some kind of bug but I'm wondering if there's some kind of tweak that can fix it.

Last edited by reygoch (2015-09-10 19:57:58)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: Corrupted screen on wakeup (gnome / gdm)

Likely a result of the current SNA issues with intel adapters: https://wiki.archlinux.org/index.php/In … SNA_issues

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Corrupted screen on wakeup (gnome / gdm)

If you have wayland installed, GDM tries to use it as backend since 3.16. If that's causing your issue after suspend, you can still use Xorg instead: https://wiki.archlinux.org/index.php/GD … rg_backend

I have the same redrawing issue with chromium, and I know it's caused by SNA acceleration together with various other screen artifacts (although I don't let it bother me that much as I believe SNA is still the fastest AccelMethod).

reygoch

Member

Registered: 2015-02-11

Posts: 9

Re: Corrupted screen on wakeup (gnome / gdm)

Nope, I've tried those tips from wiki. They don't work. @V1del notice I said this was happening on ATI card as well.

I have just noticed that If I let my screen turn off while on login than everything get's back to normal after I move my mouse.

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Corrupted screen on wakeup (gnome / gdm)

Odd.. Did double check that SNA got disabled for sure from xorg logs?

grep -i sna /var/log/Xorg.0.log
grep -i uxa /var/log/Xorg.0.log

reygoch

Member

Registered: 2015-02-11

Posts: 9

Re: Corrupted screen on wakeup (gnome / gdm)

@ooo you are right. It wasn't disabled. Any way to force it?

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Corrupted screen on wakeup (gnome / gdm)

did you precisely copy the /etc/X11/xorg.conf.d/20-intel.conf file from the wiki article V1del linked? Afaik that should take care of it.
If you did, I've got not idea what could be wrong, but I can test if it works on my system tomorrow.

Last edited by ooo (2015-09-10 22:39:17)

reygoch

Member

Registered: 2015-02-11

Posts: 9

Re: Corrupted screen on wakeup (gnome / gdm)

yes, file exists, and this is what I get when I run your commands:

[     3.165] (II) intel(0): SNA compiled from 2.99.917-381-g5772556
[     3.169] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend

reygoch [~] λ ls /etc/X11/xorg.conf.d/
00-keyboard.conf  20-intel.conf

reygoch [~] λ cat /etc/X11/xorg.conf.d/20-intel.conf 
Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod"  "uxa"
EndSection

Last edited by reygoch (2015-09-10 23:01:39)

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Corrupted screen on wakeup (gnome / gdm)

I forgot that since 1.16, you can run xorg without root privileges, and in that case the Xorg.0.log file you should check is located in ~/.local/share/xorg/ instead of /var/log/, so you might have checked the wrong log file. You can figure out which is the right one by checking the creation times, or the timestamp on log file.

Sorry about the confusion.

EDIT: Apparently with GDM, Xorg logs are stored in systemd's journal. So you should check it instead of the log files: http://who-t.blogspot.fi/2014/03/viewin … alctl.html
Sorry about even more confusion

I also tested that the chromium bug persists even when using UXA or Glamor, so it's not a SNA bug after all. Have you tested if this happens with other window managers? I'm seeing this in gnome too, so it could be a bug in mutter.

I'm not using GDM and haven't experienced such issue after waking up from suspend, so I have no idea what could be causing it you have the issue using both wayland and xorg backends. You could try if some other login manager or no login manager at all worked any better though.

Last edited by ooo (2015-09-12 00:28:55)