Integrated Lenovo Yoga pen: button assignments wrong following update 2025-09-26

After this update, on my Lenovo X13 Yoga the pen buttons are different and partly not working now.
So the lower button on the pen is now non functional and the upper button is now suddenly registered as button 1.
I’ve had problems with this in the past, but they resolved themself if I remember correctly.
Should I create a new post about this or maybe somebody knows about this problem and can help me out?

This wasn’t my highes quality post, so let me introduce some information:

Lenovo ThinkPad Yoga X13 Gen 4
The pen in question is the integrated lenovo pen.

Here is my inxi -zv8

> inxi -zv8
System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.12-x86_64
    root=UUID=a46e20e3-0afc-49b5-9200-1e62e08cbc01 rw rootflags=subvol=@
    loglevel=3 systemd.show_status=1
    resume=UUID=6c9e9761-e2fd-4cdd-bdf1-def6241b42c9 udev.log_priority=3
    nmi_watchdog=0 nowatchdog modprobe.blacklist=i2c_i801
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.18.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Convertible System: LENOVO product: 21F2CTO1WW
    v: ThinkPad X13 Yoga Gen 4 serial: <superuser required> Chassis: type: 31
    serial: <superuser required>
  Mobo: LENOVO model: 21F2CTO1WW serial: <superuser required>
    part-nu: LENOVO_MT_21F2_BU_Think_FM_ThinkPad X13 Yoga Gen 4
    uuid: <superuser required> UEFI: LENOVO v: N3OET38W (1.21 )
    date: 06/24/2025
Battery:
  ID-1: BAT0 charge: 46.7 Wh (99.5%) condition: 47/54.7 Wh (85.8%)
    volts: 17.42 min: 15.48 model: BYD 5B11H56369 type: Li-poly serial: <filter>
    charging: status: not charging control: start: 0% end: 100% cycles: 198
  Device-1: wacom_battery_0 model: Wacom HID 5354 serial: N/A charge: 50%
    status: N/A
