Help wanted: Eraser is not working after a driver update

[itcultus]

My current setup is: openSUSE Tumbleweed, XP Pen Artist 12, latest XP Pen linux drivers, Gromit 16, using X, of course.

Obviously the new XP Pen drivers changed a lot of things in the background because right now I have a non-working setup.
Specifically, the only pens that work are the red and the green arrow (see the configuration file bellow).
Shortcuts for clear screen, undo, on-off are working.

But, neither the blue/yellow pen work, nor the eraser. The eraser is the most important one because I need it, obviously. Any help would appreciated.

My current configuration is this:

"red Pen" = PEN (size=4 color="red");
"blue Pen" = "red Pen" (color="#4682B4");
"yellow Pen" = "red Pen" (color="#FE8B1B");
"green Marker" = PEN (size=5 color="green" arrowsize=2);

"Eraser" = ERASER (size = 80);

"XP-Pen Pen" = "red Pen";
"XP-Pen Eraser Eraser (0)" = "Eraser";

"default" = "red Pen";
"default"[SHIFT] = "blue Pen";
"default"[CONTROL] = "green Marker";
"default"[META] = "yellow Pen";
"default"[Button3] = "Eraser";

And XInput is this:

 Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Logitech MX Master                        id=12   [slave  pointer  (2)]
⎜   ↳ XP-Pen Mouse                              id=17   [slave  pointer  (2)]
⎜   ↳ XP-Pen Pen Pen (0)                        id=22   [slave  pointer  (2)]
⎜   ↳ XP-Pen Eraser Eraser (0)                  id=23   [slave  pointer  (2)]
⎜   ↳ Microsoft Natural® Ergonomic Keyboard 4000        id=9    [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)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Logitech Logitech Wireless Headset Consumer Control       id=11   [slave  keyboard (3)]
    ↳ Logitech MX Master                        id=14   [slave  keyboard (3)]
    ↳ XP-Pen Pen                                id=15   [slave  keyboard (3)]
    ↳ XP-Pen Eraser                             id=16   [slave  keyboard (3)]
    ↳ XP-Pen Mouse                              id=18   [slave  keyboard (3)]

I also tried to use the Keyboard (XP-Pen Eraser) but I still can't get the eraser to work.

Any ideas?

[bk138]

I suggest reverting the driver update and look and the xinput output for this case. Also, asking at their side is maybe also an approach... Sorry, no better ideas.

[itcultus]

I will first check on my laptop which has the older version of the driver. What I suspect is that the eraser is having a new "button" assigned to it. Because as you can see in the output, I use the names as given by xinput.

[itcultus]

OK, I have some news. And those news are these: No matter what I do, the eraser is NOT working. It acts as a stylus tip, not eraser. libinput debug-events --device /dev/input/event23 shows that the eraser is pressed, or released. For example:

event23  TABLET_TOOL_PROXIMITY       +1.374s           234.22/51.35    tilt: -1.00/-1.00       pressure: 0.00  eraser   (0, id 0) proximity-out

But it's not recognized as a mouse button. Even if I set the stylus button to "right click", it's not working. Using my mouse, it works just fine.

Anyway, we will see later how we can fix this. Off-topic question: If I want to configure the "auto-shapes" do I need to replace one or more pen colors? Or is there a way to have colors and "auto-shapes"?

[bk138]

Anyway, we will see later how we can fix this. Off-topic question: If I want to configure the "auto-shapes" do I need to replace one or more pen colors? Or is there a way to have colors and "auto-shapes"?

I don't know about auto-shapes, but any tool in the config can be coloured with one colour.

[bk138]

Closing as this seems to be a driver setup issue and is not actioanable from Gromit-MPX side...