xinput no longer works to set-ptr-feedback after the latest Xserver upgrade in Lucid

[Michael Marley]

Binary package hint: xinput

I had been using xinput to set the pointer acceleration on my Synaptics touchpad to 0 to work around another bug that has been present since Jaunty, but running the latest Xserver update in Lucid (and the one before that too, I think) causes "xinput set-ptr-feedback" to fail with the following message:

unable to find device SynPS/2 Synaptics TouchPad

even though "xinput list" does show the device.

[Bryce Harrington (bryce)]

Hi thefirstm,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Michael Marley (mamarley)]

Here is the lspci -vvnn

[Michael Marley (mamarley)]

And xorg.conf. There isn't anything about input in here, all that is autodetected. The only reason I have an xorg.conf at all is to load up the Nvidia blob.

[Michael Marley (mamarley)]

And a dmesg for good measure.

[Duncan Sands (baldrick-free)]

I'm having the same problem: some device names are not recognized any more, in my case "bcm5974".
As you can see below, "xinput list" shows this device, and I can manipulate it using the id (12) but not the
name ("bcm5974"). I could use the name with karmic, but not since I upgraded to lucid.

$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ "Logitech USB-PS/2 Optical Mouse" id=10 [slave pointer (2)]
⎜ ↳ "Macintosh mouse button emulation" id=14 [slave pointer (2)]
⎜ ↳ "bcm5974" id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ "Power Button" id=6 [slave keyboard (3)]
    ↳ "Video Bus" id=7 [slave keyboard (3)]
    ↳ "Power Button" id=8 [slave keyboard (3)]
    ↳ "Sleep Button" id=9 [slave keyboard (3)]
    ↳ "Apple, Inc. Apple Internal Keyboard / Trackpad" id=11 [slave keyboard (3)]
    ↳ "Built-in iSight" id=13 [slave keyboard (3)]
$ xinput set-int-prop "bcm5974" "Device Enabled" 8 0
unable to find device bcm5974
$ xinput set-int-prop 12 "Device Enabled" 8 0

[hmatsue (hmatsue)]

I wonder it is caused by "XListInputDevices" in xinput.c
The expectancy of "devices[loop].name" is;
PS2++ Logitech TrackMan
in my case, but it was;
"PS2++ Logitech TrackMan"
actually.
So that,
if ((!only_extended || (devices[loop].use >= IsXExtensionDevice)) &&
     ((!is_id && strcmp(devices[loop].name, name) == 0) ||
      (is_id && devices[loop].id == id)))
returns always false.
Is it a bug of XLib?
Or should xinput treat those double quotations?

[hmatsue (hmatsue)]

I think this bug had been fixed some time ago.

[dino99 (9d9)]

Closing that outdated report as EOL has been reached long time ago