Memory:
  System RAM: total: 32 GiB available: 31.02 GiB used: 4.68 GiB (15.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 8 modules: 8 EC: None
    max-module-size: 4 GiB note: est.
  Device-1: Controller0-ChannelA type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
  Device-2: Controller0-ChannelB type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
  Device-3: Controller0-ChannelC type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
  Device-4: Controller0-ChannelD type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
  Device-5: Controller1-ChannelA type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
  Device-6: Controller1-ChannelB type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
  Device-7: Controller1-ChannelC type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
  Device-8: Controller1-ChannelD type: LPDDR5 detail: synchronous
    size: 4 GiB speed: spec: 6400 MT/s actual: 4800 MT/s volts: curr: 0.5
    width (bits): data: 16 total: 16 manufacturer: Samsung
    part-no: K3KL9L90CM-MGCT serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 13th Gen Intel Core i5-1335U bits: 64 type: MST AMCP
    arch: Raptor Lake level: v3 note: check built: 2022+ process: Intel 7 (10nm)
    family: 6 model-id: 0xBA (186) stepping: 3 microcode: 0x4129
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 10 threads: 12 mt: 2 tpc: 2
    st: 8 smt: enabled cache: L1: 928 KiB desc: d-8x32 KiB, 2x48 KiB; i-2x32
    KiB, 8x64 KiB L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB
    desc: 1x12 MiB
  Speed (MHz): avg: 691 min/max: 400/4600:3400 scaling: driver: intel_pstate
    governor: powersave cores: 1: 691 2: 691 3: 691 4: 691 5: 691 6: 691 7: 691
    8: 691 9: 691 10: 691 11: 691 12: 691 bogomips: 59916
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts epb erms est f16c flush_l1d fma fpu fsgsbase
    fsrm fxsr gfni hfi ht hwp hwp_act_window hwp_epp hwp_notify hwp_pkg_req
    ibpb ibrs ibrs_enhanced ibt ida intel_pt invpcid lahf_lm lm mca mce
    md_clear mmx monitor movbe movdir64b movdiri msr mtrr nonstop_tsc nopl nx
    ospke pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pku pln pni popcnt
    pse pse36 pts rdpid rdrand rdseed rdtscp rep_good sdbg sep serialize
    sha_ni smap smep smx split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2
    ssse3 stibp syscall tm tm2 tsc tsc_adjust tsc_deadline_timer
    tsc_known_freq umip user_shstk vaes vme vpclmulqdq waitpkg x2apic xgetbv1
    xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
    conditional; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Lenovo driver: i915
    v: kernel alternate: xe arch: Xe process: Intel 7 (10nm) built: 2022+ ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:a7a1 class-ID: 0300
  Device-2: Syntek Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4:5 chip-ID: 174f:11a8
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0b86 built: 2022 res:
    mode: 1920x1200 hz: 60 scale: 100% (1) dpi: 171 gamma: 1.2 chroma: red:
    x: 0.655 y: 0.322 green: x: 0.298 y: 0.600 blue: x: 0.141 y: 0.063 white:
    x: 0.325 y: 0.345 size: 286x179mm (11.26x7.05") diag: 337mm (13.3")
    ratio: 16:10 modes: 1920x1200
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.2.3-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Xe Graphics (RPL-U)
    device-ID: 8086:a7a1 memory: 30.29 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.321 layers: 5 device: 0 type: integrated-gpu name: Intel
    Iris Xe Graphics (RPL-U) driver: mesa intel v: 25.2.3-arch1.2
    device-ID: 8086:a7a1 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Raptor Lake-P/U/H cAVS vendor: Lenovo
    driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel, snd_soc_avs,
    snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51ca class-ID: 0403
  API: ALSA v: k6.12.48-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:51f1 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: wwp0s20f0u2 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:6 chip-ID: 8087:0033
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 3 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 476.94 GiB used: 56.74 GiB (11.9%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD PC
    SN740 SDDQNQD-512G-1201 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 73117101 temp: 32.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 100 GiB size: 100 GiB (100.00%) used: 22.62 GiB (22.6%)
    fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3 label: Root
    uuid: a46e20e3-0afc-49b5-9200-1e62e08cbc01
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 704 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: EFI
    uuid: 78B1-C149
  ID-3: /home raw-size: 343.44 GiB size: 343.44 GiB (100.00%)
    used: 34.12 GiB (9.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: Home uuid: 17b374a9-bf64-40b4-a327-0274e0018dff
  ID-4: /var/cache raw-size: 100 GiB size: 100 GiB (100.00%)
    used: 22.62 GiB (22.6%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
    label: Root uuid: a46e20e3-0afc-49b5-9200-1e62e08cbc01
  ID-5: /var/log raw-size: 100 GiB size: 100 GiB (100.00%)
    used: 22.62 GiB (22.6%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
    label: Root uuid: a46e20e3-0afc-49b5-9200-1e62e08cbc01
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 33.2 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p4 maj-min: 259:4 label: Linuxswap
    uuid: 6c9e9761-e2fd-4cdd-bdf1-def6241b42c9
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 2-0:1 info: super-speed hub ports: 3 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: Logitech USB Receiver type: mouse,keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 98mA chip-ID: 046d:c547 class-ID: 0300
  Device-2: 3-2:3 info: Quectel Wireless Solutions EM05-G
    type: communication,CDC-data driver: cdc_mbim,option,option1 interfaces: 3
    rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 2c7c:030a class-ID: 0a00
  Device-3: 3-3:4 info: Shenzhen Goodix USB2.0 MISC type: <vendor specific>
    driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 27c6:6594 class-ID: ef00 serial: <filter>
  Device-4: 3-4:5 info: Syntek Integrated Camera type: video
    driver: uvcvideo interfaces: 5 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 174f:11a8 class-ID: fe01
    serial: <filter>
  Device-5: 3-10:6 info: Intel AX211 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0033 class-ID: e001
  Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (rpm): fan-1: 3766
Repos:
  Packages: pm: pacman pkgs: 1506 libs: 392 tools: pamac,paru pm: flatpak
    pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    2: https://mirror.komelt.dev/manjaro/stable/$repo/$arch
    3: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    4: https://manjaro.syxpi.fr/manjaro/stable/$repo/$arch
    5: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    6: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    7: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
    8: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 367
  1: cpu: 14.6% command: zen-bin pid: 2905 mem: 497.6 MiB (1.5%)
  2: cpu: 9.9% command: zen-bin pid: 3535 mem: 340.7 MiB (1.0%)
  3: cpu: 9.2% command: kwin_wayland pid: 1687 mem: 245.8 MiB (0.7%)
  4: cpu: 6.1% command: rnote pid: 3878 mem: 974.1 MiB (3.0%)
  5: cpu: 1.7% command: plasmashell pid: 1952 mem: 343.4 MiB (1.0%)
  Memory top: 5 of 367
  1: mem: 974.1 MiB (3.0%) command: rnote pid: 3878 cpu: 6.1%
  2: mem: 497.6 MiB (1.5%) command: zen-bin pid: 2905 cpu: 14.6%
  3: mem: 343.4 MiB (1.0%) command: plasmashell pid: 1952 cpu: 1.7%
  4: mem: 340.7 MiB (1.0%) command: zen-bin pid: 3535 cpu: 9.9%
  5: mem: 310.1 MiB (0.9%) command: zen-bin pid: 3587 cpu: 1.2%
Info:
  Processes: 367 Power: uptime: 11m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 12.39 GiB services: org_kde_powerdevil,upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.39

also this is the pen part of libinput list-devices

Device:                  Wacom HID 5354 Pen
Kernel:                  /dev/input/event18
Id:                      i2c:056a:5354
Group:                   7
Seat:                    seat0, default
Size:                    286x179mm
Capabilities:            tablet 
Tap-to-click:            n/a
Tap-and-drag:            n/a
Tap button map:          n/a
Tap drag lock:           n/a
Left-handed:             disabled
Nat.scrolling:           n/a
Middle emulation:        n/a
Calibration:             identity matrix
Scroll methods:          none
Scroll button:           n/a
Scroll button lock:      n/a
Click methods:           none
Clickfinger button map:  n/a
Disable-w-typing:        n/a
Disable-w-trackpointing: n/a
Accel profiles:          none
Rotation:                n/a
Area rectangle:          n/a

and another information, that might be useful in helping me?

> sudo libwacom-list-local-devices
/dev/input/event18 is a tablet but not supported by libwacom
Failed to find any devices known to libwacom.

I don’t know if it ever was supported by libwacom

I think this is a good idea; I’ve done the honours and split this from the Update thread. I have no experience with these pens myself, but this separate thread will hopefully get more attention from those who do. :wink:

1 Like

This update is 2025-09-30. But what version did you update from? Was it from 2025-08-29 or from some older version?

Another question, is the device recognized as ‘Drawing Tablet’ in Plasma’s system settings?

> cat /var/log/pacman.log | grep -i "starting full system upgrade"
....
[2025-09-14T15:50:38+0200] [PACMAN] starting full system upgrade
[2025-09-24T13:00:34+0200] [PACMAN] starting full system upgrade
[2025-09-24T13:04:31+0200] [PACMAN] starting full system upgrade
[2025-09-30T10:49:01+0200] [PACMAN] starting full system upgrade

This would be my updates @jofi. Sorry for answering so late, I only got the e-mail now.

I’m not sure, how to answer the second question….
I have a “Drawing Tablet” section in my settings. And the pen settings for my pen is also inside there.

The reason for my question was you need to know what changed (at least it could help), and you can’t know this only giving the current state. The log doesn’t help to find out. The list of stable updates shows you can’t have 4 consecutive real full system updates during September, since there was only a single stable update for September. (There may be fast tracked updates like security or web browsers but they don’t matter for this.)

The other question was about getting a clue of how the pen is supposed to work since you wrote

So to ask directly, do you know by what it is supported? I think wacom would be for a pen activated when close to the screen. But perhaps your pen connects via bluetooth?

1 Like

Thanks for your help

I’d say, it’s definitely not an older update but very recent. I usually hold my system very up to date and only post on posts where I really think the problem is from. So let’s assume, this is the case and the mentioned update (2025-09-26) created the issue.

It’s not a bluetooth pen but one activated when close to the screen, so most likely libwacom is the driver for the pen.

Just a wild guess since it is on the changes list - do you have the package udev-hid-bpf installed?

Nope

> paru -Q | rg udev
libgudev 238-3
udev-usb-sync 1.0-1

I can’t find anything in the full list of changes like wacom or hid. Can it be as deep as in linux firmware changes?

Just a thought - you could install the package and check whether the pen is listed

udev-hid-bpf list-devices

see https://libevdev.pages.freedesktop.org/udev-hid-bpf/tutorial.html

> udev-hid-bpf list-devices
devices:
  -  syspath:      "/sys/bus/hid/devices/0018:04F3:3209.0001"
     name:         "ELAN06C4:00 04F3:3209"
     device entry: "HID_DEVICE(BUS_I2C, HID_GROUP_MULTITOUCH_WIN_8, 0x04F3, 0x3209)"
  -  syspath:      "/sys/bus/hid/devices/001F:8087:0AC2.0003"
     name:         "hid-ishtp 8087:0AC2"
     device entry: "HID_DEVICE(BUS_INTEL_ISHTP, HID_GROUP_SENSOR_HUB, 0x8087, 0x0AC2)"
  -  syspath:      "/sys/bus/hid/devices/0018:056A:5354.0002"
     name:         "WACF2200:00 056A:5354"
     device entry: "HID_DEVICE(BUS_I2C, HID_GROUP_WACOM, 0x056A, 0x5354)"
  -  syspath:      "/sys/bus/hid/devices/001F:8087:0AC2.0004"
     name:         "hid-ishtp 8087:0AC2"
     device entry: "HID_DEVICE(BUS_INTEL_ISHTP, HID_GROUP_SENSOR_HUB, 0x8087, 0x0AC2)"

So I guess, yes?

Alright! So I’ve done some work. Booted into the BTRFS snapshot from the 29th of September.
Everything works fine. But I checked the settings and the settings still look wrong again eventhough functionality is correct. So apparently the settings always were borked but my problem was in rnote → On the btrfs snapshot, it works fine; on my manjaro now it doesn’t.
I updated the program on my snapshot, and it doesn’t work again.
So, thanks for trying @jofi , but appereantly while updating, rnote also got an update and, well, that broke the functionality I was expecting.

I will go to the programs developers.
Thank you all.

After checking the github of the programm, it was a fix of 30 seconds…

Under the pitfalls and known issues section of the program:



One of the stylus buttons shortcut mapping does not work as intended -
On some devices one stylus button is mapped to a dedicated "Eraser" mode (which is the back-side on other styli). The buttons in the shortcuts settings could then be inconsistent ( the secondary / upper button is actually the primary / lower button , or reverse ). To change the tool that is mapped to this "Eraser" mode, do the following:

    - Hover over the canvas, and press and hold the button that is suspected to be mapped to the "Eraser" mode
    - Switch to the desired pen style while keeping the button pressed
    - When releasing the pressed button, it should switch back to the previous pen style
    - The pen style in the "Eraser" mode should now be remembered


3 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.