Bug 563603 - KDM crash on first login
Summary: KDM crash on first login
Keywords:
Status: CLOSED DUPLICATE of bug 549687
Alias: None
Product: Fedora
Classification: Fedora
Component: ConsoleKit
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-10 17:13 UTC by Mattia Verga
Modified: 2010-02-12 21:11 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-12 21:11:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
KDM related line in /var/log/messages at time of login (399 bytes, application/octet-stream)
2010-02-10 17:13 UTC, Mattia Verga
no flags Details

Description Mattia Verga 2010-02-10 17:13:04 UTC
Created attachment 390059 [details]
KDM related line in /var/log/messages at time of login

Description of problem:
When I type my username and password in KDM, the first time I try to login it simply return to login screen (I don't know if is KDM or X server to crash, I checker xorg.log and kdm.log but I don't find any useful information - to me). The only thing I found about KDM errors are in /var/log/messages, see attached file.
At the second try the login is successful and it loads KDE.

Version-Release number of selected component (if applicable):
xorg-X11-server-Xorg 1.7.99.3-3.20100208.fc13
kdm 4.4.0-2.fc13

How reproducible:
Always

Steps to Reproduce:
1.Start Fedora rawhide with runlevel 5 and KDM
2.Type username and password - it returns to login screen
3.Type username and password a second time - it works
  
Actual results:
You must type two times username and password

Expected results:
Logins at first try

Additional info:

Comment 1 Mattia Verga 2010-02-12 16:39:30 UTC
I change the "component" to "ConsoleKit" as the error I see in the log is related to that.

Comment 2 Kevin Kofler 2010-02-12 21:11:47 UTC

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


Note You need to log in before you can comment on or make changes to this bug.