Bug 2867 - xorg.conf generated by drakX11 causes keyboard on aspire one to fail / missing AutoAddDevices off
Summary: xorg.conf generated by drakX11 causes keyboard on aspire one to fail / missin...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-09-29 02:37 CEST by Joseph Wang
Modified: 2011-10-26 17:58 CEST (History)
0 users

See Also:
Source RPM: drakx-kbd-mouse-x11
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Joseph Wang 2011-09-29 02:37:50 CEST 
Description of problem:

the xorg.conf generated by drakX11 is missing an AutoAddDevices "off".  Without this tag my Aspire One 722 mistakes the webcam for a keyboard and so creates a xorg.conf that doesn't work.

This used to work in mga1, but something changed in cauldron


Version-Release number of selected component (if applicable):


How reproducible:

Run drakx11 on an Aspire One 722.  Select ati as card.  Reboot.  Keyboard is unresponsive.


Steps to Reproduce:
1.
2.
3.
Manuel Hiebel 2011-09-29 10:58:07 CEST

Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2011-09-29 14:18:17 CEST 
Wrong pagkage.

Better fix the real issue.
Please attach (not paste) your /var/log/Xorg.0.log file with and without this line added to your xorg.conf

Keywords: (none) => NEEDINFO
Source RPM: drakconf-12.21.9-3.mga2 => drakx-kbd-mouse-x11

Comment 2 Manuel Hiebel 2011-10-25 12:02:56 CEST 
ping ?
Comment 3 Joseph Wang 2011-10-26 17:58:54 CEST 
I tried everything with the latest cauldron and everything seems to work.  In particular X11 no longer seems to confuse the webcam and the keyboard.

Resetting status to resolved/worksforme

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.