[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2017-01-26 Thread Jude Hungerford
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,

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2017-01-26 Thread Jude Hungerford
>From my reading of the above, it seems that this bug should be fixed in Yakkety, and probably also in up-to-date installations of Xenial. I believe this is the bug I'm currently seeing (prefs.sh not sourced as privileged user) in both Yakkety and Xenial (lightdm versions 1.19.5-0ubuntu1 and 1.18.

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-07-12 Thread Launchpad Bug Tracker
This bug was fixed in the package lightdm - 1.18.2-0ubuntu1 --- lightdm (1.18.2-0ubuntu1) xenial; urgency=medium * New upstream release: - Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157) - Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor soc

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-06-23 Thread Gunnar Hjalmarsson
Installed lightdm 1.18.2-0ubuntu1 from xenial-proposed and confirm that the guest user can be modified via /etc/guest-session/prefs.sh using e.g. the adduser command. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a mem

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-06-23 Thread Brian Murray
Hello Gunnar, or anyone else affected, Accepted lightdm into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.18.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-06-20 Thread Robert Ancell
** Changed in: lightdm (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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 privile

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-06-20 Thread Launchpad Bug Tracker
This bug was fixed in the package lightdm - 1.19.1-0ubuntu1 --- lightdm (1.19.1-0ubuntu1) yakkety; urgency=medium * New upstream release: * debian/lightdm.dirs: - Rename "xlocal" seat type to "local". Using "xlocal" will continue to work but report a warning. - Ensur

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-05-17 Thread Gunnar Hjalmarsson
** Description changed: + [Impact] including [Test Case] + The Ask Ubuntu question 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/

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-05-16 Thread Robert Ancell
** Also affects: lightdm (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Xenial) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: lightdm (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Xenial

[Touch-packages] [Bug 1581853] Re: Source prefs.sh as privileged user to allow user mods

2016-05-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~gunnarhj/lightdm/prefs.sh-fix_xenial ** Branch linked: lp:~gunnarhj/lightdm/prefs.sh-fix_yakkety -- 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