On Sunday, January 5, 2020 at 9:49:42 PM UTC-5, Guerlan wrote: > can you tell me how you figured this out? I've been trying to fix a > suspend bug in mine and It'd be helpful to know how you debugged things >
Mostly trial and error, trying all the things listed above. Two little tricks to use: 1. Look at the end of journalctl right before it tries to suspend. This is where I saw that it was going into s2idle, which then brought me to this thread: https://groups.google.com/forum/#!msg/qubes-users/TmGDlkluJgM/1BFsQZWNDAAJ;context-place=forum/qubes-users This Dell did not have the lack of S3 that the new Thinkpads have, but it did still try to use s2idle. 2. Run speaker-test in dom0 before suspending, if you hear sound on resume then it's some sort of a screen problem. What hardware do you have? If it's corebooted you might want to check out this thread: https://groups.google.com/forum/#!msg/qubes-users/bHJJhK4HtIw/ieQkoJePCgAJ -- 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/a6723332-968f-45e1-a376-40cb7cc801c8%40googlegroups.com.
