3M touchscreen is being recognized as a mouse
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I plugged in 3M touchscreen to my Linux PC. It appears as it recognizes it as a mouse here's my xinput output:
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=13 [slave pointer (2)]
⎜ ↳ 3M 3M USB Touchscreen - 36955 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)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Logitech USB Keyboard id=10 [slave keyboard (3)]
↳ Logitech USB Keyboard id=11 [slave keyboard (3)]
↳ HP WMI hotkeys id=14 [slave keyboard (3)
On windows 7 it works after installing driver from this site so I also tried to install Linux driver from here (Linux, Single Touch, 64bit). I think installation process fails as it interrupts immediately after I accept the license.
I test my touchscreen with Qt FingerPaint example (also works on Windows, doesn't work on Ubuntu).
I use Ubuntu 16.04 with kernel 4.10.0-35-generic and tried both Unity and Cinnamon environments. I need this for programming purposes.
EDIT:
The kernel module which supports the device is usbtouchscreen. After disabling it with sudo modprobe -r usbtouchscreen the device doesn't work at all.
And the xinput output:
$ xinput --list 10
3M 3M USB Touchscreen - 36955 id=10 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 10. Type: XIButtonClass
Buttons supported: 5
Button labels: "Button Unknown" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down"
Button state:
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs X
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8076.000000
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs Y
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8228.00000
- Pastebin with xinput -test-xi2 10
- Pastebin with /var/log/Xorg.0.log
drivers xinput touch-screen multi-touch
asked Oct 2 '17 at 9:39
jaskmar
513
 |Â
show 3 more comments
up vote
0
down vote
favorite
I plugged in 3M touchscreen to my Linux PC. It appears as it recognizes it as a mouse here's my xinput output:
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=13 [slave pointer (2)]
⎜ ↳ 3M 3M USB Touchscreen - 36955 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)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Logitech USB Keyboard id=10 [slave keyboard (3)]
↳ Logitech USB Keyboard id=11 [slave keyboard (3)]
↳ HP WMI hotkeys id=14 [slave keyboard (3)
On windows 7 it works after installing driver from this site so I also tried to install Linux driver from here (Linux, Single Touch, 64bit). I think installation process fails as it interrupts immediately after I accept the license.
I test my touchscreen with Qt FingerPaint example (also works on Windows, doesn't work on Ubuntu).
I use Ubuntu 16.04 with kernel 4.10.0-35-generic and tried both Unity and Cinnamon environments. I need this for programming purposes.
EDIT:
The kernel module which supports the device is usbtouchscreen. After disabling it with sudo modprobe -r usbtouchscreen the device doesn't work at all.
And the xinput output:
$ xinput --list 10
3M 3M USB Touchscreen - 36955 id=10 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 10. Type: XIButtonClass
Buttons supported: 5
Button labels: "Button Unknown" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down"
Button state:
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs X
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8076.000000
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs Y
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8228.00000
- Pastebin with xinput -test-xi2 10
- Pastebin with /var/log/Xorg.0.log
drivers xinput touch-screen multi-touch
asked Oct 2 '17 at 9:39
jaskmar
513
could you please addlsmod(there should be a specific driver loaded for your touchpad as a mouse) you can tell which withmodinfoand blacklisting it could fix the issue
– Christopher DÃaz Riveros
Oct 9 '17 at 2:02
@ChristopherDÃazRiveros see the edited question.
– jaskmar
Oct 9 '17 at 8:19
X will lump all devices that generate positional events under "mouse" and attach them to the "virtual core pointer" (i.e., source of mouse events). What you've shown so far gives no indication that the touchpad isn't recognized as touchpad. Runxinput -test-xi2 12(if 12 is still the current touchpad device id, they may change) and see if you can get multitouch events. In case it doesn't, please upload/var/log/Xorg.0.logto a pastebin etc. and edit question with link. Also edit question with output ofxinput --list 12.
– dirkt
Oct 9 '17 at 9:24
@dirkt I updated
– jaskmar
Oct 9 '17 at 9:38
As you can see from Xorg.log, X detects this device as touchscreen with absolute positions. With the current driver configuration, it only appears to produce a single touch position event, but it's a touchscreen, not a mouse. What features are missing you can get with the Windows driver? Multitouch? Pressure? Anything else? Or is the problem that it doesn't work with QTouchEvent? (which would make it a "how to configure X and/or Qt so it presents those events differently" question).
– dirkt
Oct 9 '17 at 11:33
 |Â
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I plugged in 3M touchscreen to my Linux PC. It appears as it recognizes it as a mouse here's my xinput output:
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=13 [slave pointer (2)]
⎜ ↳ 3M 3M USB Touchscreen - 36955 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)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Logitech USB Keyboard id=10 [slave keyboard (3)]
↳ Logitech USB Keyboard id=11 [slave keyboard (3)]
↳ HP WMI hotkeys id=14 [slave keyboard (3)
On windows 7 it works after installing driver from this site so I also tried to install Linux driver from here (Linux, Single Touch, 64bit). I think installation process fails as it interrupts immediately after I accept the license.
I test my touchscreen with Qt FingerPaint example (also works on Windows, doesn't work on Ubuntu).
I use Ubuntu 16.04 with kernel 4.10.0-35-generic and tried both Unity and Cinnamon environments. I need this for programming purposes.
EDIT:
The kernel module which supports the device is usbtouchscreen. After disabling it with sudo modprobe -r usbtouchscreen the device doesn't work at all.
And the xinput output:
$ xinput --list 10
3M 3M USB Touchscreen - 36955 id=10 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 10. Type: XIButtonClass
Buttons supported: 5
Button labels: "Button Unknown" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down"
Button state:
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs X
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8076.000000
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs Y
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8228.00000
- Pastebin with xinput -test-xi2 10
- Pastebin with /var/log/Xorg.0.log
drivers xinput touch-screen multi-touch
asked Oct 2 '17 at 9:39
jaskmar
513
I plugged in 3M touchscreen to my Linux PC. It appears as it recognizes it as a mouse here's my xinput output:
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=13 [slave pointer (2)]
⎜ ↳ 3M 3M USB Touchscreen - 36955 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)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Logitech USB Keyboard id=10 [slave keyboard (3)]
↳ Logitech USB Keyboard id=11 [slave keyboard (3)]
↳ HP WMI hotkeys id=14 [slave keyboard (3)
On windows 7 it works after installing driver from this site so I also tried to install Linux driver from here (Linux, Single Touch, 64bit). I think installation process fails as it interrupts immediately after I accept the license.
I test my touchscreen with Qt FingerPaint example (also works on Windows, doesn't work on Ubuntu).
I use Ubuntu 16.04 with kernel 4.10.0-35-generic and tried both Unity and Cinnamon environments. I need this for programming purposes.
EDIT:
The kernel module which supports the device is usbtouchscreen. After disabling it with sudo modprobe -r usbtouchscreen the device doesn't work at all.
And the xinput output:
$ xinput --list 10
3M 3M USB Touchscreen - 36955 id=10 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 10. Type: XIButtonClass
Buttons supported: 5
Button labels: "Button Unknown" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down"
Button state:
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs X
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8076.000000
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs Y
Range: 0.000000 - 16384.000000
Resolution: 0 units/m
Mode: absolute
Current value: 8228.00000
- Pastebin with xinput -test-xi2 10
- Pastebin with /var/log/Xorg.0.log
drivers xinput touch-screen multi-touch
drivers xinput touch-screen multi-touch
asked Oct 2 '17 at 9:39
jaskmar
513
asked Oct 2 '17 at 9:39
jaskmar
513
edited Oct 9 '17 at 9:36
asked Oct 2 '17 at 9:39
jaskmar
513
asked Oct 2 '17 at 9:39
jaskmar
513
asked Oct 2 '17 at 9:39
jaskmar
513
513
could you please addlsmod(there should be a specific driver loaded for your touchpad as a mouse) you can tell which withmodinfoand blacklisting it could fix the issue
– Christopher DÃaz Riveros
Oct 9 '17 at 2:02
@ChristopherDÃazRiveros see the edited question.
– jaskmar
Oct 9 '17 at 8:19
X will lump all devices that generate positional events under "mouse" and attach them to the "virtual core pointer" (i.e., source of mouse events). What you've shown so far gives no indication that the touchpad isn't recognized as touchpad. Runxinput -test-xi2 12(if 12 is still the current touchpad device id, they may change) and see if you can get multitouch events. In case it doesn't, please upload/var/log/Xorg.0.logto a pastebin etc. and edit question with link. Also edit question with output ofxinput --list 12.
– dirkt
Oct 9 '17 at 9:24
@dirkt I updated
– jaskmar
Oct 9 '17 at 9:38
As you can see from Xorg.log, X detects this device as touchscreen with absolute positions. With the current driver configuration, it only appears to produce a single touch position event, but it's a touchscreen, not a mouse. What features are missing you can get with the Windows driver? Multitouch? Pressure? Anything else? Or is the problem that it doesn't work with QTouchEvent? (which would make it a "how to configure X and/or Qt so it presents those events differently" question).
– dirkt
Oct 9 '17 at 11:33
 |Â
show 3 more comments
could you please addlsmod(there should be a specific driver loaded for your touchpad as a mouse) you can tell which withmodinfoand blacklisting it could fix the issue
– Christopher DÃaz Riveros
Oct 9 '17 at 2:02
@ChristopherDÃazRiveros see the edited question.
– jaskmar
Oct 9 '17 at 8:19
X will lump all devices that generate positional events under "mouse" and attach them to the "virtual core pointer" (i.e., source of mouse events). What you've shown so far gives no indication that the touchpad isn't recognized as touchpad. Runxinput -test-xi2 12(if 12 is still the current touchpad device id, they may change) and see if you can get multitouch events. In case it doesn't, please upload/var/log/Xorg.0.logto a pastebin etc. and edit question with link. Also edit question with output ofxinput --list 12.
– dirkt
Oct 9 '17 at 9:24
@dirkt I updated
– jaskmar
Oct 9 '17 at 9:38
As you can see from Xorg.log, X detects this device as touchscreen with absolute positions. With the current driver configuration, it only appears to produce a single touch position event, but it's a touchscreen, not a mouse. What features are missing you can get with the Windows driver? Multitouch? Pressure? Anything else? Or is the problem that it doesn't work with QTouchEvent? (which would make it a "how to configure X and/or Qt so it presents those events differently" question).
– dirkt
Oct 9 '17 at 11:33
could you please add
lsmod (there should be a specific driver loaded for your touchpad as a mouse) you can tell which with modinfo and blacklisting it could fix the issue– Christopher DÃaz Riveros
Oct 9 '17 at 2:02
could you please add
lsmod (there should be a specific driver loaded for your touchpad as a mouse) you can tell which with modinfo and blacklisting it could fix the issue– Christopher DÃaz Riveros
Oct 9 '17 at 2:02
@ChristopherDÃazRiveros see the edited question.
– jaskmar
Oct 9 '17 at 8:19
@ChristopherDÃazRiveros see the edited question.
– jaskmar
Oct 9 '17 at 8:19
X will lump all devices that generate positional events under "mouse" and attach them to the "virtual core pointer" (i.e., source of mouse events). What you've shown so far gives no indication that the touchpad isn't recognized as touchpad. Run
xinput -test-xi2 12 (if 12 is still the current touchpad device id, they may change) and see if you can get multitouch events. In case it doesn't, please upload /var/log/Xorg.0.log to a pastebin etc. and edit question with link. Also edit question with output of xinput --list 12.– dirkt
Oct 9 '17 at 9:24
X will lump all devices that generate positional events under "mouse" and attach them to the "virtual core pointer" (i.e., source of mouse events). What you've shown so far gives no indication that the touchpad isn't recognized as touchpad. Run
xinput -test-xi2 12 (if 12 is still the current touchpad device id, they may change) and see if you can get multitouch events. In case it doesn't, please upload /var/log/Xorg.0.log to a pastebin etc. and edit question with link. Also edit question with output of xinput --list 12.– dirkt
Oct 9 '17 at 9:24
@dirkt I updated
– jaskmar
Oct 9 '17 at 9:38
@dirkt I updated
– jaskmar
Oct 9 '17 at 9:38
As you can see from Xorg.log, X detects this device as touchscreen with absolute positions. With the current driver configuration, it only appears to produce a single touch position event, but it's a touchscreen, not a mouse. What features are missing you can get with the Windows driver? Multitouch? Pressure? Anything else? Or is the problem that it doesn't work with QTouchEvent? (which would make it a "how to configure X and/or Qt so it presents those events differently" question).
– dirkt
Oct 9 '17 at 11:33
As you can see from Xorg.log, X detects this device as touchscreen with absolute positions. With the current driver configuration, it only appears to produce a single touch position event, but it's a touchscreen, not a mouse. What features are missing you can get with the Windows driver? Multitouch? Pressure? Anything else? Or is the problem that it doesn't work with QTouchEvent? (which would make it a "how to configure X and/or Qt so it presents those events differently" question).
– dirkt
Oct 9 '17 at 11:33
 |Â
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f395610%2f3m-touchscreen-is-being-recognized-as-a-mouse%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
could you please add
lsmod(there should be a specific driver loaded for your touchpad as a mouse) you can tell which withmodinfoand blacklisting it could fix the issue– Christopher DÃaz Riveros
Oct 9 '17 at 2:02
@ChristopherDÃazRiveros see the edited question.
– jaskmar
Oct 9 '17 at 8:19
X will lump all devices that generate positional events under "mouse" and attach them to the "virtual core pointer" (i.e., source of mouse events). What you've shown so far gives no indication that the touchpad isn't recognized as touchpad. Run
xinput -test-xi2 12(if 12 is still the current touchpad device id, they may change) and see if you can get multitouch events. In case it doesn't, please upload/var/log/Xorg.0.logto a pastebin etc. and edit question with link. Also edit question with output ofxinput --list 12.– dirkt
Oct 9 '17 at 9:24
@dirkt I updated
– jaskmar
Oct 9 '17 at 9:38
As you can see from Xorg.log, X detects this device as touchscreen with absolute positions. With the current driver configuration, it only appears to produce a single touch position event, but it's a touchscreen, not a mouse. What features are missing you can get with the Windows driver? Multitouch? Pressure? Anything else? Or is the problem that it doesn't work with QTouchEvent? (which would make it a "how to configure X and/or Qt so it presents those events differently" question).
– dirkt
Oct 9 '17 at 11:33