Description of problem: I have two usernames with the same UID (deliberately). One of them should be listed in the GDM login screen, and the other should not. The one that should *not* be listed (call it 'hidden') has SystemAccount=true in /var/lib/AccountsService/users/hidden The one that *should* be listed has the same key set to 'false' in the corresponding file (call it user 'seeme'). The UID in question is greater than 15000. Running '/usr/libexec/accounts-daemon --debug' shows that 'hidden' is encountered first and loaded, and then 'seeme' is found subsequently and loaded. And then: ** (accounts-daemon:15985): CRITICAL **: error exporting user object: An object is already exported for the interface org.freedesktop.Accounts.User at /org/freedesktop/Accounts/User15819 (accounts-daemon:15985): DEBUG: failed to load gdms custom.conf: Key file does not have key 'AutomaticLoginEnable' (accounts-daemon:15985): DEBUG: got NameLost, exiting (accounts-daemon:15985): DEBUG: exiting Version-Release number of selected component (if applicable): accountsservice-0.6.35-4.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create two users with the same UID (greater than 1001); 2. Make sure the (sorted) first user has 'SystemAccount=true' in its /var/lib/AccountsService/users/ file; 3. Make sure the (sorted) second user has 'SystemAccount=true' 4. Bring up the login screen. Actual results: Neither user is listed in the welcome screen. Expected results: The 'SystemAccount=false' user should be included in the username login pulldown. Users with 'SystemAccount=true' should be dropped from consideration/not exported before the user list is constructed. Additional info:
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This appears to still be a problem in F21. Updating the version in the BZ..
This bug was reported nine months ago. Is there any update on when it might be scheduled for investigation, at least? Should I try to generate a patch to submit?
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This appears to have been fixed in F22. Closing.
This bug is back in F23.