Bug 1331976

Summary:	gdm : access denied
Product:	[Fedora] Fedora	Reporter:	Roman <roman.morokutti>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	normand, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gnome-shell 3.21.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-02 16:35:49 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 Roman 2016-04-30 19:49:47 UTC

Description of problem:

gdm crashes because of too many attempts to start.
The problem is according to the journalctl messages
as follows:

# journalctl -r
(excerpt)
systemd-logind[884]: Failed to stop user slice : Access Denied

/usr/libexec/gdm-wayland-session[9358]: Unable to register display with display manager

gdm-launch-environment[9338]: pam_systemd(gdm-launch-environment:session): Failed to create session: Access denied
systemd-logind[884]: Failed to start session scope session-c504.scope: Access Denied

systemd-logind[884]: Failed to start user slice user-42.slice, ignoring: Access denied (org.freedesktop.DBus.Error.AccessDenied)

gdm[997]: Unable to kill session worker process
gdm[997]: Child process 9320 was already dead.
gdm[997]: Child process -9326 was already dead.

These messages are repeating (with increasing session numbers) certain times and than no Login Screen appears. Instead the screen is frozen. This happens right after Plymouth shows the 'f' when fully loaded.

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

gdm: 3.20.1
pymouth: 0.8.9
systemd: 229
kernel: 4.6.0.0.rc5.git2.1.fc25.x86_64


Actual results:
No GNOME.


Expected results:
GNOME login

Additional info:

Comment 1 Roman 2016-05-02 16:35:49 UTC

Problem solved with newest version.