Sorry, please ignore my previous comment. It does work with some commands, I'm experiencing the failure mentioned above when trying to run "cupsdisable" and "cupsreject" upon login, but when I try other privileged commands they work.
I'll see if I can narrow down exactly what is failing and where, but my post above is incorrect, prefs.sh is being sourced as a privileged user (I can't seem to edit or delete the post hence this addition). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1581853 Title: Source prefs.sh as privileged user to allow user mods Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Xenial: Fix Released Bug description: [Impact] including [Test Case] The Ask Ubuntu question <http://askubuntu.com/q/771080> called my attention to a regression in 16.04 as regards the possibilities for the system owner to configure the guest account. Up to 15.10 you can put e.g. this line in /etc/guest-session/prefs.sh: adduser $USER somegroup But if you try that in 16.04, the guest session won't launch. The explanation is that after the reorganization of the guest session code in 16.04, prefs.sh is sourced by /usr/share/lightdm/guest- session/setup.sh, which is not run as root. The linked merge proposals restore the previous behavior by letting prefs.sh be sourced by /usr/sbin/guest-account again. [Regression Potential] Low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp