On Fri, Jun 20, 2025 at 07:03:32PM +1000, Jonathan Gray wrote: Hello Jonathan,
>> As of some time early this week, I noticed that my xidle screensaver >> command is not running. [It may have happened before that, but if so I >> didn't notice.] > I don't normally use xidle, but it works here with: > > xidle -no -program /usr/X11R6/bin/xclock -timeout 5 > > with both cwm and fvwm This observation sent me down an interesting, long rabbit hole of enabling / disabling software! Long story short: Firefox with my old configuration was the culprit. I don't know how. If it's running, xidle doesn't get X events, and xlock can't shut the monitor down. If it's not running, everything works as expected. All I have to do is `kill`/run it -- it's totally deterministic. Running Firefox with a fresh config cures the problem; perhaps as I build it back up, I might find what setting is the cause, but that might not happen. I haven't changed anything in the configuration in months, to the best of my knowledge, so I'm not sure why it might suddenly have caused problems now. I'm hopeful that this might also solve the suspend issue, but it will take several more successful cycles before I'm confident about that. Thank you for your patience on this, particularly as I incorrectly, and foolishly, assumed it was amdgpu related! Laurie
