Comment 21 for bug 636693

@Ted
No, no, it seems like I have failed to explain the reasons for my suggestion.

I want to give users options; I want to make it easy to customize the guest sessions. What makes guest sessions different compared to other kinds of sessions is that you can't make use of the normal tools within a session for customizing the behavior. It has to be done before launch, since no changes within a guest session are saved til next time you start a guest session.

I already mentioned the tutorial I wrote. For the time being that tutorial serves as a response to various user requests for customization options; please see bug 667089. Some settings are better done on-the-fly when launching a guest session, and that kind of customization (the example in the tutorial is the session language) must be done before the screen is locked.

I'm not against adding additional menu items when feasible; that's what people currently are advised to do in the tutorial. But that requirement makes customization more difficult, and with the suggested code change in the new merge proposal, using the default "Guest Session" menu item would work just fine.

During our IRC talk you mentioned interesting examples of how gdm-guest-session may be used, that I hadn't thought of before. To make it easier to launch guest sessions for such purposes, I made your suggestion for a --no-lock option be implemented. Now I ask you to please make on-the-fly customization easier by approving the new merge proposal.

Gunnar