Hot answers tagged xinput
5
Turns out this problem was caused by a hardware fault in both mice. I fixed it by opening up my mouse and hosing down both the wheel and all the button swictes with compressed contact cleaner.
Unfortunately this dissolved the grease on the mousewheel rigging so I had to apply fresh silicone grease to these parts.
All in all, an £8 spend to bring a £100 ...
4
I'm using Enlightenment DM, but that's relevant to other DMs/desktops. I start my session using xsession so I initially put xinput commands in ~/.xsession which didn't change all settings I wanted to change. Only some of them. I was expecting either all or no changes, so I added a 10-interation loop to my .xsession with 1 second intervals, running xinput ...
4
The following methods will ensure your changes persist as long as you use gnome:
Install and run dconf-editor (if you're on 12.10, dconf-editor might be pre-installed):
$ sudo apt-get install dconf-tools
$ dconf-editor
Go to the following settings directory:
org.gnome.settings-daemon.peripherals
Under touchpad, uncheck the touchpad-enabled checkbox.
...
2
Answering my own question after lots of further research.
The new udev "philosophy"
Apparently the new "proper" way to use udev is not to incur long-running processes.
Via http://blog.fraggod.net/2012/06/16/proper-ish-way-to-start-long-running-systemd-service-on-udev-event-device-hotplug.html:
RUN ... Starting daemons or other long running processes ...
2
I don't have a fix, but I might have a hint as to what's happening.
I have the same mouse, and the same problem, and I suspect a kernel bug somewhere in the USB subsystem. Using kernel 3.2.0 (Debian-unstable), and following the usbmon documentation:
# mount -t debugfs none_debugfs /sys/kernel/debug
# modprobe usbmon
# grep -B5 SteelSeries ...
2
Ditto. Except that disabling it in Windows only seems to temporarily fix the problem--it resurfaces if the mouse is reconnected. Which, interestingly, seems to then persist until I next visit Windows. I should probably stop plugging it into my monitor.
I also tried the 3.4 kernel from the kernel PPA to no effect.
After some searching about for this error ...
2
Same problem here as well with same behaviour. I've made a workaround for that by USB resetting the device using simple libusb solution and a wrapper which uses lsusb output to reset Ideazon and that works for me.
I can also confirm that changing HID_MAX_USAGES doesn't help at all. Neither helps removing additional HID Keyboard device that Sensei exports ...
1
Instructions for your wireless mouse: I noted it has 2 ids, but I think no. 12 should be the one you want to use (if not, try the others).
I see in your first codeblock you have got the device ids for your hardware (this can be done just by entering xinput). Now, with that in mind, select the id you want to use, e.g. 12, and gain the detailed readout of ...
1
If reinstalling synaptics doesn't work. Try adding this to your /etc/X11/xorg.conf file. You should have it if you have the nvidia driver installed. If not create one.
Section "InputClass"
Identifier "touchpad"
Driver "synaptics"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
...
1
So you want a substring?
string=$(xinput | grep HID | cut -f 2);
echo ${string:3}
This does not work in shell only in bash
chad@M4A79XTD-EVO:~$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ HID 04b4:0033 id=8 ...
1
This should work for you.
xinput list|grep AT|grep id=|cut -f 2|cut -f 2 -d =
cut command has an option to specify the delimiter.
xinput list|grep AT|grep id=|cut -f 2
This gives you id=13, so pass it to another cut command specifying the delimiter as =
Sample
~$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ ...
Only top voted, non community-wiki answers of a minimum length are eligible
