Incorrect configuration for udev and xorg for wizardpen tablets.

Bug #576610 reported by negora
48
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Wizardpen
Undecided
Unassigned

Bug Description

I don't know where to start from... I've Ubuntu 10.04 (Lucid Lynx), the 64-bit edition, and a Manhattan Graphics Tablet whose device ID is 5543:0005 and its internal name is "UC-LOGIC Tablet WP8060U". Some times with more difficulty than others, I was able to make it work in the past. The easiest time was with Ubuntu 9.10 (Karmic Koala). However I'm facing serious problems in the last version from Canonical.

I've tried both ways, installing the last package from the DoctorMo repositories and also compiling the sources from LaunchPad by myself. No luck with any of them.

What's the problem in a few words? The pen is perfectly recognized and I can move the pointer over any place on the screen. However, once that I press the tip for first time, it's like if the pointer got stuck and I needed to continue pressing the pointer to move it.

I've checked the logs from /var/log/Xorg.0.log and in one line it says:

(**) UC-LOGIC Tablet WP8060U: Applying InputClass "evdev pointer catchall"

I've seen in the logs from people who have successfully installed their tablets that there are 3 lines like this, being this the first one, and another one assigning the InputClass "wizardpen" the last one. I lack of that last line, which makes me think that the X server doesn't parse the 70-wizardpen.conf right. Or maybe it does it right but my tablet doesn't match its rules (what would be weird as it's just a simple WP8060U tablet and is perfectly set in the udev and HAL rules).

Another interesting test which I did was to edit /etc/X11/xorg.conf, which always seemed to work for me in the past, except when the X server started to rely on the HAL rules (FDI files). I added something like this:

Section "InputDevice"
    Identifier "Tablet0"
    Driver "wizardpen"
    Option "Device" "/dev/input/event6"
    Option "TopX" "2650"
    Option "TopY" "3563"
    Option "TopZ" "10
    Option "BottomX" "30733"
    Option "BottomY" "29715"
    Option "BottomZ" "511"
EndSection

Result? ALMOST DONE! I could move the pen like before and when I pressed the tip I still was able to move it without pushing it again. What's wrong then? The fact that the pen seems to send 2 events to the X server when a button is pressed, like if 2 of them were pressed at the same time.

For example, if I click on a page while I'm using Firefox, apart of doing the actual click, it also turns me back to the past page in the history. I could confirm this executing "xev" and checking which kind of events it triggered, resulting in:

Tip => It triggers key codes 1 & 8 .
Button A => It triggers key codes 2 & 9 .
Button B => It triggers key codes 3 & 10 .

This means that when pressing a button, it causes 2 different actions. I tried to use xinput to alter this behaviour with no luck.

So, summarizing a lot, I get 2 different behaviours depending on if I edit /etc/X11/xorg.conf or not. And, by the way, if I don't edit this file, no mention to the driver "wizardpen" appears in the logs of X. Although it's not assigned to the tablet, at least it's mentioned as loaded.

By the way, I never got a soft link called /dev/tablet-event , that's why I had to use /dev/input/event6 instead.

Related branches

Revision history for this message
negora (negora) wrote :
Revision history for this message
negora (negora) wrote :

Here it's the other log...

Revision history for this message
negora (negora) wrote :

My problem seems to be equal to the bug 573191 which I hadn't seen when I reported mine. I'm not sure if the origins are the same, since the tablet models are different. But the symptoms are very similar.

Revision history for this message
Irishbandit (irishbandit) wrote :

Try deleting the edits you made in /etc/X11/xorg.conf
and add them to /lib/X11/xorg.conf.d/70-wizardpen.conf
Like so:

Section "InputClass"
   Identifier "wizardpen"
   MatchIsTablet "on"
   MatchDevicePath "/dev/input/event*"
   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   Driver "wizardpen"
   Option "TopX" "826"
   Option "TopY" "2626"
   Option "BottomX" "32747"
   Option "BottomY" "32762"
   Option "TopZ" "10"
   Option "BottomZ" "1023"
EndSection
Section "InputClass"
   Identifier "wizardpen ignore mouse dev"
   MatchIsTablet "on"
   MatchDevicePath "/dev/input/mouse*"
   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   Driver ""
EndSection

See what you get. You an idea.

Revision history for this message
negora (negora) wrote :

Hello IrishBandit. When I did all the tests, I tried exactly something like that too, but it didn't work :/ .

Revision history for this message
Irishbandit (irishbandit) wrote :

What is the output from or the contents fo each of the following files?
cat /lib/udev/rules.d/67-xorg-wizardpen.rules
cat /usr/lib/X11/xorg.conf.d/70-wizardpen.conf
cat /etc/udev/rules.d/70-xorg-wizardpen-settings.rules
cat /etc/X11/xorg.conf

do you have the following installed?
xutils libx11-dev libxext-dev x-dev build-essential xautomation xinput xserver-xorg-dev

What are the contents of directories?
/etc/X11/xorg.conf.d/
/usr/share/X11/xorg.conf.d/
/usr/lib/X11/xorg.conf.d

Finaly what do you get from
xinput list
and
xinput get-button-map "your tablet name from above command"

Revision history for this message
negora (negora) wrote :

Hello:

I've attached a file with the output from the command "cat". In /etc/X11/xorg.conf I've commented the device corresponding to the tablet in order to start X as it would do usually when I hadn't altered anything.

Among the mentioned packs, I do have installed: xutils build-essential xautomation xinput . Those with the "-dev" suffix were uninstalled because they're packs of headers which I only needed when I compiled the driver by myself. I guess they're not necessary any longer. Right? I keep "build-essential" because I compile a few things from time to time.

Finally, about the specified directories, only /usr/lib/X11/xorg.conf.d exists. The other 2 are missing. The content of the first one is:

-rw-r--r-- 1 root root 946 2010-03-31 08:29 05-evdev.conf
-rw-r--r-- 1 root root 946 2010-03-31 08:29 05-evdev.conf~20100510
-rw-r--r-- 1 root root 766 2010-04-15 23:37 10-synaptics.conf
-rw-r--r-- 1 root root 139 2010-04-22 17:14 10-vmmouse.conf
-rw-r--r-- 1 root root 480 2010-04-22 22:59 10-wacom.conf
-rw-r--r-- 1 root root 382 2010-04-16 08:13 70-wizardpen.conf
-rw-r--r-- 1 root root 382 2010-04-16 08:13 70-wizardpen.conf~20100510

Files whose name ends with ~ plus a date are just backups of the original ones. Both, original and backup, has the same content, as I restored it before writing this answer.

Since I started my tests, I've tried to edit:

/lib/udev/rules.d/67-xorg-wizardpen.rules
/usr/lib/X11/xorg.conf.d/70-wizardpen.conf
/etc/X11/xorg.conf

All them edited in very different ways. However the only modification which has almost worked has been editing the last one. I also tried the configuration mentioned in the thread http://ubuntu-ky.ubuntuforums.org/showthread.php?t=1475433 ,
 which you recommended to read... But no luck either.

Apart of all this, there are 2 issues which I can't understand:

1 - I've edited by hand /usr/lib/X11/xorg.conf.d/05-evdev.rules and added the lines corresponding to the Wizardpen tablet there. Just to make sure that 70-wizardpen.conf wasn't being ignored by X. No effect however. I've restored it.

2 - /var/log/Xorg.0.log still misses any mention to the wizardpen driver (except when mentioned explicitly at /etc/X11/xorg.conf ). Such driver is compiled and placed in the right directory:

/usr/lib/xorg/modules/input/wizardpen_drv.la
/usr/lib/xorg/modules/input/wizardpen_drv.so

No idea either.

Revision history for this message
negora (negora) wrote :

Ops, I forgot to add the output of the last commands, sorry.

xinput list:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB-PS/2 Optical Mouse id=8 [slave pointer (2)]
⎜ ↳ Logitech Logitech USB Keyboard id=10 [slave pointer (2)]
⎜ ↳ UC-LOGIC Tablet WP8060U id=11 [slave pointer (2)]
⎜ ↳ Macintosh mouse button emulation id=12 [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)]
    ↳ Logitech Logitech USB Keyboard id=9 [slave keyboard (3)]

xinput get-button-map "your tablet name from above command":

1 2 3 4 5 6 7 8 9 10 11 12 13 14

If my memory serves me right, this output is the same regardless I add the tablet definition into /etc/X11/xorg.conf .

