On Sat, Apr 02, 2005 at 06:58:49PM -0800, Jamie Zawinski wrote:
> If by that you mean: 4.19 was running; you installed 4.21; and you did
> "xscreensaver-command -restart" (or "killall xscreensaver -HUP"),
Funny you should mention that...
xscreensaver (4.21-2) unstable; urgency=low
* driver/subprocs.c: revert unuseful patch.
* hacks/bubbles.h: BUBBLES_IO is unused now.
* debian/copyright: update copyright dates.
* configure.in: don't check for gdmflexiserver's location, so that we don't
have to build-depend on gdm.
* debian/xscreensaver.postinst:
+ send SIGHUP to all running xscreensaver processes.
+ don't call update-menus twice.
* improve maintainer scripts.
* driver/XScreenSaver.ad.in: use url mode by default, pointing to
planet.debian.net's RSS feed.
* driver/xscreensaver-text: fall back to text file mode when an URL isn't
found.
* hacks/webcollage: remove moot patch.
* driver/Makefile.in, hacks/Makefile.in, hacks/glx/Makefile.in: patch from
upstream, to avoid patching all the man files.
* hacks/*.man, hacks/glx/*.man: this makes all these patches unnecessary.
* hacks/vidwhacker: remove unuseful patch.
* debian/rules: install debian/changelog even in dummy packages.
Damn, but you're good. :)
> then maybe what happened is that the new 4.21 executable picked up the
> setgid bit that had been associated with the running 4.19 pid (since you
> were re-execing the 4.21 executable in a process that had previously been
> occupied by the 4.19 executable.)
Well, I could have sworn that I killed all the running xscreensaver
processes the first time the error showed up, but there's no way to show
that one way or the other now.
--
Marc Wilson | "On a normal ascii line, the only safe condition
[EMAIL PROTECTED] | to detect is a 'BREAK' - everything else having
| been assigned functions by Gnu EMACS." (By Tarl
| Neustaedter)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
