Bug 1755078

Summary:	Second seat session in GNOME 3.34 is locked after few seconds.
Product:	[Fedora] Fedora	Reporter:	Baptiste Mille-Mathias <baptiste.millemathias>
Component:	gnome-session	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	31	CC:	bberg, caillon+fedoraproject, gnome-sig, john.j5live, mclasen, rhughes, rstrode, sandmann
Target Milestone:	---	Keywords:	Desktop, Regression
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-24 17:45:07 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 Baptiste Mille-Mathias 2019-09-24 17:32:10 UTC

Description of problem:
the second person login on a computer is locked-on after few seconds.

Version-Release number of selected component (if applicable):
gnome-session-3.34.0-2.fc31.x86_64
gnome-session-wayland-session-3.34.0-2.fc31.x86_64
gnome-session-xsession-3.34.0-2.fc31.x86_64
gnome-settings-daemon-3.34.0-1.fc31.x86_64
gnome-shell-3.34.0-2.fc31.x86_64

How reproducible:
100%

Steps to Reproduce:
1. one person logs into his session, then lock the screen.
2. another person logs into his session

Actual results:
The lock screen, with the current time slides dozn within 10 seconds each time the second person logs on.
Even once the first person logs off, the second session works, but a screen corruption occurs, however locking the screen (key meta + l) and login again fix the corruption

Expected results:
multi-user to work as before.

Additional info:
Fedora with all packages up-to-date as of yesterday

Comment 1 Benjamin Berg 2019-09-24 17:45:07 UTC


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

Comment 2 Benjamin Berg 2019-09-24 17:46:36 UTC


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