Revision history for this message
negora (negora) wrote :

Oh, just to clarify... May the fact of using the 64-bit version be the origin of these problems? Because many of the solutions which other comments seem to happen on i386 systems.

Revision history for this message
negora (negora) wrote :

OK, I have been able to make it WORK :) .

I've edited /usr/lib/X11/xorg.conf.d/05-evdev.conf by hand. I've altered this:

Section "InputClass"
    Identifier "evdev pointer catchall"
    MatchIsPointer "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

By:

Section "InputClass"
    Identifier "evdev pointer catchall"
    MatchIsPointer "on"
    MatchDevicePath "/dev/input/event3"
    Driver "evdev"
EndSection

Basically what I'm doing is specifying /dev/input/event3 as the only pointer in my system, in order to avoid that my tablet "falls" in this rule and make it be caught by the other rule at 70-wizardpen.conf (supposedly, as I still need to know if X reach this file or not). Now the output from Xorg.0.log looks like OK and shows how the "wizardpen" module is loaded successfully.

Now I'm doing more research to know why 70-wizardpen.conf didn't overwrite the rule specified at 05-evdev.conf .

Revision history for this message
negora (negora) wrote :

I believe to have found part of the origin of this issue and a solution. There are 2 important conclusions:

1 - My tablet is not "recognized" as being a tablet but a pointer, so the "MatchIsTablet" rule at /usr/lib/X11/xorg.conf.d/70-wizardpen.conf won't work ever. I've tried different possibilities and "MatchIsPointer" works right.

I guess that it has something to do with UDEV and the rule files. On HAL there was a key which allowed to set the device as a tablet (as a stylus really):

<merge key="input.product" type="string">stylus</merge>

However, I've no idea about if this could be achieved in UDEV in a similar way.

2 - If we only replace "MatchIsTablet" by "MatchIsPointer", this will activate the rule and cause the pointer to move and get stuck to the coordinate 0,0 . It's mandatory to set the dimensions of the tablet to make it work.

So, summarizing, here it's my 70-wizardpen.conf file:

Section "InputClass"
   Identifier "wizardpen"
   MatchIsPointer "on"
   MatchDevicePath "/dev/input/event*"
   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   Driver "wizardpen"
   Option "TopX" "2650"
   Option "TopY" "3563"
   Option "TopZ" "10"
   Option "BottomX" "30733"
   Option "BottomY" "29715"
   Option "BottomZ" "511"
EndSection

Section "InputClass"
   Identifier "wizardpen ignore mouse dev"
   MatchIsPointer "on"
   MatchDevicePath "/dev/input/mouse*"
   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   Driver ""
EndSection

And that's all. I hope that someone with more knowledge investigate the origin of all this. By now, this patch works flawless ;) .

Revision history for this message
Guillermo Espertino (Gez) (gespertino-gmail) wrote :

It finally worked! Thank you!
I had two problems, but I could solve them:
-First, X didn't start. That was caused by the spaces before the options. I removed the spaces and it started.
-I had to comment the "MatchVendor" lines to make it work properly.

Everything works so far, but the device is still detected 3 times. Not a big problem, but I have 3 inputs in GIMP and Inkscape "extended devices" rollout to set.
But hey, it works. I hope all this information can be useful for a future version of the driver.

Meanwhile I'll mark my report as a duplicate of this.

Revision history for this message
negora (negora) wrote :

I'm happy that it has worked for you too!

I should have attached 70-wizardpen.conf as a file instead of copying and pasting its content directly. That way you wouldn't have had any problem to start X, I guess.

About the "MatchVendor" line, maybe you should check one useful command which IrishBandit gave us on the ticket which you opened:

sudo udevadm monitor --property

If you check the log file which you attached, the variable ID_VENDOR_ENC is equal to \x20\x20\x20 . That's why "MatchVendor" doesn't match yours. Although you can comment that line (as you did), I'd recommend you to append that weird vendor name to the rule:

MatchVendor "UC-LOGIC|KYE Systems|Ace Cad|\x20\x20\x20"

Otherwise, other devices which match all the rest of conditions would be affected by this rule too. I'm not sure if that vendor name is what the hardware reports about or it's a mistake from the wizardpen driver.

