Bug 397775 - Support for CTL-4100WL
Summary: Support for CTL-4100WL
Status: RESOLVED FIXED
Alias: None
Product: wacomtablet
Classification: Plasma
Component: general (show other bugs)
Version: 3.0.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Valerii Malov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-23 07:30 UTC by lylewang.au
Modified: 2019-06-27 16:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lylewang.au 2018-08-23 07:30:58 UTC
Hi, Not sure if this is right place to report this, if not, please let me know and sorry for inconvenience, Thanks.

I'm using Fedora 28 (KDE Plasma desktop) and bought a new Wacom Intuos (model CTL-4100WL), it had some problems:
1) When connected via Bluetooth, touching the pen tip won't trigger mouse click; but while connected via usb, it works
2) "Map to Cursor" and "Map to Screen" in settings seems giving no difference.

Is this model supported ? (It can be recognized tho)

Having these packages installed
-----------------------------------------
Name         : xorg-x11-drv-wacom
Version      : 0.36.1
Release      : 4.fc28

Name         : libwacom
Version      : 0.30
Release      : 1.fc28

Name         : kcm_wacomtablet
Version      : 3.0.0
Release      : 0.6.beta2.fc28
-----------------------------------------

Thanks a lot!
Comment 1 Valerii Malov 2018-08-25 14:02:11 UTC
Generally device support depends on X11 driver support, Tablet KCM is just a GUI to configure the driver. So if device shows up in the KCM, it should be supported.

>When connected via Bluetooth, touching the pen tip won't trigger mouse click; but while connected via usb, it works

1) Can you share lsusb command output when device is connected via bluetooth and via usb?
2) When connected via bluetooth, can you run command "xev -event button", tap with a pen inside a smaller square that appears on the screen, and share the output of the xev command?

>"Map to Cursor" and "Map to Screen" in settings seems giving no difference.

What do you mean? Tablet keeps working in absolute mode when you enable relative mode?
Comment 2 lylewang.au 2018-08-26 23:40:22 UTC
Hi Valeriy Malov :

Thanks a lot for looking into this.

1) I found it was the button-1 (the pen tip) was not configured, so after I configured that it works now, though not sure why it was working without proper config while connected via usb cable.

2) Yes when I chose "Map to Cursor" I was expecting it behaves like a mouse - if I move pen away from pad, then touch the pad again with the pen, the cursor should stay where it was, no matter which point I touch on the pad. But this seems not happening - instead the cursor jumps to the point where relatives to the point I touch on pad.


Last thing, there are 4 extra buttons on the pad that can be customized. Their signals can be picked up in the settings - Input Devices - Joystick, but the "Graphic Tablet" doesn't provide customization options for these (in "Tablet" tab), what is the current best solution for this ?

Many Thanks
Comment 3 Valerii Malov 2018-09-02 16:50:36 UTC
>1) I found it was the button-1 (the pen tip) was not configured, so after I configured that it works now, though not sure why it was working without proper config while connected via usb cable.

This is probably a bug with default configuration. I'm aware of this but haven't really pinned it down yet.

>Yes when I chose "Map to Cursor" I was expecting it behaves like a mouse - if I move pen away from pad, then touch the pad again with the pen, the cursor should stay where it was, no matter which point I touch on the pad. But this seems not happening - instead the cursor jumps to the point where relatives to the point I touch on pad.

Can you please run

$ xsetwacom --list devices

To see the ID of the stylus device of your tablet, then run

$ xsetwacom --get id-of-stylus Mode

and share the output. When you have "Map to Cursor" enabled it should read "Relative", when not "Absolute".

>Last thing, there are 4 extra buttons on the pad that can be customized. Their signals can be picked up in the settings - Input Devices - Joystick, but the "Graphic Tablet" doesn't provide customization options for these (in "Tablet" tab), what is the current best solution for this ?

These buttons should be available in Express Buttons tab. If this tab is missing, then tablet description is probably missing info about buttons.

If you've added the tablet via Tablet Finder tool (did the setting screen warn you about tablet not being detected?), you should run it again and specify number of buttons in the "button mapping" group (if you haven't done this initially).

This shouldn't be necessary in wacomtablet 3.1.0. If you can contact Fedora KDE team to update the package, you can just move to 3.1.0 and delete ~/.config/tabletprofilesrc
Comment 4 lylewang.au 2018-09-05 00:49:31 UTC
Thanks Valeriy.

The pen mode looks correct:
------------------------------------------
[10:29]✱lylew@dhcp-1-58 ~ ▶ xsetwacom --list devices
Wacom Intuos BT S Pad pad               id: 17  type: PAD       
Wacom Intuos BT S Pen stylus            id: 18  type: STYLUS    
[10:29]✱lylew@dhcp-1-58 ~ ▶ xsetwacom --get 18 Mode
Relative
------------------------------------------

