fix time after suspend-to-*
Quoted 12 lines
Quoted 5 lines
Userspace behavior on suspend transitions is still a bit fuzzy at best. I am beginning to look at userspace requirements, so if anyone wants to send me suggestions, no matter how trivial or wacky, please feel free (on- or off-list).
Many userspace applications are not prepared for suspension, like Evolution. When suspending the machine for a long time, all IMAP sessions are broken as their counterpart TCP sockets timeout. While resuming, Evolution is unable to handle this condition and simply informs the network connection has been dropped.
Quoted 4 lines
What about sending the SIGPWR signal to all userspace processes before suspending so applications like Evolution can be improved to handle this signal, drop their IMAP connections and then, when resuming, reestablish them?
I think that messagebus is for such stuff. ?!
Greetings
Mathias
Signature · 1 line
Mathias Fröhlich, email: [email protected]