On 07/06/2023 08:01, Ulrich Windl (Google) wrote:
Do you recognize any hardware activity when trying to resume?
Pressing any keyboard key causes the keyboard backlight to turn on for a
few seconds (which does not happen after pressing the power-on button).
What about journal messages in Dom0
This seems to be the relevant part of `journalctl` output:
Jun 08 11:24:55 dom0 systemd[1]: Starting Qubes suspend hooks...
Jun 08 11:24:57 dom0 52qubes-pause-vms[4634]: 0
Jun 08 11:24:57 dom0 systemd[1]: Finished Qubes suspend hooks.
Jun 08 11:24:57 dom0 audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=qubes-suspend comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Jun 08 11:24:57 dom0 kernel: audit: type=1130 audit(1686216297.032:303):
pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-suspend
comm="systemd" exe="/usr/lib/systemd/systemd" hos>
Jun 08 11:24:57 dom0 systemd[1]: Reached target Sleep.
Jun 08 11:24:57 dom0 systemd[1]: Starting Suspend...
Jun 08 11:24:57 dom0 systemd-sleep[4642]: Suspending system...
Jun 08 11:24:57 dom0 kernel: PM: suspend entry (s2idle)
-- Reboot --
Jun 08 11:28:06 dom0 kernel: Linux version
6.3.2-1.qubes.fc32.x86_64 ...
BTW, reporting on Qubes GitHub issue tracker, I've been pointed to
https://github.com/QubesOS/qubes-issues/issues/6411 where a likely
relevant discussion takes place.
Thanks for your reply,
Sylwester
--
https://slayoo.github.io/
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/db8ce9b9-417f-076f-96af-443acafe8cc2%40staszic.waw.pl.
