On Sat, Jun 25, 2011 at 5:14 PM, Yann Dirson wrote:
> 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.

The -s option was removed from the command line because the option is
ignored by gdmflexiserver. At least, that is what "gdmflexiserver -?"
says.

> 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.

Yes, this would be nice. I think a run-time check is the only proper
way to determine if the button should be displayed or not.

> 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

Are you really sure that the -s has any effect? In that case the "-?"
output must be wrong.

> /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.

I believe XScreenSaver should be a symlink, pointing to
XScreenSaver-gl as long as xscreensaver-gl has been installed. The
link is created/deleted in the xscreensaver-gl postinst/postrm.

> 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 ?

The postinst/postrm files have not been touched since at least the
5.05-2 release (that's how far back the git history goes). Maybe there
was a bug in some really old version and you have kept the plain file
ever since?

Thanks for investigating these issues!
Tormod



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

Reply via email to