Bug 2005682

Summary: FreeIPA-based users not showing up in GDM list
Product: [Fedora] Fedora Reporter: James <james>
Component: accountsserviceAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: ctimko, gnome-sig, liebundartig, mclasen, stanislav.polasek, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 15:35:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James 2021-09-19 14:09:18 UTC
Description of problem:
Users with FreeIPA-based accounts do not show up in the GDM list after logging in.

Version-Release number of selected component (if applicable):
gdm-41~rc-1.fc35.x86_64
accountsservice-0.6.55-8.fc35.x86_64
sssd-2.5.2-5.fc35.x86_64
freeipa-client-4.9.7-1.fc35.x86_64

How reproducible:
Very consistently, although it has worked on a few occasions. Can't recall the conditions surrounding this.

Steps to Reproduce:
1. Log in as a FreeIPA-based user via 'Not listed' in GDM.
2. Log back out again.

Actual results:
The user just logged out does not appear in the list. Only machine-local UNIX accounts present.

Expected results:
FreeIPA users seen by GDM remain in the list.

Additional info:
$ dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers
method return time=1632060491.545046 sender=:1.18 -> destination=:1.244 serial=117 reply_serial=2
   array [
      object path "/org/freedesktop/Accounts/User1001"
   ]

-- i.e. just the local account.

Comment 1 Charles Timko 2021-10-29 17:17:13 UTC
I'm able to reproduce this as well (on F35). Additionally, since this doesn't register the account, deleting temporary local users results in gnome-initial-setup being triggered following a reboot.

Comment 3 James 2022-02-20 16:29:58 UTC
Still present with sssd-2.6.3-1.fc35.x86_64, gdm-41.3-1.fc35.x86_64 (same accountsservice).

Might provide a better user experience if the users list were turned off as part of IPA client config or authselect? Certainly less clumsy than having to click the 'not listed' option each time to log in.

Comment 4 James 2022-03-13 14:21:51 UTC
Regression present in F36, tested on gdm-41.3-3.fc36.aarch64, sssd-2.6.3-1.fc36.aarch64, accountsservice-0.6.55-9.fc36.aarch64.

Comment 5 René Genz 2022-03-14 17:49:14 UTC
I am coming from bug 2021839. Does the workaround "select any session type manually and login" create the icon permanently for you too?

Comment 6 James 2022-03-14 20:49:50 UTC
(In reply to René Genz from comment #5)
> I am coming from bug 2021839. Does the workaround "select any session type
> manually and login" create the icon permanently for you too?

Seems to so far.

Comment 7 Charles Timko 2022-10-25 15:10:56 UTC
My workaround that has been pretty faithful is to have a local throw-away account and to lock it. That gives me a login without sending me back through the whole account setup process. It's not ideal, but it works reliably.

Comment 8 Ben Cotton 2022-11-29 17:04:49 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 9 Ben Cotton 2022-12-13 15:35:38 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 10 Red Hat Bugzilla 2023-09-18 04:26:15 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days