[systemd-bugs] [Bug 58950] Send signal when about to suspend
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Jan 23 04:57:54 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=58950
--- Comment #4 from Bastien Nocera <bugzilla at hadess.net> ---
(In reply to comment #2)
> Lennart, why don't you send the old UPower signals as well, so that you
> don't break existing applications and they have some time to migrate to the
> new signals?
>
> This transition has broken some important applications, not just IM clients,
> for example NetworkManager. If I suspend through systemd, it fails to
> disconnect from the network and VPN, and after resume it looks like
> connected, but the routing is broken.
>
> I'll report a bug against NetworkManager, but I just don't understand why do
> we change API without giving developers time to adjust. Reopening for your
> consideration.
The UPower API was *always* broken as there wasn't a way to delay the suspend
while you did things, it would send the signal and suspend even if you were in
the middle of saving your data for example.
I'm pretty sure that UPower could be fixed to send the signal, but it would
have the same caveat which makes it unusable right now.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130123/caf8f12a/attachment.html>
More information about the systemd-bugs
mailing list