- HEADLINE: More stable dock/undock and sleep/wake handling.
- DESCRIPTION:
I've noticed that my system often hangs unrecoverably with a blank screen during dock/undock and sleep/wake events. I've learned, though, that I can reduce the likelihood of having problems by trying to minimize the number of state changes that the system has to handle at once. For example, if I'm leaving the house with the laptop, I'll first open the lid, wait 10 seconds to see if the display wants to turn on or not, undock it, wait 10 seconds for it to adjust, and only then put it to sleep. Same thing waking it up: one step at a time, with 10 second pauses in between. Seems to reduce my problems by about 90%. As a developer, this screams "race conditions" to me, but what do I know? If there's a bug filed for this already, I wouldn't know -- no idea what I'd search for.
I take the uptime game pretty seriously: having to reboot means that I lose a ton of context. Right now, I've got nine separate workspaces/desktops going, all with several browser, terminal, etc. windows. A reboot means I'll spend anywhere from 10 to 20 minutes installing updates and recovering all of that state. It's painful. Right now, my system has only been up for 9 days, which is weak sauce.
- ROLE/AFFILIATION: software developer in the federal government