Bug 1379418

Summary: First login after boot takes over 25 seconds
Product: [Fedora] Fedora Reporter: Volker Sobek <reklov>
Component: selinux-policy-targetedAssignee: Owen Taylor <otaylor>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: dwalsh, fmuellner, otaylor, sangu.fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-07 17:45:30 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:
Attachments:
Description Flags
Output of journalctl -b none

Description Volker Sobek 2016-09-26 16:39:59 UTC
Created attachment 1204886 [details]
Output of journalctl -b

Description of problem:

The first time I try to log in from gdm after booting it takes over 25 seconds until I get to the desktop. Subsequent logins (after logging out or switching user) do not have this issue. The only suspicious thing I can see in the logs is this:

Sep 26 17:57:10 hp org.gnome.Shell.desktop[1622]: Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)


Version-Release number of selected component (if applicable):
gnome-shell-3.22.0-1.fc25.x86_64
gnome-session-3.22.0-1.fc25.x86_64
storaged-2.6.2-2.fc25.x86_64


How reproducible:
Always


Steps to Reproduce:
1. Reboot fedora 25
2. Choose user and log in from gdm

Actual results:
It takes about 25 seconds until you get to the desktop

Expected results:
The desktop should show up immediately

Additional info:
This system is a fresh fedora 24 install from a couple of days ago, which I brought up-to-date before doing a dnf system-upgrade to upgrade it to fedora 25.

Comment 1 Volker Sobek 2016-10-07 17:45:30 UTC
Upgrading selinux-policy{,-targeted} from 3.13.1-214.fc25 3.13.1-218.fc25 fixed the issue today.