You are not logged in.
xinput list gives me
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=16 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech TrackPoint id=17 [slave pointer (2)]
⎜ ↳ Logitech M325 id=13 [slave pointer (2)]
⎜ ↳ Logitech K360 id=12 [slave pointer (2)]
⎜ ↳ Wacom Pen and multitouch sensor Pen stylus id=11 [slave pointer (2)]
⎜ ↳ Wacom Pen and multitouch sensor Pen eraser id=19 [slave pointer (2)]
⎜ ↳ Wacom Pen and multitouch sensor Finger touch id=10 [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)]
↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=18 [slave keyboard (3)]
↳ Integrated Camera: Integrated C id=14 [slave keyboard (3)]
↳ Logitech K360 id=20 [slave keyboard (3)]
Stylus (11) is the stylus' tip, eraser (19) is the same tip when the lowest button is pressed and touch (10) is, well, the touchscreen. There are three buttons on the pen: Two side buttons and a top button. The side buttons work, but the top button doesn't even seem to show up in the list. I already tried out some of the devices with xinput test. In the graphics tablet configuration tool the button is configurable, but it has no effect.
KDE Plasma, ThinkPad X380 Yoga, Intel Core i7-8550U, Intel UHD Graphics 620, 512GB PCIe-NVMe SSD (OPAL 2.0), 16GB PC4-19200 (2400 MHz)
Offline
You can use xev to find the button id of the event and use xsetwacom to map the button to desired function. For instance I have an Intuos and its 4 buttons are registered as 1,2,3,8. I set button 1 as:
xsetwacom set "Wacom Intuos BT S Pad pad" Button 1 "key +ctl z -ctl" for instance.
Offline
No it is not recognized by xev. I realized something else. When the top button is pressed for a few seconds, you can pair it via bluetooth. After you release the button, the bluetooth connection ceases. When you press the button, it instantly establishes a bluetooth connection again. So I think that I must configure an action on the bluetooth connection of the device! It is not a button in the normal button sense. Any ideas how that could be done?
The pen and the other two buttons work without pairing the device btw.
Last edited by gunjah292 (2019-03-31 10:54:37)
KDE Plasma, ThinkPad X380 Yoga, Intel Core i7-8550U, Intel UHD Graphics 620, 512GB PCIe-NVMe SSD (OPAL 2.0), 16GB PC4-19200 (2400 MHz)
Offline
In xev did you point the pen on top of the monitoring window before pushing the button? The bluetooth issue is strange indeed. What functionality would you like for the top button?
Offline
Yes, I did. It shows the other two buttons, but not the top button. I also realized that there are two BT devices called Bamboo Ink. One I could connect and has a normal icon. The other one has a keyboard icon and I can't connect to it.
I want the top button to open Xournal++.
KDE Plasma, ThinkPad X380 Yoga, Intel Core i7-8550U, Intel UHD Graphics 620, 512GB PCIe-NVMe SSD (OPAL 2.0), 16GB PC4-19200 (2400 MHz)
Offline
I tried to write a udev rule /etc/udev/rules.d/99-bambooinkbutton.rules
KERNEL="hidraw" \
SUBSYSTEM="hidraw" \
ATTRS{address}=="c0:a4:e9:ae:2d:78" \
RUN+="xournalpp"
Unfortunately it doesn't work.
KDE Plasma, ThinkPad X380 Yoga, Intel Core i7-8550U, Intel UHD Graphics 620, 512GB PCIe-NVMe SSD (OPAL 2.0), 16GB PC4-19200 (2400 MHz)
Offline
Do you connect the device via USB or bluetooth? You can use udevadm monitor, connect and disconnect your device to determine how udev registers the device. From that info you can create your udev rule. I think you need more info for your udev rule. However, unless the button is recognised I don't think you can add the functionality to it.
Offline
I connect it via bluetooth of course. As I've said the button is not directly recognized, but when I press it, the pen establishes a bluetooth connection which ceases, when you release the button. So you just need to assign an event to the connection of the device. The drawing of the pen doesn't need bluetooth. Just this one button
KDE Plasma, ThinkPad X380 Yoga, Intel Core i7-8550U, Intel UHD Graphics 620, 512GB PCIe-NVMe SSD (OPAL 2.0), 16GB PC4-19200 (2400 MHz)
Offline
I don't know if it's possible to map the button if it doesn't trigger an event. Of course it trggers the bluetooth event but that doesn't seem to trigger an id for the event. I asked if you're using USB or bluetooth because it would be good to know if using USB would trigger an event different from bluetooth or an an event with specific id. Have you tried connecting via USB and checking xev or udev monitor to see if that button triggers an event?
Offline
The pen doesn't have a usb connection. It is a pen and you insert a battery.
KDE Plasma, ThinkPad X380 Yoga, Intel Core i7-8550U, Intel UHD Graphics 620, 512GB PCIe-NVMe SSD (OPAL 2.0), 16GB PC4-19200 (2400 MHz)
Offline