Fedora Account System
Red Hat Associate
Red Hat Customer
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Build Identifier: I can use the touchscreen features and the tablet's "Lock" button (which locks the screen), but cannot use the stylus. Reproducible: Always Steps to Reproduce: 1. Install Fedora 23 Workstation on a machine with an Wacom Penabled 2FG Touchscreen 2. Update 3. Use the touchscreen to, say, press activities 4. Try to use the pen to click on things or draw in Xournal (having installed the xournal package) 5. Lock the screen by pressing the padlock button next to the touch screen Actual Results: The touchscreen works fine, but no input is accepted from the stylus. The lock button locks the screen. Expected Results: Touchscreen should still work, and the pen should produce click events. Lock button should also work. Kernel version: 4.4.8-300.fc23.x86_64 By way of debugging, I've tried installing the kernel from fedora-rawhide-kernel-nodebug, 4.6.0-0.rc7.git1.1.fc25.x86_64 This fixes the issues with the stylus, and I can use all of the stylus' features including the eraser tip and pressure sensitivity on the pen tip. However, under that alternative kernel, the screen doesn't work as a touch screen - if I try to press things with my finger I get no response. So by choosing a different kernel from the GRUB menu I can choose either stylus or touchscreen, but can't have both.
Created attachment 1159612 [details] Initial debug output from both kernels I've attached lsmod, xsetwacom and xinput output under both kernels.
Created attachment 1159613 [details] Spreadsheet comparing working features on both tested kernels
Results of running on each kernel: dmesg | grep -i -e wacom -e touch 4.4 kernel from Fedora 23: [ 1.617136] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd047b3/0xb40000/0xa0000/0x0, board id: 0, fw id: 616291 [ 1.675160] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 8.252143] input: Wacom Serial Penabled 2FG Touchscreen as /devices/pnp0/00:05/tty/ttyS4/serio3/input/input15 4.6 kernel from rawhide: [ 1.854422] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd047b3/0xb40000/0xa0000/0x0, board id: 0, fw id: 616291 [ 1.913056] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 6.555321] input: Wacom Serial Penabled 2FG Touchscreen Pen as /devices/pnp0/00:05/tty/ttyS4/serio3/input/input15 [ 6.555875] input: Wacom Serial Penabled 2FG Touchscreen Finger as /devices/pnp0/00:05/tty/ttyS4/serio3/input/input16
Created attachment 1160308 [details] Details of investigation into raised events under /dev/input I've just been doing some further digging, and found that events are being raised in /dev/input/event* nodes for all touch and stylus features of the touchscreen. I've attached my method and more detailed findings. I also did git log and git diff on wacom_w8001.c in the upstream kernels on git.kernel.org and the work between 4.4 and 4.5 to split the device into separate device nodes for 'Pen' and 'Finger' events does provide a plausible partial explanation for the change of behaviour between the kernels, but doesn't explain why X doesn't support the full range of available features under either. Perhaps this isn't a kernel issue after all...
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
I've since upgraded to Fedora 24 and this issue has recently been fixed in that release (see Bug 1349686).
*** This bug has been marked as a duplicate of bug 1349686 ***