Bug 1379390

Summary:	login loop fedora 23 and 24
Product:	[Fedora] Fedora	Reporter:	xtify21 <tuxfed21>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	23	CC:	rstrode
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-20 21:36:17 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:

Description xtify21 2016-09-26 14:43:29 UTC

Description of problem: 

After installing fedora 24 which was great, I got bit with the gdm login loop. When I enter my username and password, It attempt to log me in but I then get sent right back to the login screen. However, this only happens with username and pass, I can login with root and password just fine. 

I am not sure what update is causing this to happen but seems as though when I update the system some package thats gets updated is causing this to happen in both fedora 23 and fedora 24


Version-Release number of selected component (if applicable):

fedora 23 and fedora 24

How reproducible:
dnf update ; dnf upgrade. Again, not sure what package is causing this but I have experienced the bug in both versions.

I thought it was a kernel bug but I even re-compiled it again to the latest stable release (4.7.5) and upon rebooting the bug still occurred.


Steps to Reproduce:
1. update ; upgrade system
2. attempt to login with user name and password - fails
3. login in as root - success

Actual results:


Expected results:


Additional info: I was able to work around the issue by deleting the user and then adding the user back. When I did this I was able to login via gdm with the new user and password with success. 

I just dont want to have to continue deleting and removing user account to work around this bug which has become tiresome, especially since I have experienced the issue now with both fedora 23 and 24

Please continue to look into these odd gdm login issues

Thanks

Comment 1 Fedora End Of Life 2016-11-25 09:36:12 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 2 Fedora End Of Life 2016-12-20 21:36:17 UTC

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.