MerrierWinter
commented
1 month ago I can post the full log or any log if requested , I made xscreensaver log to a file while testing suspend , here's what may be relevant
The first and last parts of the log (the omitted part is just devices detection) :
xscreensaver: 00:49:16.97: warning: $DISPLAY is not set: defaulting to ":0.0"
xscreensaver: 00:49:16.99: pid 6755: launched xscreensaver-auth --init --verbose
xscreensaver: 00:49:16.99: pid 6756: launched xscreensaver-systemd --verbose
xscreensaver-auth: 00:49:17.01: OOM: echo -1000 > /proc/6754/oom_score_adj
xscreensaver-auth: 00:49:17.01: initial effective uid/gid was root/user (0/1000)
xscreensaver-auth: 00:49:17.01: changed uid/gid to user/user (1000/1000)
xscreensaver-systemd: 00:49:17.01: registered as "org.jwz.XScreenSaver"
xscreensaver-systemd: 00:49:17.01: registered as "org.freedesktop.ScreenSaver"
xscreensaver-systemd: 00:49:17.01: "org.gnome.SessionManager" not in use
xscreensaver-systemd: 00:49:17.01: "org.kde.Solid.PowerManagement.PolicyAgent" not in use
xscreensaver: 00:52:26.33: SIGHUP received: restarting
xscreensaver: 00:52:26.33: pid 6756: killing xscreensaver-systemd ```
How to file a helpful issue
Qubes OS release
Qubes R4.2.2
Brief summary
When logging in into a sys-gui session (GUI Domain), and then suspending to RAM . I can't recover from suspending
all I can see on screen is the cursor , the screen turns dark but I can still switch to tty2 to reboot
Tested on 3 devices where suspend works well without sys-gui
Steps to reproduce
1- Setup sys-gui as mentioned in documentation 2- make sys-gui the default_guivm 3- login in sys-gui (GUI Domain) session. 4- suspend to RAM
Expected behavior
That Waking from suspend is possible
Actual behavior
Waking from suspend is not possible, and only the cursor is visible after suspending