PS: Thanks to IrishBandit for spending its time to try to help us, of course :) .

Revision history for this message
Irishbandit (irishbandit) wrote :

Negora
No i use 64-bit and it is working great.
I would delete the following out of my Xorg.conf and use the /usr/lib/X11/xorg.conf.d/70-wizardpen.conf
having its configuration in both configuration files is confusing and could cause problems.

delete or comment out
Section "InputDevice"
  Identifier "Tablet0"
  Driver "wizardpen"
  Option "Device" "/dev/input/event6"
  Option "TopX" "2650"
   Option "TopY" "3563"
  Option "TopZ" "10
  Option "BottomX" "30733"
  Option "BottomY" "29715"
  Option "BottomZ" "511"
 EndSection

Then restore 05-evdev.conf to original file.

Run the command:
cat /proc/bus/input/devices
find your tablet in the list and where it says H: Handlers=mouse# event# mine is H: Handlers=mouse1 event4
copy the mouse# and event#
edit /usr/lib/X11/xorg.conf.d/70-wizardpen.conf
add you event# and mouse# where the event* and mouse* are at
so it looks like this:
Section "InputClass"
   Identifier "wizardpen"
   MatchIsTablet "on"
   MatchDevicePath "/dev/input/event*"
## MatchVendor "UC-LOGIC|KYE Systems|Ace Cad" comment out this line
   Driver "wizardpen"
   Option "TopX" "2650"
   Option "TopY" "3563"
   Option "BottomX" "30733"
   Option "BottomY" "29715"
   Option "TopZ" "10"
   Option "BottomZ" "1023"
EndSection
Section "InputClass"
   Identifier "wizardpen ignore mouse dev"
   MatchIsTablet "on"
   MatchDevicePath "/dev/input/mouse*"
## MatchVendor "UC-LOGIC|KYE Systems|Ace Cad" comment out this line
   Driver ""
EndSection

Restart computer or restartX with a ctrl+backspace
See if it works.

Revision history for this message
negora (negora) wrote :

Irishbandit:

Prior to my last test, I also tried that, taking the example from the UbuntuForum thread which you supplied on the other ticket. However it didn't work either :( . Since MatchIsTablet never meets the "on" value, it won't work for my case.

Revision history for this message
Irishbandit (irishbandit) wrote :

Did you delete the configuration in xorg.conf before you tried?
Section "InputDevice"
  Identifier "Tablet0"
  Driver "wizardpen"
  Option "Device" "/dev/input/event6"
  Option "TopX" "2650"
   Option "TopY" "3563"
  Option "TopZ" "10
  Option "BottomX" "30733"
  Option "BottomY" "29715"
  Option "BottomZ" "511"
 EndSection

Revision history for this message
Irishbandit (irishbandit) wrote :

The other thing we need to look into is the pressure sensitivity since most of these pads have 1024 sensitivity changing topz to a higher value might help in some cases.

Revision history for this message
stripedxii (darkness-is-awesome) wrote :

Ok, I kind of had the same problem and tried your solutions, but when I the tablet did start working properly but now my USB mouse just moves the cursor to the top left and makes it stay there whenever I move it. Does anyone know a fix to this?

Revision history for this message
Irishbandit (irishbandit) wrote :

stripedxii. Which solution did you try?

Revision history for this message
stripedxii (darkness-is-awesome) wrote :

When I did Negora's solution, the tablet worked but the USB mouse gets stuck at the very top left. When I tried yours, the tablet gets stuck if pressed but the USB mouse works.

Revision history for this message
Irishbandit (irishbandit) wrote :

Looks like this is a problem all over the forums with 10.04.
I posted a response to your thread at http://ubuntu-ky.ubuntuforums.org/showthread.php?p=9274428
is that the solution you tried?
You would need the other options for your tablet I left them blank.

Revision history for this message
stripedxii (darkness-is-awesome) wrote :

well in the /usr/lib/X11/xorg.conf.d/70-wizardpen.conf, if I change "MatchIsTablet" to "MatchIsPointer" the tablet starts working how it should, but the USB Mouse goes instantly to the top left corner. If I keep it "MatchIsTablet" the tablet lets me move the cursor around until I press it which makes it freeze until I unplug it and plug it back in, but the usb mouse works.

Revision history for this message
negora (negora) wrote :

