Fujitsu T4310: tablet pen is not working after boot, need "restart gdm"

[H.-Dirk Schmitt]

Binary package hint: wacom-tools

After initial boot the tablet pen is not working.
If I do a "restart gdm" the tablet pen is recognized.

The Xorg.0.log shows before "restart gdm":
(WW) stylus: xf86WcmWrite ISDV4_STOP error : Input/output error
(WW) stylus: xf86WcmWrite ISDV4_STOP error : Input/output error
(EE) Couldn't init device "stylus"
(II) UnloadModule: "wacom"

ProblemType: Bug
Architecture: amd64
Date: Thu Feb 4 00:29:35 2010
DistroRelease: Ubuntu 9.10
MachineType: FUJITSU SIEMENS LifeBook T4310
Package: wacom-tools 1:0.8.4.1-0ubuntu4
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-18-generic root=/dev/mapper/system-root ro splash i8042.reset i8042.nomux
ProcEnviron:
 LANGUAGE=de_DE:de:en_US:en
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LC_PAPER=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.1-0ubuntu1+1
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1+1
SourcePackage: wacom-tools
Tags: ubuntu-unr
UdevDb: Error: [Errno 2] No such file or directory
Uname: Linux 2.6.31-18-generic x86_64
dmi.bios.date: 09/30/2009
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.05
dmi.board.name: FJNB206
dmi.board.vendor: FUJITSU
dmi.board.version: G4
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: LifeBook T4310
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd09/30/2009:svnFUJITSUSIEMENS:pnLifeBookT4310:pvr10601127925:rvnFUJITSU:rnFJNB206:rvrG4:cvnFUJITSUSIEMENS:ct10:cvrLifeBookT4310:
dmi.product.name: LifeBook T4310
dmi.product.version: 10601127925
dmi.sys.vendor: FUJITSU SIEMENS
fglrx: Not loaded
glxinfo:
 Error: couldn't find RGB GLX visual or fbconfig
 name of display: localhost:12.0
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-18-generic

[JDHarper (jdhbiz)]

I'm getting the same result: On boot, the pen isn't working; on "gdm restart" it works fine.

This is a relatively new behavior; it worked fine a couple of weeks ago. (Sorry that I can't be more specific; I only noticed the problem today and last used the pen input a couple weeks ago.)

[JDHarper (jdhbiz)]

New problem: Instead of just not working, using the pen now moves the cursor to the bottom of the screen, and slightly to the left of where I'm pointing with the pen. The same "gdm restart" command workaround fixes this for that session

[Bryce Harrington (bryce)]

Thank you for reporting this issue with wacom-tools, we are migrating it to the new xf86-input-wacom package which has replaced it in the development version of Ubuntu.

This would be a good point for you to re-test this issue against the new package to see if is still occurring. If not, you can mark it as Fix Released in Launchpad. If it is still an issue in the current development release and you're the original reporter, please reply and attach a fresh Xorg.0.log.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[JDHarper (jdhbiz)]

I've switched from ubuntu to kubuntu, and I'm still getting the same behavior: When I use the stylus initially, the cursor goes to the bottom-right corner of the screen. After I type "sudo /etc/init.d/gdm restart" into the terminal, KDE restarts and the stylus works properly.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi H.-Dirk,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 516823

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 516823 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/516823

[H.-Dirk Schmitt (dirk-computer42)]

Seems to be resolved in lucid.