Bug 1046756

Summary: No X display even if X server and GDM seems to start fine
Product: [Fedora] Fedora Reporter: Yann Droneaud <yann>
Component: libevdevAssignee: Peter Hutterer <peter.hutterer>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ajax, peter.hutterer, xgl-maint
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: 2014-01-03 01:37:03 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 Yann Droneaud 2013-12-26 22:56:57 UTC 
I'm using Fedora 20 on a Lenovo Thinkpad X220.

After installing updates for Fedora 20 and rebooting, I'm now facing a fixed console display while I would expect a GDM login screen.

GDM is started and Xorg server is running and alive: according to server log, it detects VT switch and handle it (I have to hit CTRL+ALT-F2 to exit from the first console, while I have to hit CTRL-F1 to go back to the console used by X / GDM). But the first virtual console which is devoted to X only show the boot messages and don't support any interaction (mouse, keyboard).

I have tested with kernel option i915.modeset=1 added on command line through grub without any change on the behavor.
Comment 1 Yann Droneaud 2013-12-28 11:13:24 UTC 
After downgrading libevdev (from -testing), graphical login screen is shown on the computer.

libevdev-0.6-1.fc20.x86_64 was installed from testing repo, downgrading to libevdev-0.5-1.fc20.x86_64 fix my problem.

My issue is reported https://admin.fedoraproject.org/updates/FEDORA-2013-23934/libevdev-0.6-1.fc20?_csrf_token=637132ef43236645ce9d396b74eefbb45ff2668b
Comment 2 Peter Hutterer 2014-01-03 01:37:03 UTC 

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