users.conf doesn't match users.c

Bug #1069218 reported by Mike Major on 2012-10-20
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Light Display Manager
Medium
Unassigned
1.10
Medium
Unassigned
1.2
Medium
Unassigned
1.8
Medium
Unassigned
lightdm (Ubuntu)
Medium
Unassigned
Precise
Medium
Unassigned
Trusty
Medium
Unassigned

Bug Description

[Impact]
The default users.conf provided by LightDM mentions a section [UserAccounts]. It should be [UserList].

[Test Case]
1. Check default installed users.conf
Expected result:
Should have a [UserList] section with all items available but disabled.
Observed result:
Have a [UserAccounts] section with all items available but disabled.

[Regression Potential]
Very low - just changing the default configuration file which has no active configuration items.

Matt Fischer (mfisch) on 2012-11-13
Changed in lightdm:
status: New → Confirmed
Changed in lightdm:
status: Confirmed → Triaged
importance: Undecided → Medium
dino99 (9d9) on 2014-05-19
tags: added: patch trusty utopic
Changed in lightdm:
status: Triaged → Fix Committed
dino99 (9d9) wrote :

Is it fixed yet with 1.11.2 in Utopic ?

Robert Ancell (robert-ancell) wrote :

dino99 - no. When it is fixed the bug will be marked "Fix Released" and the Milestone will be set to the version it is released in.

Changed in lightdm:
milestone: none → 1.11.5
milestone: 1.11.5 → 1.11.3
status: Fix Committed → Fix Released
description: updated

Hello Mike, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Changed in lightdm (Ubuntu):
status: New → Fix Released
importance: Undecided → Medium
Changed in lightdm (Ubuntu Precise):
importance: Undecided → Medium
Changed in lightdm (Ubuntu Utopic):
importance: Undecided → Medium
no longer affects: lightdm (Ubuntu Utopic)
Changed in lightdm (Ubuntu Trusty):
status: New → Fix Committed
status: Fix Committed → Fix Released
importance: Undecided → Medium
Robert Ancell (robert-ancell) wrote :

Confirmed fixed in precise-proposed.

tags: added: verification-done
removed: verification-needed
Changed in lightdm (Ubuntu Precise):
status: New → Fix Committed
Sebastien Bacher (seb128) wrote :

changing to verfication-failed, the update is at least creating a 100% cpu use for quite some users in trusty, see bug #1431654, the tag is to avoid having the SRU validated and copied over to updates before that's resolved

tags: added: verification-failed
removed: verification-done
Brian Murray (brian-murray) wrote :

Hello Mike, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: removed: verification-failed
tags: added: verification-needed
Robert Ancell (robert-ancell) wrote :

Still working with 1.2.3-0ubuntu2.7

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lightdm - 1.2.3-0ubuntu2.7

---------------
lightdm (1.2.3-0ubuntu2.7) precise; urgency=medium

  * debian/patches/15_gsources.patch:
    - Correctly remove GSources on finalize (LP: #1431654)

lightdm (1.2.3-0ubuntu2.6) precise; urgency=medium

  * debian/patches/09_close_pipes.patch:
    - Close pipes correctly (LP: #1190344)
  * debian/patches/10_conf_section_name.patch:
    - Correct section name in default users.conf (LP: #1069218)
  * debian/patches/11_quit_timeout.patch:
    - Destroy quit timeout when a process object is destroyed - fixes a crash
      where a deleted Process object might be accessed after a timeout
      (LP: #1207935)
  * debian/patches/12_layout_no_x11.patch:
    - Handle not getting an X connection when attempting to get X layouts
      (LP: #1235915)
  * debian/patches/13_introspection_makefile.patch:
    - Fix introspection build with newer versions of g-ir-scanner
  * debian/patches/14_compile_warnings.patch:
    - Fix compile warnings
 -- Robert Ancell <email address hidden> Tue, 17 Mar 2015 14:21:43 +1300

Changed in lightdm (Ubuntu Precise):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for lightdm has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers