Bug 1860438 - Login to Gnome fails for FreeIPA managed users when AD User Short Names is used
Summary: Login to Gnome fails for FreeIPA managed users when AD User Short Names is used
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 32
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-24 14:49 UTC by Thomas Höll
Modified: 2021-05-25 17:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:45:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thomas Höll 2020-07-24 14:49:30 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36
Build Identifier: 

When I try to log in to Gnome using my AD user, I'm authenticated but shortly after my Gnome session crashes and I'm returned to the login screen. This only happens when I just enter the sAMAccountName, the full UPN works fine. However, a console login works fine with either the sAMAccountName or the full UPN.


Reproducible: Always

Steps to Reproduce:
1. Setup a fresh F32 Workstation installation, install updates and freeipa-client
2. Join a FreeIPA domain (ipa-client-install --mkhomedir --enable-dns-updates)
A trust between the IPA domain and an AD domain is set up
3. Set the domain resolution order to AD domain BEFORE IPA domain
4. Log on the Gnome on the F32 Workstation machine
Actual Results:  
User is logged in, home directory is created, Gnome session crashes

Expected Results:  
Gnome session should start properly

This problem started after the upgrade to Fedora 32, a fresh F31 installation works perfectly fine. Rawhide doesn't work either.
Console sessions work perfectly fine from F31 to Rawhide.

I don't know whether is affects just the AD users or the IPA managed users as well. Local users work fine.

Comment 1 Thomas Höll 2020-10-16 13:39:40 UTC
Seems to be fixed in Fedora 33.

Comment 2 Fedora Program Management 2021-04-29 17:05:01 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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.

Comment 3 Ben Cotton 2021-05-25 17:45:55 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


Note You need to log in before you can comment on or make changes to this bug.