4 ms·
And at least OpenSuSE and Slackware just patched the warning out already -- probably after getting hit by it in the past. See for example the patch in Slackwar
by jhkaghjkga 11y ago
And at least OpenSuSE and Slackware just patched the warning out already -- probably after getting hit by it in the past.
See for example the patch in Slackware:
https://slackbuilds.org/mirror/slackware/slackware-current/source/xap/xscreensaver/xscreensaver.no.expiration.date.diff.gz https://slackbuilds.org/mirror/slackware/slackware-current/s...
- cyphax 11y agoOh wow, I didn't expect that from Slackware... I hadn't noticed that the message is gone, I guess. I can't help but to think it is kind of rude to keep using xscreensaver but not honor the request of its author. It's purely the principle of the thing because I agree that the message is ugly. That's not in true Slackware spirit imho (in the sense that this is a less-than-necessary patch). I am a little bit disappointed. :(
- morb 11y agoYes, the nag text was removed, but at least xscreensaver gets updates, which was the whole point. > patches/packages/xscreensaver-5.34-i486-1_slack14.1.txz: Upgraded. I promised jwz that I'd keep this updated in -stable when I removed (against his wishes) the nag screen that complains if a year has passed since that version was released. So, here's the latest one. Personally I don't get the point of screesavers at all, since we have monitors that can be sent sleep/standby mode when they're not used.
- basch 11y agoit is a lock screen that prompts for password on wake https://www.jwz.org/xscreensaver/toolkits.html https://www.jwz.org/xscreensaver/toolkits.html