I'm not sure if that means it just works the way it is, or could there be anything else to look into ?
The mouse cursor still jumps to a different point when I move the pen in the air (outside area the tablet can detect)


For the additional buttons, I don't see that "Express Buttons" tab. 
I didn't use the tablet finder tool to set it up, I just connect via Bluetooth then it works and I setup in the Settings.

I think it's better way to request an update for this package in the Fedora repo, since it's now using an old beta version.
I filed this to request update, I'll see how it goes when new version available.
https://bugzilla.redhat.com/show_bug.cgi?id=1624665

Thanks again.
Comment 5 Valerii Malov 2018-09-09 15:27:01 UTC
(In reply to lylewang.au from comment #4)
> I'm not sure if that means it just works the way it is, or could there be
> anything else to look into ?
> The mouse cursor still jumps to a different point when I move the pen in the
> air (outside area the tablet can detect)

If it's actually set to relative mode, there's not much the KCM can do. Might be a driver bug or a hardware issue, so it's worth reporting to linuxwacom project.

For my tablet, there is a small distance above the tablet when pen movement isn't registered anymore but it still causes jumps in relative mode. If lift my pen further, relative mode works as intended.

> For the additional buttons, I don't see that "Express Buttons" tab. 
> I didn't use the tablet finder tool to set it up, I just connect via
> Bluetooth then it works and I setup in the Settings.

1) Which device ID does the KCM show in the Select Tablet dropdown list in square brackets?
2) Do you have a ~/.config/tabletdblocalrc file?
Comment 6 lylewang.au 2018-09-17 03:48:03 UTC
Hi, 

>> 1) Which device ID does the KCM show in the Select Tablet dropdown list in square brackets?
It reads "Wacom Intuos BT S P [0377]"

>> 2) Do you have a ~/.config/tabletdblocalrc file?

13:47]✱lylew@dhcp-1-58 .config ▶ cat ~/.config/tabletdblocalrc 
[0377]
layout=unknown
model=unknown
name=Wacom Intuos BT S P
padbuttons=0
statusleds=0
touchring=false
touchstripl=false
touchstripr=false
wheel=false
Comment 7 lylewang.au 2018-09-17 03:54:11 UTC
By the way I updated the kcm package to the latest 3.1.0 via this bz:
https://bugzilla.redhat.com/show_bug.cgi?id=1624665
Still not showing me "Express Buttons" tab. 


" ~/.config/tabletprofilesrc " file  shows [056A:0377]
According to this, https://github.com/linuxwacom/input-wacom/wiki/Device-IDs  , it should be supported and recognized correctly ?
Comment 8 Valerii Malov 2018-09-17 10:23:23 UTC
You want to remove ~/.config/tabletdblocalrc, because it containts manually created description for the tablet, which is missing express buttons ("padbuttons=0"). Manual definitions take priority over everything else just in case if database-provided ones have some kind of error. Unfortunately, this isn't conveyed clearly with the current UI.

After that, reconnect the tablet and it should be detect with proper amount of express buttons. If it still doesn't try restarting wacom tablet daemon or kded.
Comment 9 lylewang.au 2018-09-19 00:43:08 UTC
Hi, Valeriy:

Thanks very much. 
I removed ~/.config/tabletdblocalrc, then on connecting the tablet again it says I needed to add that manually so I click that button it asked me to choose some details including the hardware buttons detection. I finished that and saved, then rebooted.

Then I was able to connect tablet again and it shows me the configuration GUI now it has "Express Buttons" tab, was able to define keyboard shortcut for these buttons.

Only small problem is, two of buttons seem not mapping correctly (the 2 buttons in the middle got wrong), but after I tweak the tabletdblocalrc file manually it is working as expected now.


This leaves only the cursor jumping problem in relative mode which I believe is a driver issue. I think I'm able to live with that (not very convenient but not a big issue when I get used to it...)

Again, Thanks very much!
Comment 10 Valerii Malov 2019-06-27 16:47:47 UTC
Git commit a431056224a4e610cfad763cc9ea92d0dc8aff4a by Valerii Malov.
Committed on 27/06/2019 at 16:45.
Pushed by valeriymalov into branch 'master'.

Add mapping for Wacom Intuos BT S (bluetooth)

Based on https://github.com/linuxwacom/input-wacom/wiki/Device-IDs wacom 0376 and wacom 0377 are the same device

M  +14   -0    data/wacom_devicelist

https://commits.kde.org/wacomtablet/a431056224a4e610cfad763cc9ea92d0dc8aff4a