Problems with Pensketch 12x9 (UC-Logic) and Ubuntu 10.04

[Guillermo Espertino (Gez)]

I just installed Ubuntu 10.04 - 64 bit and can't make my tablet work properly. I'm using the driver from doctormo's PPA.

The tablet behavior is the following: if I hover the pen over the tablet, the cursor moves, but as soon I press the tip on the tablet, the cursor stops moving and the only way I can move it is applying pressure on the tip. If I unplug and plug the device, I get the same. The cursor moves until I press the tip on the tablet.
I tried with my previous FDI from Jaunty and it didn't help.
I thought that could be the button mapping but when I tried to re-map the buttons found something strange: the device is listed three times when I run xsetpointer -l. The same happens if I run grep -i name /proc/bus/input/devices
Does it have something to do with the problem?

I'm attaching the Xorg log (my xorg.conf file is empy, so I guess the driver is using the .fdi)

The lsusb output for my tablet is:
Bus 003 Device 002: ID 5543:0042 UC-Logic Technology Corp. Genius PenSketch 12x9 Tablet

[Irishbandit (irishbandit)]

looking at your log file the wizardpen driver is not loading for your tablet.

For mine the log looks something like this.
(II) config/udev: Adding input device UC-LOGIC Tablet WP5540U (/dev/input/event4)
(**) UC-LOGIC Tablet WP5540U: Applying InputClass "evdev pointer catchall"
(**) UC-LOGIC Tablet WP5540U: Applying InputClass "evdev tablet catchall"
(**) UC-LOGIC Tablet WP5540U: Applying InputClass "wizardpen"
(II) LoadModule: "wizardpen"
(II) Loading /usr/lib/xorg/modules/input/wizardpen_drv.so

Make sure you have the xserver-xorg-input-wizardpen version 0.7.3 or higher loaded.
Could you then post the output from the following command when you unplug and plug in the tablet?
sudo udevadm monitor --property

[negora (negora)]

It's really interesting. It's the same problem that I'm facing with my WP8060U tablet. I reported about this here: https://bugs.launchpad.net/wizardpen/+bug/576610 .

The issue of being listed several times seems to have sense in my case too, since the pen sends every event at least twice (read my description of the bug #576610 ). If I press the tip, it sends to "keypress" events, one using the key code 1 and and the other one with 9. Really curious!

I don't want to "corrupt" this thread from Gez, but in case that it's of help for we both, my results to the command "sudo udevadm monitor --property" are attached to this message.

[Guillermo Espertino (Gez) (gespertino-gmail)]

Here's my log of the udevadm output.

[Guillermo Espertino (Gez) (gespertino-gmail)]

Irishbandit: I didn't configure xorg.conf at all. I'm just using the fdi in the policy directory.
Should I add something in my xorg.conf file? (it's empty, btw).
I am using xserver-xorg-input-wizardpen version 0.7.3 from doctormo's PPA

[negora (negora)]

As long as I know, FDI files are useless on Ubunto 10.04 because the used version of X relies on udev instead of HAL. I have not much idea about udev rule files, but those included with the wizardpen pack seem to be OK: I checked them and the vendor and product IDs employed to "catch" my tablet are OK.

[Guillermo Espertino (Gez) (gespertino-gmail)]

I thought it was exactly the opposite, that moving from xorg.conf to
FDI files was because of the move from HAL to UDEV/Policykit. Are you
sure about that?
Anyway, I'm getting the same result with the FDI file, so it looks
like both xorg and FDI are working the same way.

[negora (negora)]

From my understanding, the idea of configuring input devices for X.org using FDI files (which correspond to the mechanism of HAL) lasted very little and it was quickly deprecated in favour of the UDEV rule files (I guess that by "PolicyKit" you really meant DeviceKit). HAL was integrated into UDEV, so FDI files became useless because UDEV uses other syntax.

[Irishbandit (irishbandit)]

Try this thread
http://ubuntu-ky.ubuntuforums.org/showthread.php?t=1475433
seems people are having problems with the vendor match its worth a try.

[negora (negora)]

Hello to you all. As I've just commented at bug 576610 , I've been able to make it work. Check it to know how I did it. It's a temporal solution until we know why it happens.

[negora (negora)]

SOLVED :) . Please, try the solution explained at bug 576610 .