wacom does not work after upgrade to gutsy

Bug #151902 reported by Leon van der Ree
4
Affects Status Importance Assigned to Milestone
wacom-tools (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

My wacom device (on Toshiba M200) does not work anymore after the upgrade from Feisty to Gutsy.

wacdump /dev/input/wacom gives me:
11:35:35.386 ERROR: Failed to open /dev/input/wacom: No such device
WacomOpenTablet: No such device

While /dev/input/wacom still is a symlink to /dev/ttyS0

But under system/preferences/hardware info (HAL device manager) (I've got Dutch installed, so maybe this menu is called differently, but I assume you know what I mean) I see the wacom device mentioned, and linked to /dev/ttyS0

Revision history for this message
Leon van der Ree (lvanderree) wrote :

I still haven't got this working, but I found out that with the live-cd of gutsy my tablet works.

With the livecd I can run "cat /dev/ttyS0" and see weird symbols whenever I move my pen over the screen.

In my upgraded gutsy I get "unknown device" (in Dutch)

I am not in the mood to reinstall Ubuntu, and I guess it should be possible to have it working without reinstalling.

Revision history for this message
Leon van der Ree (lvanderree) wrote :

I think it should be linked to the wacom-kernel-source package, but wacom-tools or xserver-xorg-input-wacom might be possible as well...

Revision history for this message
anco (ancovanbergeijk) wrote :

Did you check your xorg.conf for outcommented lines in the last part of xorg.conf

For me wacom works fine if I freshly start Gutsy, but after suspend it never comes backu until I do a reboot. I'm searching if somebody did already a bugreport on this one, but first try to give you an answer.

Revision history for this message
Leon van der Ree (lvanderree) wrote :

I have the same xorg.conf as in Feisty, so I don't tink there can be anything wrong with it, unless gutsy should have added something to it.

But I think that even if I have a problem in my xorg.conf, I still should be able to get some feedback from "cat /dev/ttyS0"

Just to be sure, I post you the lines I have, related to the tablet-pen:

Section "InputDevice"
        Driver "wacom"
        Identifier "stylus"
        Option "Device" "/dev/input/wacom"
        Option "Type" "stylus"
        Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "eraser"
        Option "Device" "/dev/input/wacom"
        Option "Type" "eraser"
        Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
        Driver "wacom"
        Identifier "cursor"
        Option "Device" "/dev/input/wacom"
        Option "Type" "cursor"
        Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "ServerLayout"
        Identifier "Default Layout"
  screen "Default Screen"
        Inputdevice "Generic Keyboard"
        Inputdevice "Configured Mouse"
        Inputdevice "stylus" "SendCoreEvents"
        Inputdevice "cursor" "SendCoreEvents"
        Inputdevice "eraser" "SendCoreEvents"
        Inputdevice "Synaptics Touchpad"
EndSection

Revision history for this message
Leon van der Ree (lvanderree) wrote :

I finally decided to reinstall Gutsy and now my tablet also works until I put the system in standby.

When I resume from standby the pen again does not work anymore.

Revision history for this message
kvpetrov (kvpetrov) wrote :

I have exactly the same problem on my Toshiba m200, the pen works until the machine is suspended. Once suspended the pen does not work at all even if I restart X (switching to console Alt-F1 /etc/init.d/gdm stop, /etc/init.d/gdm start).

Quite annoying taking into account that it worked just fine with Feisty.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

The "pen not working after suspend" is bug 108961, but this bug apparently was "fixed" by something, so I'll close it now. Thanks.

Changed in wacom-tools:
status: New → Invalid
Revision history for this message
Leon van der Ree (lvanderree) wrote :

As far as I know this bug (and bug 108961) is not fixed.

I can confirm this for Gutsy and Hardy Alpha2.

I just retested this with the latest Hardy-updates and with additional parameters in my xorg.conf, but I can see the folowing (new) problem in my xorg-log file:

module ABI major version (0) doesn't match the server's version (2)

I see an ABI class versio 0.7 beiing mentioned for the wacom module.(compiled for 4.3.99.902, module version= 1.0.0)

wacdump /dev/input/wacom (which is a symlink I created to /dev/ttyS0 (this was created in gutsy by default)) returns some data when I hover with my pen above the screen after a fresh start.

After standby I cannot do this anymore, first I get
No such device,
trying it a second time I get
Invalid argument

I think this report should be re-opened...

Revision history for this message
Leon van der Ree (lvanderree) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.