I see the pen in the list of devices in the bluetooth settings, but I can't pair it. I'm running Ubuntu 20.04 on a Dell Latitude 3390.
Thanks
I am trying to get the stylus working properly on a One Netbook One Mix 3s tiny laptop.
This laptop is compatible with microsoft pens (I.e. it's using n-trig technology) but as far as I can tell the touchscreen is not actually made by Wacom.
On the newest Ubuntu version (19.0?) the touchscreen and stylus is not supported at all. In other versions of the distribution (for example 18.04.3 LTS) the touchscreen works great, but the stylus is detected as "clicking" as in it's as if you are holding the mouse button down when it is anywhere in the vicinity of the screen.
The output of xinput list looks like this:
ubuntu@ubuntu:~$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ HAILUCK CO.,LTD USB KEYBOARD Mouse id=12 [slave pointer (2)]
⎜ ↳ GXTP7386:00 27C6:0113 UNKNOWN id=16 [slave pointer (2)]
⎜ ↳ GXTP7386:00 27C6:0113 id=15 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ HAILUCK CO.,LTD USB KEYBOARD Wireless Radio Control id=11 [slave keyboard (3)]
↳ HAILUCK CO.,LTD USB KEYBOARD id=10 [slave keyboard (3)]
↳ HAILUCK CO.,LTD USB KEYBOARD Consumer Control id=14 [slave keyboard (3)]
↳ GXTP7386:00 27C6:0113 Keyboard id=17 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)]
↳ HAILUCK CO.,LTD USB KEYBOARD System Control id=13 [slave keyboard (3)]
On 18.04.3. Notice that one of the devices is called UNKNOWN. Also the device with a similar name, at id 15, I know for a fact is the touchscreen. So I am pretty sure the UNKNOWN one is supposed to be the pen.
A different computer made by the same company (the 2s) had a similar problem with the pen not working. It was solved by Adya on github who released a custom kernel module: https://bbs.archlinux.org/viewtopic.php?id=242893
This is the same behavior except on that computer, the pen didn t show up at all on xinput list. The fact that there is this UNKNOWN device makes me think the problem is a little different. Furthermore, some people on forums claimed that the pen worked well with KDE neon. I tested it and it wasn't detected at all. Perhaps because KDE neon is on a different version. Anyway, it seems like a shame if the newer version of Ubuntu is less compatible than the older one. I will try 18.04.2 and see if the pen support is different there.
Can anyone tell me what the differences are between the different Ubuntu releases? Is there any hope of fixing these issues and getting it running well on all future releases any time soon?
Update: Sure enough on Ubuntu 18.04.2, the stylus is working. xinput list gives the same except where there is UNKNOWN we have "Pen pen(0)". Will all the future Ubuntu releases not support this touchscreen? Can we just take some kinds of settings from somewhere and put them in the new versions?
Update to update: after installing Ubuntu 18.04.2 the pen is again set to UNKNOWN in xinput. It is still detected but behaves badly (always clicking). I have confirmed that id 16 is the pen using libinput
Edit: In Xournalpp, under devices, GXTP7386:00 Pen pen(0) DOES show up. That means somewhere this computer knows there's a pen... but xinput doesn't know where it is...
Edit: I followed these steps: (sort of) https://forums.linuxmint.com/viewtopic.php?f=59&t=312005&p=1762496#p1762496
Effect: xinput now calls GXTP7386:00 "touch" and the line with UNKNOWN disappears. The pen is no longer detected at all. <--- I don't think this has much to do with it because the config files in /usr/share/X11/xorg.conf.d/ look exactly the same on 18.04.2 and newer kernels.
Possibly relevant note: Behavior is the same on the newest Fedora release which apparently uses Wayland. So the problem must be something totally not related to "compositors" not that I know anything about that.
As requested here is lsusb output:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 002: ID 258a:0021
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
another comment: I am aware that this is kernel issue. I.e. the kernel does not support the devices. What I am asking is, what can we do to add/improve this support? And also, why not? Clearly the linux kernel supports other N-trig devices such as the Microsoft surface pro etc.
I have a Lenovo L13 Yoga and Lenovo ThinkPad Pen Pro with Ubuntu 19.10 installed on it.
I'd like to be able to use certain keyboard shortcuts while the notebook is folded down (especially shift + prt screen, to select an area with my stylus to screenshot).
Is there a way to achieve this, preferably other than using an on-screen keyboard?
I'm running Ubuntu 19.10 on a Dell Inspiron 13 7000 2-in-1 Black Edition (7391). The laptop comes with a really nice stylus, the Dell PN350M Active Pen, which unfortunately does not work under my system at all. A little bit of digging around the web reveals that the pen uses the Microsoft Pen Protocol to pair with a laptop instead of Bluetooth. Are these supported? Google leaves me with no answers.
EDIT:
Below is an updated output of xinput. There's something suspicious here, in particular the "UNKNOWN" thing.
~> xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ DELL0960:00 04F3:30E4 Touchpad id=9 [slave pointer (2)]
⎜ ↳ CUST0000:00 27C6:0111 id=10 [slave pointer (2)]
⎜ ↳ CUST0000:00 27C6:0111 UNKNOWN id=11 [slave pointer (2)]
⎜ ↳ PS/2 Generic Mouse id=16 [slave pointer (2)]
⎜ ↳ M585/M590 Mouse id=18 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Dell WMI hotkeys id=14 [slave keyboard (3)]
↳ Intel HID 5 button array id=13 [slave keyboard (3)]
↳ Intel HID events id=12 [slave keyboard (3)]
↳ Integrated_Webcam_HD: Integrate id=8 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
↳ M585/M590 Keyboard id=17 [slave keyboard (3)]
I'm using Kubuntu 16.04 (xenial) on a laptop with an ELAN Touchscreen together with a DELL 750-AAHC active stylus. One of the buttons on the stylus behaves as a mouse middle-button, and I want it to be a right button instead.
I can achieve this by doing
$ xinput set-button-map "ELAN Touchscreen Pen" 1 3 2
(i.e., mapping the function of button 3, which must correspond to the right button, to physical button 2).
This does what I want, but the change is not permanent.
I added the command in ~/.xsessionrc (according to the answer on this post), so it's run automatically when I reboot, but the button mapping "randomly" reverts to default on its own: it's working as expected for a while, and suddenly I discover that it doesn't, so I get
$ xinput get-button-map "ELAN Touchscreen Pen"
1 2 3 4 5
and I have to remap it manually.
I tried a few "suspect" things to see what might be responsible for reverting, but I couldn't figure it out. It's not caused by
- suspending the laptop or turning off the screen
- rotating the screen (this was suspect because xinput is used on rotation to transform the input matrix.)
- toggling touchscreen, touchpad or stylus input on/off (also with xinput).
IMPORTANT UPDATE:
I've discovered that this problem is not specific to the stylus: I disabled the finger-touch capability of the screen ("ELAN Touchscreen") earlier for some reason by doing:
$ xinput disable "ELAN Touchscreen"
and I just discovered that it came back on its own (and the stylus right-click had again reverted). So it seems like all xinput changes revert to default for this unknown reason.
UPDATE 2
I found some suspicious entries in /var/log/syslog when this happened again. The timestamps were during a time I had not actually been using the laptop for some time, so energy-saving features were probably activated (I have "dim screen" at 9 mins and "switch off" at 10 mins; I will experiment with energy saving and update accordingly).
The pattern bellow is actually repeated many times, with only a few seconds difference between each block.
usb 1-8: USB disconnect, device number 18
usb 1-8: new full-speed USB device number 19 using xhci_hcd
usb 1-8: New USB device found, idVendor=04f3, idProduct=2073
usb 1-8: New USB device strings: Mfr=4, Product=14, SerialNumber=0
usb 1-8: Product: Touchscreen
usb 1-8: Manufacturer: ELAN
input: ELAN Touchscreen Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:04F3:2073.04EE/input/input7548
input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:04F3:2073.04EE/input/input7549
input: ELAN Touchscreen Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:04F3:2073.04EE/input/input7552
hid-multitouch 0003:04F3:2073.04EE: input,hiddev0,hidraw0: USB HID v1.10 Keyboard [ELAN Touchscreen] on usb-0000:00:14.0-8/input0
In each block, almost everything is the same except a few numbers that increase. Here's the next block for comparison:
usb 1-8: USB disconnect, device number 19
usb 1-8: new full-speed USB device number 20 using xhci_hcd
usb 1-8: New USB device found, idVendor=04f3, idProduct=2073
usb 1-8: New USB device strings: Mfr=4, Product=14, SerialNumber=0
usb 1-8: Product: Touchscreen
usb 1-8: Manufacturer: ELAN
input: ELAN Touchscreen Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:04F3:2073.04EF/input/input7554
input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:04F3:2073.04EF/input/input7555
input: ELAN Touchscreen Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:04F3:2073.04EF/input/input7558
hid-mul itouch 0003:04F3:2073.04EF: input,hiddev0,hidraw0: USB HID v1.10 Keyboard [ELAN Touchscreen] on usb-0000:00:14.0-8/input0
The device numbers wrap around at 128.
System:
- KDE Plasma 5.5.5
- Qt 5.5.1
- Kernel 4.13.0-32-generic #35~16.04.1-Ubuntu 64-bit
xinput version 1.6.2
XI version on server: 2.3
X.Org X Server 1.19.5
Release Date: 2017-10-12
X Protocol Version 11, Revision 0