automatic login configured in ubiquity cannot be disabled by gnome-control-center
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
Fix Released
|
Undecided
|
Unassigned | ||
ubiquity (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
user-setup (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Release: vivid (fresh install with ubuntu-
Version:
ubiquity 2.21.4
gnome-
gdm 3.14.1-0ubuntu1
What I expected:
+ Fresh install with ubiquity, create a user with auto-login enabled
+ User logs in automatically on subsequent boots
+ Disable auto-login via System -> Users -> Unlock -> Automatic login (OFF)
+ Restart and see gdm login dialog
What happened:
+ After disabling auto-login, the user is nonetheless automatically logged if gdm is left alone for 10 seconds
If auto-login is selected in ubiquity, it appears to write the following into /etc/gdm/
AutomaticLo
AutomaticLo
TimedLoginE
TimedLogin=
TimedLoginD
While toggling auto-login in gnome-control-
Related branches
- Mathieu Trudel-Lapierre: Approve
-
Diff: 36 lines (+9/-5)2 files modifieddebian/changelog (+7/-0)
user-setup-apply (+2/-5)
information type: | Private Security → Public Security |
Changed in ubuntu-gnome: | |
milestone: | none → vivid |
affects: | gnome-control-center (Ubuntu) → user-setup (Ubuntu) |
Changed in ubuntu-gnome: | |
status: | New → Fix Released |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.