You are not logged in.
Hello.
After last upgrade graphic tablet XP-PEN STAR G640 mouse pointer stop working.
Mouse buttons work on it, but the cursor does not move.
xinput --list output:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ HID 04f3:0103 Consumer Control id=10 [slave pointer (2)]
⎜ ↳ A4TECH USB Device Consumer Control id=14 [slave pointer (2)]
⎜ ↳ A4TECH USB Device id=15 [slave pointer (2)]
⎜ ↳ XP-PEN STAR G640 id=18 [slave pointer (2)]
⎜ ↳ XP-PEN STAR G640 Mouse id=19 [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)]
↳ Power Button id=7 [slave keyboard (3)]
↳ USB PnP Audio Device(EEPROM) id=8 [slave keyboard (3)]
↳ HID 04f3:0103 id=9 [slave keyboard (3)]
↳ HID 04f3:0103 System Control id=11 [slave keyboard (3)]
↳ A4TECH USB Device Keyboard id=12 [slave keyboard (3)]
↳ A4TECH USB Device System Control id=13 [slave keyboard (3)]
↳ Eee PC WMI hotkeys id=20 [slave keyboard (3)]
↳ HID 04f3:0103 Consumer Control id=21 [slave keyboard (3)]
↳ A4TECH USB Device Consumer Control id=22 [slave keyboard (3)]
↳ XP-PEN STAR G640 id=16 [slave keyboard (3)]
↳ XP-PEN STAR G640 Keyboard id=17 [slave keyboard (3)]
dmesg:
[ 2561.607996] usb 2-3.3: USB disconnect, device number 9
[ 2562.336915] usb 2-3.3: new full-speed USB device number 10 using xhci_hcd
[ 2562.437734] usb 2-3.3: New USB device found, idVendor=28bd, idProduct=0094, bcdDevice= 0.00
[ 2562.437739] usb 2-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2562.437741] usb 2-3.3: Product: STAR G640
[ 2562.437743] usb 2-3.3: Manufacturer: XP-PEN
[ 2562.447489] input: XP-PEN STAR G640 Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.3/2-3.3:1.0/0003:28BD:0094.000F/input/input37
[ 2562.447843] hid-generic 0003:28BD:0094.000F: input,hidraw0: USB HID v1.00 Mouse [XP-PEN STAR G640] on usb-0000:00:14.0-3.3/input0
[ 2562.448781] input: XP-PEN STAR G640 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.3/2-3.3:1.1/0003:28BD:0094.0010/input/input38
[ 2562.448982] input: XP-PEN STAR G640 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.3/2-3.3:1.1/0003:28BD:0094.0010/input/input39
[ 2562.449102] input: XP-PEN STAR G640 Keyboard as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.3/2-3.3:1.1/0003:28BD:0094.0010/input/input40
[ 2562.503982] hid-generic 0003:28BD:0094.0010: input,hiddev0,hidraw1: USB HID v1.00 Keyboard [XP-PEN STAR G640] on usb-0000:00:14.0-3.3/input1
[ 2562.504769] hid-generic 0003:28BD:0094.0011: hiddev1,hidraw2: USB HID v1.00 Device [XP-PEN STAR G640] on usb-0000:00:14.0-3.3/input2
[ 2730.629267] audit: type=1006 audit(1536480001.261:8): pid=13947 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=7 res=1
[ 2730.629272] audit: type=1006 audit(1536480001.261:9): pid=13946 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=8 res=1
[ 2730.629276] audit: type=1006 audit(1536480001.261:10): pid=13945 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=9 res=1
[ 3330.521306] audit: type=1006 audit(1536480601.152:11): pid=23293 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=10 res=1
But the strange thing is that the cursor is registered in libinput debug-events:
event12 POINTER_MOTION_ABSOLUTE +3.76s 37.19/ 92.70
event12 POINTER_MOTION_ABSOLUTE +3.77s 37.20/ 92.69
event12 POINTER_MOTION_ABSOLUTE +3.77s 37.20/ 92.69
event12 POINTER_MOTION_ABSOLUTE +3.78s 37.21/ 92.69
event12 POINTER_MOTION_ABSOLUTE +3.78s 37.21/ 92.69
event12 POINTER_MOTION_ABSOLUTE +3.79s 37.21/ 92.68
event12 POINTER_MOTION_ABSOLUTE +3.80s 37.21/ 92.68
event12 POINTER_MOTION_ABSOLUTE +3.80s 37.22/ 92.68
event12 POINTER_MOTION_ABSOLUTE +3.81s 37.23/ 92.68
event12 POINTER_MOTION_ABSOLUTE +3.81s 37.24/ 92.68
event12 POINTER_BUTTON +3.81s BTN_LEFT (272) released, seat count: 0
event12 POINTER_MOTION_ABSOLUTE +3.81s 37.25/ 92.68
event12 POINTER_MOTION_ABSOLUTE +3.82s 37.26/ 92.68
event12 POINTER_MOTION_ABSOLUTE +3.82s 37.26/ 92.68
event12 POINTER_MOTION_ABSOLUTE +3.83s 37.26/ 92.57
event12 POINTER_MOTION_ABSOLUTE +3.84s 37.15/ 92.43
event12 POINTER_MOTION_ABSOLUTE +3.84s 37.08/ 92.43
event12 POINTER_MOTION_ABSOLUTE +3.85s 37.00/ 92.26
event12 POINTER_MOTION_ABSOLUTE +3.85s 36.91/ 92.18
But not in xev:
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718749, (475,249), root:(1439,815),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718751, (477,249), root:(1441,815),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718753, (478,250), root:(1442,816),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718755, (480,250), root:(1444,816),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718757, (481,250), root:(1445,816),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718759, (482,250), root:(1446,816),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718761, (484,250), root:(1448,816),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718763, (485,250), root:(1449,816),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3718767, (486,250), root:(1450,816),
state 0x0, is_hint 0, same_screen YES
ButtonPress event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3721211, (486,250), root:(1450,816),
state 0x0, button 1, same_screen YES
ButtonRelease event, serial 33, synthetic NO, window 0x4800001,
root 0x1e1, subw 0x0, time 3721311, (486,250), root:(1450,816),
state 0x100, button 1, same_screen YES
lsusb:
Bus 002 Device 010: ID 28bd:0094
what was updated:
tail -n 1500 /var/log/pacman.log | grep -P "(09-0[78])" | grep upgrad
[2018-09-07 14:37] [PACMAN] starting full system upgrade
[2018-09-07 14:37] [ALPM] upgraded udisks2 (2.7.7-1 -> 2.8.0-1)
[2018-09-07 18:10] [PACMAN] starting full system upgrade
[2018-09-07 18:10] [ALPM] upgraded coreutils (8.29-1 -> 8.30-1)
[2018-09-07 18:10] [ALPM] upgraded file (5.33-3 -> 5.34-1)
[2018-09-07 18:10] [ALPM] upgraded sudo (1.8.24-1 -> 1.8.25-1)
[2018-09-07 19:01] [ALPM] upgraded visual-studio-code-bin (1.26.1-2 -> 1.27.1-1)
[2018-09-08 08:03] [PACMAN] starting full system upgrade
[2018-09-08 08:03] [ALPM] upgraded curl (7.61.0-2 -> 7.61.1-1)
[2018-09-08 08:03] [ALPM] upgraded glib2 (2.56.2-1 -> 2.58.0-1)
[2018-09-08 08:03] [ALPM] upgraded ghostscript (9.24-2 -> 9.24-5)
[2018-09-08 08:03] [ALPM] upgraded json-c (0.13.1-1 -> 0.13.1-2)
[2018-09-08 08:03] [ALPM] upgraded lib32-p11-kit (0.23.13-2 -> 0.23.14-1)
[2018-09-08 08:03] [ALPM] upgraded libarchive (3.3.2-2 -> 3.3.3-1)
[2018-09-08 08:03] [ALPM] upgraded libgsf (1.14.43-1 -> 1.14.44-1)
[2018-09-08 08:03] [ALPM] upgraded linux (4.18.5.arch1-1 -> 4.18.6.arch1-1)
[2018-09-08 08:03] [ALPM] upgraded linux-headers (4.18.5.arch1-1 -> 4.18.6.arch1-1)
[2018-09-08 08:03] [ALPM] upgraded lynis (2.6.6-1 -> 2.6.8-1)
[2018-09-08 08:03] [ALPM] upgraded nvidia (396.54-2 -> 396.54-3)
[2018-09-08 08:03] [ALPM] upgraded polkit (0.114-1 -> 0.115+3+g8638ec5-1)
[2018-09-08 12:53] [PACMAN] starting full system upgrade
[2018-09-08 12:53] [ALPM] upgraded mesa (18.1.7-1 -> 18.1.8-1)
[2018-09-08 12:53] [ALPM] upgraded lib32-mesa (18.1.7-1 -> 18.1.8-1)
[2018-09-08 12:53] [ALPM] upgraded mesa-vdpau (18.1.7-1 -> 18.1.8-1)
[2018-09-08 14:44] [PACMAN] starting full system upgrade
[2018-09-08 14:44] [ALPM] upgraded tumbler (0.2.1-2 -> 0.2.2-1)
Offline
Can someone give me a hint?
I really need a working graphics tablet.
Offline
Possibly the easiest thing to test would be install linux-lts and see if changing the kernel has any effect.
Offline
Well, today I noticed the same thing as Mr.Smith1974 did...
Offline
Well, today I noticed the same thing as Mr.Smith1974 did...
What have you tried to determine the cause?
Offline
darapsas wrote:Well, today I noticed the same thing as Mr.Smith1974 did...
What have you tried to determine the cause?
Good evening,
as I myself don't have time to try all the solutions on the internet, I have just downgraded the linux kernel and linux headers for now until the bug is going to be fixed on newer versions:
sudo pacman -U /var/cache/pacman/pkg/linux-headers-4.18.3.arch1-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/linux-4.18.3.arch1-1-x86_64.pkg.tar.xz
If this doesn't work, just check the last versions of linux and linux-headers that were installed on your system before upgrading and than modify first command:
ls /var/cache/pacman/pkg | grep linux
After this your g640 tablet should work perfectly fine, at least mine does.
Last edited by darapsas (2018-09-13 18:54:42)
Offline
So the issue is caused by a change between 4.18.3 and 4.18.5 but no one affected will bisect between those kernels to find the cause.
Offline
If I will have some free time on the weekend I will check it out, but for now temporary fix should work.
Offline
Try to use mypaint. IIRC unlike other programs it reads table input directly from kernel. Other programs use input from libinput. I've had pressure bug and libinput was the cause.
Offline
Try to use mypaint. IIRC unlike other programs it reads table input directly from kernel. Other programs use input from libinput. I've had pressure bug and libinput was the cause.
I only use mypaint
And it stopped working
Offline
After upgrade to
[2018-09-14 18:35] [ALPM] upgraded linux (4.18.6.arch1-1 -> 4.18.7.arch1-1)
[2018-09-14 18:35] [ALPM] upgraded linux-headers (4.18.6.arch1-1 -> 4.18.7.arch1-1)
[2018-09-14 17:00] [ALPM] upgraded libinput (1.11.3-1 -> 1.12.0-1)
and reboot the situation has not changed
Offline
I think we should report a bug on kernel.org about this mistake.
Offline
I would suggest checking 4.18.4.arch1-1 that should narrow the search area down to 4.18.3-4.18.4 or 4.18.4-4.18.5 then bisect between those releases to find the causal commit and report that upstream.
You could also check 4.19-rc3 to see if the issue has already been fixed upstream.
Offline
After upgrade to kernel version 4.18.8-arch1-1-ARCH the situation has not changed
Offline
@Mr.Smith1974 what about the requested information from post #13?
Offline
@loqs no, I need the latest stable kernel.
In 4.18.12-arch1 this bug still persists.
Offline
Nothing has changed since upgrading to 4.19.1
Offline
Nothing has changed since upgrading to 4.19.4
Offline
Please don't bump the thread with empty posts. if you want to actively do something about it, follow loqs advice and bisect the kernel to find the offending commit and make a report upstream
Offline