On Fri, May 13, 2022 at 11:11:47AM +0100, Laurence Tratt wrote: > On Tue, May 10, 2022 at 09:26:48PM +0100, Laurence Tratt wrote: > > > Maybe! Would that device have some sort of interaction with X one way or > > another? Because it seems that I can reliably suspend/resume if xenodm is > > on the login page, but after I've logged in via xenodm, suspend rarely > > works and, if it does, resume almost certainly doesn't. > > Partly based on a prompt from Mike Larkin, I went through all my running > applications to see if anything caused suspend problems and I believe I've > now found the culprit: web browsers, both Firefox and Chrome. > > To cut a long story short, and for the benefit of the mailing list archive, > if I used Firefox or Chrome (with long-standing config/cache), suspend didn't > work. Blowing away their config & cache makes suspend (and resume!) work. > [Firefox was auto-started by XFCE hence why I'd conflated "login via xenodm" > with "can't suspend". But Chrome also caused the same problem if I ran it > even if Firefox hadn't been started.] > > I don't know what in the old config/cache could have caused this, other than > the config/cache for both browsers was pretty old. Building the config back > up to what I believe I had before has not made the problem come back so far. > Should that change, I'll post a follow-up. > > Thanks Jonathan and Mike for your help and suggestions! > > > Laurie >
Probably audio and/or DRM doing something weird that gets that hardware in an un-zzzable state. Although I think we'd have seen that across a bunch of machines if it was something systemic. Probably just a quirk of your machine. -ml
