<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Send signal when about to suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=58950#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Send signal when about to suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=58950">bug 58950</a>
from <span class="vcard"><a class="email" href="mailto:bugzilla@hadess.net" title="Bastien Nocera <bugzilla@hadess.net>"> <span class="fn">Bastien Nocera</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=58950#c2">comment #2</a>)
<span class="quote">> 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.</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>