Bug 1376590

Summary:	Can't login after logout
Product:	[Fedora] Fedora	Reporter:	Giulio 'juliuxpigface' <juliux.pigface>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	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-09-15 20:48:19 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 Giulio 'juliuxpigface' 2016-09-15 20:40:34 UTC

Description of problem:
I'm testing the login capabilities on Fedora 25 Workstation (20160912 compose).
I think I found a case where login through gdm fails.

Version-Release number of selected component (if applicable):
gdm-3.21.91-2.fc25.x86_64

How reproducible:
Always

Steps to Reproduce (1):
1. Prepare a system with two user accounts
2. Log in with the first user account
3. Log out
4. Try to log in again with the first account (the same account as step 2)

Steps to Reproduce (2):
1. Prepare a system with two user accounts
2. Log in with the first user account
3. Log out
4. Log in with the second user account
5. Log out
6. Try to log in again with the first account (the same account as step 2)

Actual results:
1. Can't login until reboot

Expected results:
1. Users should be able to log in

Additional info:
1. This might be Wayland related, since logging in to a "Gnome+Xorg" session seems to work successfully.
2. I'm testing on qemu-kvm, so it might also be something specific to the "relationship" between QXL and Wayland.

Comment 1 Giulio 'juliuxpigface' 2016-09-15 20:48:19 UTC

Please disregard this.
I've just found that a bug has already been filled for the same issue.

*** This bug has been marked as a duplicate of bug 1373169 ***