(Oh, I had not noticed that NMU)
That way of fixing the problem seems a bit crude. After all, it may
be legitimate to get the running screensavers to upgrade when the
binary gets updated - but is that what SIGHUP does, I can find nothing
in the manpage or in the README.
It could be that a correct fix would be to save the current state of
the screensaver before handling the signal, and getting back to that
state afterwards - however that may be more difficult to do safely,
without any time-window kept unlocked.
I'll let you decide, whether to forward this upstream or not.
Best regards,
--
Yann Dirson <[EMAIL PROTECTED]> |
Debian-related: <[EMAIL PROTECTED]> | Support Debian GNU/Linux:
| Freedom, Power, Stability, Gratis
http://ydirson.free.fr/ | Check <http://www.debian.org/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
