Comment 3 for bug 1028552

[+3.74s] DEBUG: Greeter start authentication for guest account
[+3.74s] DEBUG: Greeter requests session kde-plasma
[+3.74s] DEBUG: Using session kde-plasma
[+3.74s] DEBUG: Stopping greeter
[+3.74s] DEBUG: Session 8928: Sending SIGTERM
[+3.75s] DEBUG: Session 8928 exited with return value 0
[+3.75s] DEBUG: Greeter quit
[+3.75s] DEBUG: Opening guest account with command '/usr/sbin/guest-account add'
[+3.94s] DEBUG: Guest account setup script returns 32512: Adding system user `guest-mrIqvz' (UID 116) ...
Adding new group `guest-mrIqvz' (GID 126) ...
Adding new user `guest-mrIqvz' (UID 116) with group `guest-mrIqvz' ...
Not creating home directory `/'.

[+3.94s] DEBUG: Can't autologin guest, no guest account

When we run the guest account creation script on it's own (/usr/sbin/guest-account add):
Adding system user `guest-xNlkcz' (UID 117) ...
Adding new group `guest-xNlkcz' (GID 127) ...
Adding new user `guest-xNlkcz' (UID 117) with group `guest-xNlkcz' ...
Not creating home directory `/'.
bash: line 1: gconftool-2: command not found

 1) This a packaging bug in lightdm, it should depend on gconftool-2 if it uses it.
 2) wrong anyway. The lightDM guest-account-add script should not be doing Gnome specific things.
 3) we need a way to add the same, but KDE specific stuff, namely:
     Disable nepomuk (initial table creation takes a long time, and all data is discarded anyway, Vishesh agreed on this)
     Disable the screen lock (as if it does lock, the user is locked out completely)
     Disable jockey, software update et-al that need root access.

I'm pretty sure they'll be (equally) upset if we just add KDE code into this script, so we need to talk to upstream about a good universal way to do this, maybe loading a specific script based on the session name.