Guest accounts may not be removed properly on system reboot

Bug #1506489 reported by Laércio de Sousa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Light Display Manager
Triaged
Medium
Unassigned

Bug Description

I've noticed that guest accounts may not be cleanly removed from my system if I stop lightdm directly (e.g. on reboot without logging out first). This may lead to a situation where guest login fails due to lack of available GIDs (which shorten more quickly than UIDs).

A possible workaround for this problem is the addition of a pre-start (or post-stop) stanza to flush all remaining guest accounts. At least for systemd, the ExecStartPre option is preferable, because ExecStopPost may not be run if system is rebooted/halted with "systemctl --force".

This problem may affect Precise/Trusty, too.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Related to bug 1259562?

Changed in lightdm:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Laércio de Sousa (lbssousa) wrote :

Not sure. I'm running these tests in Debian, which doesn't install AccountsService by default. There are no leftovers in my filesystem, but there may be letfover entries in /etc/passwd and /etc/group if not logging out guest before stopping lightdm service.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.