Wacom tablet on Wayland

I recently upgraded to F40. I usually use KDE/Plasma because some things didn’t work under Gnome - like my Wacom tablet.

Since upgrading to F40 the tablet has been acting up under KDE. The pointer is trapped on one monitor, input isn’t read, and the virtual keyboard pops up without warning. So I tried Gnome.

The tablet works under Gnome Classic and Gnome on Xorg but not Gnome on Wayland making it looks like the problem is Wayland.

Are there any fixes to get the tablet to work under Wayland or should I just switch to Gnome classic until the next release?

Do you have Linux drivers installed for your specific tablet? Can you post the model of your Wacom ?

If you run into trouble there are some pretty reliable drivers for Wacom (specifically)

Unlike my HUION KAMVAS 16 Pro

I thought the drivers had been added to the Linux system a few years back. It worked fine from F29-F39…. A GitHub article I found earlier seemed to say the Wacom drivers were dependent on Xorg and did not function under Wayland. I’ll look at it again later.

The tablet is an old Bamboo Fun, 6x8, with stylus and buttons.

1 Like

If your Wacom works under X11 flawlessly, I think you’ll need to stick to that since you are on KDE.
I don’t use KDE, but I think they jjust went Wayland for F40. So you would need to get X11 to work under Plasma6. Maybe someone from the kde SIG can come in and give some advice.

I’ll dig up some information for you in hopes to get that fixed for you and other creators. It’s a big deal IMO.

I’ve had so much trouble with my HUION KAMVAS on Wayland, I basically abandoned a 16" Tablet :laughing:

1 Like

Thanks. I can use Gnome on Xorg for now. Getting the current KDE to work on Xorg seems like more than I want to deal with. My program seems to work with the current release (it didn’t on earlier ones).

1 Like

Sorry about that, I’m not a KDE user, and have only seen here on the forums that there are packages that need to be installed. As for Gnome, if you can use Gnome Classic, or Gnome on Xorg to get by, that might be the best solution.

This is a big issue with Wayland and moves to other forms of OS as well. Creators are always the last in line.

In another thread it was suggested I add “plasma-workspace-x11”. I added it through dnfdragora and rebooted. I then had an option for using Plasma on Xorg at login. Wacom tablet now works, mouse slowness is gone, and kcalc again accepts keyboard input.

1 Like

Thanks for that, I’m sure this information will help many KDE users.

I installed updates yesterday - plasma-workspace-x11 was removed. I tried re-installing - error is:

Problem: conflicting requests

  • nothing provides plasma-workspace = 6.0.5 needed by plasma-workspace-x11-6.0.5-1.fc40.x86_64 from updates

Plasma is being weird, tablet is being weird, hopefully Gnome works better

Thank you for updating this thread with your experience. If you are going to try Gnome, please test it on Wayland, but I believe the best use case will still be X11.

I will look into testing my Huion KAMVAS 16 PRO soon as well.

I tried Gnome on Wayland Gnome Classic on Wayland, and Gnome on Xorg. My “test” was whether my program & tablet (both) worked - Wayland failed. It didn’t read input from the stylus in the program I use. Gnome on Xorg seems to be working.

I thought Wayland was supposed to be better than Xorg

1 Like

Could you tell me what program that is if possible ? I could include it in my upcoming test. I typically use Inkscape, GIMP, Krita, Blender and Pinta (rarely now. . . )

I checked Stitchmastery which is based on/in Eclipse. I’ll try a few of the others and report

1 Like

As much as I like GNOME, the pressure sensitivity is all wrong on GNOME Wayland and there’s no way to change it (way too soft). Pressure sensitivity can’t be changed on KDE Wayland either (though it’s coming) but by default it’s more usable, despite not being quite right in the opposite direction.

Not for artists. My use case isn’t serious enough to go back to X11, but most artists would be better served by it at this point in time.

If you want more graphics tablet options and color management, X11 is a better option for now. Color management might be standardized and added to Wayland compositors by Fedora 41 (though I doubt it) but at that point Fedora Workstation is on track to get rid of their X11 session too by default.

okay. I did some testing - very cursory testing using Plasma, Gnome on Wayland, Gnome Classic, and Gnome on Xorg

GIMP worked on all of them
Blender worked on all of them

Scribus took a long time to load a file under Plasma, Grome on Wayland, and Gnome Classic. On Plasma I got a message saying “Crashed due to Signal #11” Then it seemed to be okay. The program and files seemed to load faster under Gnome on Xorg -or maybe I’d just loaded the file before.

Inkscape had a fatal crash under Plasma, Gnome on Wayland, and Gnome Classic. The same error has been reported under Win11. It loaded and worked fine on Gnome on Xorg.

Stitchmastery works under Gnome on Xorg, otherwise it doesn’t accept input and gives repeated messages about “not rseesponding wait or cancel”.

otherwise: When first loading Plasma the mouse is non-responsive. It gradually “warms up” then seems okay. The stylus cursor gets trapped on a screen (I have a dual monitor setup). If I move the cursor to the secondary screen, I can’t get it back to the primary screen without using the mouse. Gnome (all versions I tried) doesn’t exhibit either of these issues.

hope this helps
otherw

1 Like