IrishBandit:

Yes, I did all my last tests commenting the old tablet configuration in /etc/X11/xorg.conf . Once I made it work using the file /usr/lib/X11/xorg.conf.d/70-wizardpen.conf , then I even deleted such lines from xorg.conf (but not deleted the whole file, since I need it for the nVidia graphics card). As I mentioned before, the only line which cause all this mess is "MatchIsTablet".

stripedxii:

Make sure that you have NOT commented the line MatchVendor "UC-LOGIC|KYE Systems|Ace Cad" . If everything is OK, your mouse would never be affected by this rule, except if it's manufactured by UC-Logic, KYE Systems or Ace Cad, of course. But I doubt that your mouse is from that branch, Right?

Revision history for this message
stripedxii (darkness-is-awesome) wrote :

If I uncomment the MatchVendor line, the tablet stops working again.

Revision history for this message
negora (negora) wrote :

stripedxii: You've SEVERAL ways to solve that. The idea behind this configuration file is to RESTRICT only the necessary.

So either you add the name of the vendor of your tablet to the MatchVendor key (using a pipe like "|" to separate the name from the others), or you set MatchDevice to the specific device path of your tablet, replacing event* by the concrete one. There are even more ways of achieving the same if you employ other kind of matching rules.

If you decide to use the rule MatchVendor, type:

sudo udevadm monitor --property

And look for a keyword called ID_VENDOR_ENC .That's the vendor name.

However, if you choose to use MatchDevice, type:

ls -al /dev/input/by-id

And see which event points to your tablet.

Both ways should work, as long as you keep MatchIsPointer instead of MatchIsTablet and you also specify the tablet features explicitly.

Revision history for this message
negora (negora) wrote :

I forgot to mention that apart of using MatchIsPointer, MatchVendor, etc. you can also use the rule MatchProduct . You can get the product name in the same way that you got the vendor name, but looking for the key ID_MODEL_ENC instead.

The biggest confusion here comes from the MatchIsTablet rule, which seems not to work because our tablets are detected as simple pointers.

Revision history for this message
stripedxii (darkness-is-awesome) wrote :

I've tried each of those and although it makes the mouse work again, the tablet starting freezing unless pressed.

the event thing worked, but only if I don't disconnect anything which I really can't do since I'm on a laptop.

according to "ID_VENDOR_ENC" it is "\x20"
according to "ID_MODEL_ENC" it is "TABLET\x20DEVICE"

and I tried using each of those separately in 70-wizardpen.config and it just causes my tablet to freeze when pressed and won't move unless its pressed against the pad still. The tablet only seems to want to work if I comment the MatchVendor (and now MatchProduct) but if I do that, the mouse stops working.

Revision history for this message
negora (negora) wrote :

stripedxii:

MatchVendor and MatchProduct may not be working because these keys use something called regular expressions, which allow the combination of signs which have a special meaning. The reverse bar \ is one of that special characters and, since you use \x20 , it may be affecting to the rule

Try using a double bar:

"MatchVendor" "\\x20"

Or 4 bars:

"MatchVendor" "\\\\x20"

Or maybe, in the product name, use .* :

"MatchProduct" "TABLET.*"

I hope that anything of that works.

Revision history for this message
stripedxii (darkness-is-awesome) wrote :

I found the problem
' according to "ID_MODEL_ENC" it is "TABLET\x20DEVICE" '

Putting MatchProduct "TABLET DEVICE" instead of "TABLET\x20DEVICE" worked perfectly. I was guessing "\x20" meant "space" since other terminal commands said my tablet's name was " TABLET DEVICE"

Thanks for your help =)

Revision history for this message
negora (negora) wrote :

stripedxii: Cool :) . 20 is the hexadecimal code of the space in the Unicode character set (that's why it's preceded by \x ). I'm sorry for taking this last issue to the "land" of the regular expressions (which is valid, by the way) instead of telling you to try with a simple space, so... I guess that programming so many hours a day has "modelled" my mind to think in that terms :P .

Revision history for this message
andrew87 (andrew1987) wrote :

Hello

I'm Italian, I'm sorry for my bad English, I hope that you can understand me...
I'm writing about this problemi everywhere about this problem because for me is very important to use this tablet with ubuntu
I've got the Trust TB-6300 tablet + mouse, I minutely followed this guide:

