Display blank / won't refresh image after suspend/resume
joev...@gmail.com
https://github.com/QubesOS/qubes-issues/issues/3558
In RC4.0... After suspend/resume
Any monitors that were inverted or rotated, will be black.
The mouse does move across the screen... but no objects move on this screen.
Refreshing the configurations by toggling to another terminal (ctrl-alt-f2) then back again (ctrl-alt-f1), or changing the resolution/position of screens in xrandr/arandr/etc/... will restore the last known image on the affected monitors.
Reconfiguring the affected screen to remove invert/rotate settings does restore the image refreshing ability. The monitors behave normal, but I need them inverted.
Logging off or restarting X server does not fix the issue.
A reboot is needed to restore the desired behavior of having a working and inverted screen.
Very problematic as I do need to suspend resume a lot.
Ivan Mitev
(xrandr --output dispname --off) and un-rotating your primary display
(ie. getting back to a "clean" state) ?
That's what I used to have to do with my laptop docked: in that case I'd
use only my secondary larger monitor with the laptop's display turned
off and without turning on the primary display before suspending both
displays would stay off after resuming and I would have to type my
xscreensaver password and issue xrandr commands blindingly to turn on
one of the displays.
Note that I write "used to": a kernel update fixed the problem (some
weeks or months ago - can't remember) - both displays are now turned on
after resume. So the issue was likely not specific to Qubes.
Hope this helps.
Yuraeitha
Did you try restart LightDM in TTY2 terminal? As I understand it, it's a layer below the x-server because LightDM will start/stop the x-server whenever it's starting or stopping. You probably can't fix this issue which seems heavily XFCE4 related, by just restarting the x-server. You most likely need to go deeper, and restart the LightDM. Plenty of guides on the internet on how to do that btw, in case you need an approach.
It's not uncommon for XFCE4 to loose configuration files. Hard reset can for example mess-up the Whisker-menu XFCE4-panel plugin configuration files. Updates to the packages can cause old custom settings not to be loaded. And probably suspend/hibernate too.
Also it may be driver related, if some people can't reproduce your issue, then it's likely driver/hardware related issue, and perhaps blacklisting hardware so that a driver is unplugged before suspend/hibernate, and then automatically brought back after suspend/hibernate, may very well fix issues. But you need to know which driver that is causing the issue.
If its driver related, which it may very well be, then it can be as simple as changing your kernel version, or even xen version. If older versions do not work, then you may need to wait for a newer version.
It's my understanding possible that sometimes other code can trigger driver bugs, which were otherwise dormant. So it may not entirely be driver related, however, it does look like it's XFCE4/driver related. Maybe it's the graphic/screen driver. I'm not sure if a blacklist before/after suspend/hibernate of a graphic driver is feasible, but it may be another clue you could try look further into.