This is incredible work :ballot_box_with_check: and invaluable information :handshake:t5: :fedora:

At the moment I used this the most, so I’m going to do some testing in it. I also have a thread with optimizations for the application and how some thngs might help you as well :

Maybe some of those settings can help you as well. I am on Gnome/Wayland btw, but can test them all.

When you get a moment can you share if possible the output of inxi -Fzxx here as reference and to guage expectations ?

the output is:

System:
  Kernel: 6.8.11-300.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.2 tk: GTK v: 3.24.42 wm: gnome-shell dm: SDDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Server System: Supermicro product: Super Server v: 0123456789
    serial: <superuser required> Chassis: type: 17 v: 0123456789
    serial: <superuser required>
  Mobo: Supermicro model: X11SAT-F v: 1.01 serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 1.0a date: 04/29/2016
CPU:
  Info: quad core model: Intel Xeon E3-1225 v5 bits: 64 type: MCP
    arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 875 high: 900 min/max: 800/3700 cores: 1: 800 2: 900
    3: 900 4: 900 bogomips: 26399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: ZOTAC driver: nvidia
    v: 550.78 arch: Maxwell pcie: speed: 2.5 GT/s lanes: 16 ports: active: none
    off: DVI-D-1,DVI-I-1 empty: DP-1,HDMI-A-1 bus-ID: 04:00.0
    chip-ID: 10de:1402
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 24.1.0
    compositor: gnome-shell driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,vesa alternate: nouveau,nv
    gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3200x1080 s-dpi: 96
  Monitor-1: DVI-D-1 mapped: DVI-D-0 note: disabled pos: primary,left
    model: Acer X233H res: 1920x1080 dpi: 96 diag: 585mm (23")
  Monitor-2: DVI-I-1 mapped: DVI-I-0 note: disabled pos: right
    model: Samsung SyncMaster res: 1280x1024 dpi: 86 diag: 482mm (19")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 950/PCIe/SSE2
  API: Vulkan v: 1.3.283 surfaces: xcb,xlib device: 0 type: discrete-gpu
    driver: N/A device-ID: 10de:1402 device: 1 type: cpu driver: N/A
    device-ID: 10005:0000
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Super Micro
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
  Device-2: NVIDIA GM206 High Definition Audio vendor: ZOTAC
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 04:00.1 chip-ID: 10de:0fba
  Device-3: Blue Microphones Snowflake driver: snd-usb-audio type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-13:7 chip-ID: b58e:f5a5
  API: ALSA v: k6.8.11-300.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Ethernet I219-LM vendor: Super Micro driver: e1000e
    v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b7
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I210 Gigabit Network vendor: Super Micro driver: N/A pcie:
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0 chip-ID: 8086:1533
  Device-3: Realtek RTL8188EUS 802.11n Wireless Network Adapter driver: N/A
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-11:5
    chip-ID: 0bda:8179
  IF-ID-1: virbr0 state: down mac: <filter>
Drives:
  Local Storage: total: 989.18 GiB used: 207.46 GiB (21.0%)
  ID-1: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-2: /dev/sdb model: USB DISK 2.0 size: 57.67 GiB type: USB rev: 2.0
    spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 68.35 GiB used: 41.58 GiB (60.8%) fs: ext4 dev: /dev/dm-0
    mapped: fedora_localhost--live-root
  ID-2: /boot size: 973.4 MiB used: 586.4 MiB (60.2%) fs: ext4
    dev: /dev/sda1
  ID-3: /home size: 838.24 GiB used: 114.76 GiB (13.7%) fs: ext4
    dev: /dev/dm-2 mapped: fedora_localhost--live-home
Swap:
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-1 mapped: fedora_localhost--live-swap
  ID-2: swap-2 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  Src: ipmi Permissions: Unable to run ipmi sensors. Root privileges required.
  Src: lm-sensors System Temperatures: cpu: 29.2 C pch: 31.0 C mobo: N/A
    gpu: nvidia temp: 28 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 37%
Info:
  Memory: total: 16 GiB note: est. available: 15.43 GiB used: 4.26 GiB (27.6%)
  Processes: 822 Power: uptime: 2h 1m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: pm: flatpak pkgs: 2 Compilers: clang: 18.1.6 gcc: 14.1.1
    Shell: Bash v: 5.2.26 running-in: gnome-terminal inxi: 3.3.34
1 Like

I just dusted off the ol’ HUION KAMVAS 16 PRO, and it was an interesting experience. I guess to start would be Inkscape crashing twice, being fine since :thinking: Very strange. Right now Inkscape works smoothly, all under Wayland.

Here is a picture of the Tablet and my Laptop :

I think the cabling is excessive, but it is what is is. Today I tested RNote https://rnote.flxzt.net/ :

It was a delightful experience to have. Notes were pretty seamless but I miss the tips on what the icons do :thinking: Overall, as a note taking, doodling application it’s pretty, clean UI, and swift to use.

Inkscape seems to crash after the device is unplugged, So to get back into Inkscape it requires a restart or a logout of the current session.

Well, this has gotten worse. Now, if the device is connected before Inkscape is launched, I crash and Inkscape fails to start. There is a bug filed for this. The workaround is to start Inkscape, then connect the tablet.

Added design