Bug 834430

Summary: LightDM takes very long to start and login
Product: [Fedora] Fedora Reporter: Heiko Adams <bugzilla>
Component: lightdmAssignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: christoph.wickert, gregor, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-22 16:47:23 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:
Bug Depends On: 834427    
Bug Blocks:    
Attachments:
Description Flags
lightdm.log
none
log from gtk-greeter none

Description Heiko Adams 2012-06-21 20:44:21 UTC
Created attachment 593593 [details]
lightdm.log

Description of problem:
LightDM currently takes at least extremely long to start. After plymouth finished the screen stays black for several seconds until lightdm greeter is visible, Loging into my desktop takes also several seconds from pressing "login" button until the desktop environment is starting.

Version-Release number of selected component (if applicable):
lightdm-gobject-1.2.2-15.fc17.x86_64
lightdm-1.2.2-15.fc17.x86_64
lightdm-gtk-1.1.6-3.fc17.x86_64

How reproducible:
allways

Steps to Reproduce:
1. install lightdm
2. reboot
3.
  
Actual results:
After plymouth has finished the screen stays black for several seconds.

Expected results:
LightDM should be available imidiately after plymouth finishes, like LXDM does.

Additional info:

Comment 1 Heiko Adams 2012-06-21 20:44:58 UTC
Created attachment 593594 [details]
log from gtk-greeter

Comment 2 Christoph Wickert 2012-06-21 23:23:38 UTC
Is ConsoleKit-x11 installed?

Comment 3 Gregor Tätzner 2012-06-22 08:23:20 UTC
I'm tempted to mark this as a duplicate of 834427. @Heiko Can you have a look at your selinux log and try the suggested workaround?

At least on my system it doesn't make a difference if consolekit-x11 is installed or not.

Comment 4 Rex Dieter 2012-06-22 13:25:24 UTC
it's likely selinux-policy getting in the way, see bug #834427 

(a quick-n-dirty test would be to temporarily set selinux to permissive, and reboot)

Comment 5 Heiko Adams 2012-06-22 16:26:12 UTC
Yes, I can confirm that it's selinux what makes this trouble

Comment 6 Gregor Tätzner 2012-06-22 16:47:23 UTC

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