ChanceNCounter
commented
1 week ago Update: this may not be a UI error after all. A hunch after some visual weirdness on wake caused me to attach to the lapce process, and it turns out it's calling sched_yield() in an infinite loop, very rapidly. I suspect that's the cause, and this issue should probably be moved to the main lapce repo. Sorry about that.
Will close and reopen there if this isn't moved in the next few days.
LightDM/X11/AwesomeWM (eos, current)
This has only happened once so far, but I'm not sure what logs to monitor, what flags to pass going forward, etc, and I'd like to prep for the next time right away so we can debug it.
I suspended the machine. I woke it. I switched to the tag containing a lapce instance. I had a window border, but it was empty, could not be clicked, and did not respond to my attempts at blindly raising the command palette. The window border also was not responsive, which briefly led me to wonder if it was Awesome's fault, but I've never seen this with any other programs.
I killed the program via terminal. This is obviously undesirable for a text editor.
I imagine I'll "try" to repro the next time I suspend this machine. What should I do to prepare?