Comment 15 for bug 636693

Hi Gunnar,

I'm going to mark this fixed, and I realize that it's not the way that you thought it was going to be fixed, but I want to explain why this way is better. I think it specifically takes your use-case into account and in fact enriches the very interesting work that you're doing.

I'm now launching the guest-session with the --no-lock parameter in indicator-session. So this means that this bug is closed because only indicator-session is locking the screen. That's better because indicator-session takes a more global view of when the screen should be locked and looks at other desktop settings. We want to keep that.

I realize you're thinking that this restricts you from doing custom guest sessions. And that's partially true in that you can't use the "Guest Session" entry for that. But, what we've added is much richer. Also in this release is the ability to add to the session menu arbitrary desktop files. What this means is that you can add multiple enriched sessions like the ones that you've documented how to do on the forums. And you can do you it in packages and very maintainable ways. I think this is exciting, and I can't wait to see what you do with it.

What you need to do is put a file in /usr/share/indicators/session/applications/ that is a .desktop file. That file will be put in the menu with the menu entry being the "Name" key. When that entry is clicked on the "Exec" line will be run. This can be any script. Indicator session will not take care of locking when these commands are run. There can be any number that you'd like.

Thanks for your passionate appeal for this change, I hope this gives you the tools to do some really cool things with Ubuntu.

Ted