Peter Eriksson wrote:
> Perhaps xscreensaver could grab the .Xauthority file from $HOME when it
> starts and then use that copy when starting up things instead of relying on
> having a readable $HOME...
Unfortunately, xscreensaver is caught between the requirements of
PAM & GTK here. It has to be setuid-root to run the PAM stack, so
that PAM can read things such as /etc/shadow if it needs to, but GTK
refuses to run in setuid applications, so the unlock GUI is a
seperate program that is forked off as the user when it's time to
unlock, and that's what's failing to read your .Xauthority.
There is a major rearchitecture of the GNOME screen lock planned for
the future - moving to gnome-screensaver and possibly using gdm to
provide the authentication dialogs - but that's probably a year or
more from being ready to ship.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
