| Summary: | keyboard unresponsive when logging into gdm - startup race | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Joseph Wang <joequant> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | Keywords: | NEEDINFO |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gdm-3.2.0-1.mga2 | CVE: | |
| Status comment: | |||
| Attachments: |
gdm log
gdm log |
||
|
Description
Joseph Wang
2011-10-01 16:34:33 CEST
Created attachment 874 [details]
gdm log
Created attachment 875 [details]
gdm log
Joseph Wang
2011-10-01 17:30:45 CEST
Summary:
keyboard unresponsive when logging into gdm =>
keyboard unresponsive when logging into gdm - startup race This seems to be a startup race condition. When I switched to systemd, gdm behaves differently. I am able to use the keyboard, but gdm goes into classic mode because the dri device is not visible. It appears that dm is getting run too early in the boot process before the keyboard and the devices have settled down. And if you disable speedboot ? Thanks. It works perfectly when speedboot is off. Just one think to tho use systemd ?
Manuel Hiebel
2011-10-07 14:39:54 CEST
Keywords:
(none) =>
NEEDINFO so closing Status:
NEW =>
RESOLVED |