https://help.ubuntu.com/community/TabletSetupWizardpen

My problem is the sequent: the pen work correctly, but the mouse, when I try to move, put the cursor in the top left corner of the screen, and don't move at all... the button seems to work correctly too.

I edited my xorg.conf file (even if this edit don't seems to serve)
I edited my 70-wizardpen.conf file whit the correct addres of device.
I try to change MathIsTablet whit MatchIsPointer too

Nothing... the cursor remains stuck in that damn corner (only with mouse).
But I tried to do a particular edit to xorg.conf file:

Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection

And when I rebooted the system, magically the mouse work perfectly!!!! but the pen and the keyboard didn't work no more...

Revision history for this message
Jairo Serrano (jairo-serrano) wrote :

The mouse and the tablet works fine with

Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection

but the keyboard dont work!

how i do to enable the keyboard?

Revision history for this message
negora (negora) wrote :

Don't add that clause. Instead try to "play" with the other keywords.

Revision history for this message
andrew87 (andrew1987) wrote :

other keywords?

Martin Owens (doctormo)
summary: - Manhattan tablet (WP8060U) working weird on Ubuntu 10.04 (Lucid Lynx)
+ Incorrect configuration for udev and xorg for wizardpen tablets.
Revision history for this message
matrix (maxim-kyznecoff) wrote : Ответ: [Bug 576610] Re: Manhattan tablet (WP8060U) working weird on Ubuntu 10.04 (Lucid Lynx)

Hello
the fact that I have on ubuntu 10 .. 04 not working tablet
6300
I installed 9.10 on there for me all
worked
I have a box with Linux and
there I take the tablet.
If I have
success with the installation of ubuntu then I will write you

Revision history for this message
eamusic (edwandrade-hotmail) wrote :

Hola a todos

Muchas gracias por la ayuda, finalmente POR FIN tengo funcionando mi table MousePen 8x6 Genius.

Gracias a Negora, pues la configuración de su 70-wizardpen.conf me sirvió totalmente.

Saludos.

Revision history for this message
Ivan Ivanoff (spammeroff) wrote :

Genius EasyPen i405 does not work with you driver in Lucid (flawlessly works in 9.10). Pointer runs to the upper left corner of screen and stops there. Something wrong with evdev and wizardpen.
Here my xorg.0.log:
(II) config/udev: Adding input device UC-LOGIC Tablet WP5540U (/dev/input/event7)
(**) UC-LOGIC Tablet WP5540U: Applying InputClass "evdev pointer catchall"
(**) UC-LOGIC Tablet WP5540U: Applying InputClass "evdev tablet catchall"
(**) UC-LOGIC Tablet WP5540U: always reports core events
(**) UC-LOGIC Tablet WP5540U: Device: "/dev/input/event7"
(II) UC-LOGIC Tablet WP5540U: Found 10 mouse buttons
(II) UC-LOGIC Tablet WP5540U: Found scroll wheel(s)
(II) UC-LOGIC Tablet WP5540U: Found relative axes
(II) UC-LOGIC Tablet WP5540U: Found x and y relative axes
(II) UC-LOGIC Tablet WP5540U: Found absolute axes
(II) UC-LOGIC Tablet WP5540U: Found x and y absolute axes
(II) UC-LOGIC Tablet WP5540U: Found absolute tablet.
(II) UC-LOGIC Tablet WP5540U: Configuring as tablet
(**) UC-LOGIC Tablet WP5540U: YAxisMapping: buttons 4 and 5
(**) UC-LOGIC Tablet WP5540U: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "UC-LOGIC Tablet WP5540U" (type: TABLET)
(WW) UC-LOGIC Tablet WP5540U: touchpads, tablets and touchscreens ignore relative axes.
(II) UC-LOGIC Tablet WP5540U: initialized for absolute axes.
(II) config/udev: Adding input device UC-LOGIC Tablet WP5540U (/dev/input/mouse2)
(II) No input driver/identifier specified (ignoring)

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Please see this post by Martin about tablets support:
https://lists.launchpad.net/wizardpen-testers/msg00000.html

Also consider joining this team to help get further support for your devices:
https://edge.launchpad.net/~wizardpen-testers

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers