Description of problem: The gdm login screen does not display an icon for my account. I can, however, log in successfully by clicking 'not listed' and then enter my user name and password. Only my own account is affected by this, all other users' icons are displayed as expected. What's weird is that, if I switch to a text console on a different VT and log in there, then switch back to gdm, an icon for my account is now displayed and I can use it to log in. The same is true if I log off from the console session before returning to the gdm login screen. However, after logging off from the gdm session, the login screen comes up again with my icon missing. Version-Release number of selected component (if applicable): gdm-40.1-1.fc34 How reproducible: always Steps to Reproduce: see description above Actual results: no login icon displayed Expected results: login icon should always be displayed on login screen Additional info: All users are in a ldap data base, which is accessed through sssd.
Also present in F35.
I have the same problem with Microsoft Active Directory (ADDS; if you deem it to be an LDAP identity provider) and reported it upstream: https://gitlab.gnome.org/GNOME/gdm/-/issues/743 I can reproduce it with Fedora 36 too, hence set prioritized bug flag. Bug 2005682 seems to be the same issue, but different identity provider (FreeIPA). Does the workaround "select any session type manually and login" creates the icon permanently for you too?
(In reply to René Genz from comment #2) > Does the workaround "select any session type manually and login" creates the > icon permanently for you too? Yes, it does. Curious.
> Does the workaround "select any session type manually and login" creates the > icon permanently for you too? Yes, works for me, too.
I think this really needs some design work and careful thinking. Obviously it can't just show all the users who might be configured in an identity provider (both because it could be thousands of accounts, and because getting a list might not even be possible without authenticating first). And saving users who have logged in makes sense in many settings — but not in others like a lab environment. I suggest taking this and the related use cases to the Fedora Workstation working group for discussion.
In today's Prioritized Bugs meeting, we agreed to reject this as a prioritized bug. Although we recognize it's undesirable behavior in some circumstances, it's best left to upstream to decide if it's the behavior they want or if it should be modified in some way. (see also comment 5) https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-06/fedora_prioritized_bugs_and_issues.2022-04-06-14.01.log.html#l-159
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.
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.