On Sat, Jun 25, 2011 at 02:12:05PM +0200, Yann Dirson wrote:
> I note that the 5.13-1 changelog says "Remove obsolete gdmflexiserver
> options".  Without more details it is hard to say if this had an
> influence, but it has at least the potential to.  Could it be that
> previously the --starnew option was passed, but that it is not passed
> any more ?

Looking further, /etc/X11/app-defaults/XScreenSaver says:

! This command is executed by the "New Login" button on the lock dialog.
! (That button does not appear on the dialog if this program does not exist.)
! For Gnome: probably "gdmflexiserver -ls".  KDE, probably "kdmctl reserve".
!
! ! *newLoginCommand:   gdmflexiserver -ls
! Debian: Hard-wire the command in case the build machine does not have gdm
*newLoginCommand:       gdmflexiserver -l


So it looks like the -s flag was indeed here at some point, but was
removed to improve things for machines without gdm ?  Unfortunately, I
can't find any details in the changelog, not in the bts, about what
can be improved that way.

Perhaps what's missing is a way to check whether the newLoginCommand
can in fact be executed, and gray out the "new login" button if not.
Looks like this would address #304406 and #499909 at the same time.


Another strange issue: although /etc/X11/app-defaults/XScreenSaver is
there and adding -s in there does allow "new login" to work again
correctly, it is not provided by any package, whereas there is a
/etc/X11/app-defaults/XScreenSaver-nogl which is provided by
xscreensaver-data, and *does* contain the -s flag.  Unfortunately,
moving app-defaults/XScreenSaver out of the way leaves the
"gdmflexiserver -l" built into the binary be used as default, the
-nogl version is not used.  Looking at the xscreensaver postinst, it
appears that file should be handled as a symlink, but here it is a
plain file.

Here I suspect that there would have been a transition from plain to
symlink at some point, but can't find a hint about that in the
changelog either (looking for "app-default" or "symlink").  Any idea
why I got this plain file ?

Best regards,
-- 
Yann



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to