'Option "AutoAddDevices" "off"' is not preventing devices from being automatically added

Bug #488086 reported by Simon Booth
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

It's necessary for me to use 'Option "AutoAddDevices" "off"' in my xorg.conf, in order to work around bug 305955. However, since upgrading to Karmic, the workaround no longer works; even though I have that line in my xorg.conf, HAL devices are still automatically added and removed, so the bug remains and my system is as a result barely usable. (hopefully my Xorg log is attached and you can see the lines at the end where this is happening)

What do I need to do to turn off the use of HAL for input devices in Karmic?

ProblemType: Bug
Architecture: i386
CurrentDmesg:
 [ 40.980011] eth0: no IPv6 routers present
 [ 95.500020] Clocksource tsc unstable (delta = -67988415 ns)
 [ 8520.461392] padlock: VIA PadLock Hash Engine not detected.
 [ 8520.463758] PPP MPPE Compression module registered
Date: Wed Nov 25 09:15:17 2009
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 002 Device 003: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
 Bus 002 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 004: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: xserver-xorg-input-kbd 1:1.3.2-3
ProcCmdLine: root=UUID=32627e88-fc9e-45b9-bc36-d413531fa260 ro splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xserver-xorg-input-keyboard
Uname: Linux 2.6.31-15-generic i686
dmi.bios.date: 03/26/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N8L ACPI BIOS Revision 0404
dmi.board.name: M2N8L
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N8LACPIBIOSRevision0404:bd03/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2N8L:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-15-generic

Revision history for this message
Simon Booth (sgb-ubuntu) wrote :
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

It needs a boolean, try "false".

affects: xserver-xorg-input-keyboard (Ubuntu) → xorg-server (Ubuntu)
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
Johannes Reisinger (tschoo) wrote :

AutoAddDevices does not work for me in karmic too (and I used "false":-).
I use a special X-configuration for a couple of Ubuntu releases:
A second X-server with a special xorg.conf file is running on my PVR-350 (ivtv) card on which MythTV is running. For this I needed an xorg.conf without any input devices (mythtv is controlled by lirc).
But with Karmic, the 'AutoAddDevices' option does not work further.

Revision history for this message
Johannes Reisinger (tschoo) wrote :

Here is my Xorg.1.log ...

Revision history for this message
Bryce Harrington (bryce) wrote :

@tschoo - thanks for providing that info, but we would like to see it from the original reporter. We may want to send this bug report upstream, but upstream has a hard and fast rule that logs from someone other than the original reporter are not acceptable. The reason for that is that quite often with X.org bug reports, two people may *think* they have the same issue based on commonality of symptoms and/or hardware, but in truth they have separate issues and mixing the report and the files can cause the developers some confusion.

If this bug report seems not to be getting attention, I would encourage you to file a new bug report with this data, and simply reference this bug report in your bug description.

Changed in xorg-server (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Simon Booth (sgb-ubuntu) wrote :

@Bryce: you do have my logs - is there any other information I can provide? Using "false" rather than "off" didn't help.

Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Simon,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 488086

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 488086 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/488086

Changed in xorg-server (Ubuntu):
status: Incomplete → New
status: New → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Simon Booth (sgb-ubuntu) wrote :

Some good news, some bad news. It does seem that the option prevents the keyboard from being automatically added. Unfortunately, this meant that after the upgrade I had no keyboard at all in X, which was a bit awkward to say the least. However, my feeling is that this bug is probably fixed in Lucid and I can go back to worrying about bug 305955.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.