← Back to team overview

touch-packages team mailing list archive

[Bug 1302491] Re: when autlogin with a timeout is used, it should be reapplied when the user logs out.

 

** Description changed:

- IF lightdm is configure for autologin with a timeout, it only autologins
- the user when the system starts.  If the (auto logged in) users logs
- out, the timeout is then not re-applied.
+ [Impact]
+ If LightDM is set up for timed login this only occurs on first login, i..e after a session logout timed login is not reattempted. This doesn't match the traditional behaviour of GDM. A common use case for timed login is kiosk setups where the greeter should never be displayed for any significant amount of time; this is currently impossible to set up with LightDM.
  
- I would expect the system to autologin in this case as well, just when
- the timeout expired.
+ [Test Case]
+ 1. Setup LightDM to do a timed login
+ 2. Wait for timeout
+ (session starts)
+ 3. Log out of session
+ Expected result:
+ The session is started again after the timeout.
+ Observed result:
+ The greeter is show forever.
  
- GDM's autologin with timeout feature behaves this way, fwiw.  i.e. if
- you log out, the timeout is re-applied.
- 
- Whether this can be considered a bug or feature, is debatable, I filed
- it as bug for now (because for our application it is a bug).
- 
- background:  We use the autologin with timeout feature to start a POS
- application automatically.  When the POS application terminates, lightdm
- regains control.  And now the user is stuck, unless he knows the login
- credentials.
+ [Regression potential]
+ There is some risk that someone might have been relying on the existing behaviour. The assumption is that most timed login users would prefer the new behaviour. There is a small risk that these changes may have broken something else, this has been reduced by using the regression tests.

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: lightdm (Ubuntu Utopic)
   Importance: Undecided
       Status: New

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: lightdm (Ubuntu Utopic)
       Status: New => Fix Released

** Changed in: lightdm (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Trusty)
       Status: New => In Progress

** Changed in: lightdm (Ubuntu Utopic)
   Importance: Undecided => Medium

** Changed in: lightdm
     Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm/1.10
     Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm (Ubuntu Trusty)
     Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm (Ubuntu Utopic)
     Assignee: (unassigned) => Robert Ancell (robert-ancell)

-- 
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/1302491

Title:
  when autlogin with a timeout is used, it should be reapplied when the
  user logs out.

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  In Progress
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  If LightDM is set up for timed login this only occurs on first login, i..e after a session logout timed login is not reattempted. This doesn't match the traditional behaviour of GDM. A common use case for timed login is kiosk setups where the greeter should never be displayed for any significant amount of time; this is currently impossible to set up with LightDM.

  [Test Case]
  1. Setup LightDM to do a timed login
  2. Wait for timeout
  (session starts)
  3. Log out of session
  Expected result:
  The session is started again after the timeout.
  Observed result:
  The greeter is show forever.

  [Regression potential]
  There is some risk that someone might have been relying on the existing behaviour. The assumption is that most timed login users would prefer the new behaviour. There is a small risk that these changes may have broken something else, this has been reduced by using the regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1302491/+subscriptions