evtoch calibration does not consistently work

[Andrew Frank]

i have a touchscreen. karmic detects the stylus out of the box !! great!!! but i cannot calibrate the stylus. i have installed the touchscreen calibration and it produces an etc/evtouch/config file (and i have replaced it with one that i am sure to be working from the jaunty installation). after restart it sometimes uses this calibration , sometimes not. then the stylus sends the cursor always into the lower left corner (trash opens) indepenent where on the screen i touch. sometimes it works. it seems that the evtouch/config file is not always read during startup (is there a way to force this reading? is there a way to check that it is read?)

thank you - progress to an out of the box working for tablets is made!
andrew

ProblemType: Bug
Architecture: i386
Date: Sun Oct 4 22:29:41 2009
DistroRelease: Ubuntu 9.10
MachineType: FUJITSU LifeBook P1630
Package: xserver-xorg-input-evtouch 0.8.8-0ubuntu3
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=10394d0e-9429-41f4-ad98-667d6f72fcd9 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu7
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
SourcePackage: xf86-input-evtouch
Uname: Linux 2.6.31-11-generic i686
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 11/14/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB1F8
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: A322H10305301010
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd11/14/2008:svnFUJITSU:pnLifeBookP1630:pvr:rvnFUJITSU:rnFJNB1F8:rvr:cvnA322H10305301010:ct10:cvr:
dmi.product.name: LifeBook P1630
dmi.sys.vendor: FUJITSU
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-11-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
     Subsystem: Fujitsu Limited. Device [10cf:145c]

[Andrew Frank (frank-geoinfo)]

afer some experimentation i found that touchscreen calibration sets the value minY wrongly - it uses a value similar to minX, but it should be different (in my case minX is 449 and minY is 1384.

i checked the code of the calibrate_touchscreen, but i cannot understand the logic. where is some documentation found?

[Andrew Frank (frank-geoinfo)]

just got the updates (fri oct 9) and now the issue seems resolved! the figures the calibration program reports are seemingly ok and the cursor is calibrated after restart!

good work! congratulations!

andrew

[Andrew Frank (frank-geoinfo)]

after another dist upgrade (fri oct 9 - i got seemingly only part of the upgrade and ubuntu crashed in the process - compiz. report send) i found:
twice i had to do the calibration twice in a row. the first time, minx and miny (the figure top left) is 4xx/4xx and remains in the 400 range for both (this is wrong for myscreen, it should be 400/1400). after calibration, the cursor is somewhere ...
when i do calibration immediately afterwards again, then it starts with 2000/2000 and goes quickly to 400/1400 range figures. then the calibration is good after restarting the xserver with ctrl-alt-bcksp.

this is confusing and i hope you can fix it.
andrew

[Andrew Frank (frank-geoinfo)]

i just installed the new distribution - the behaviour has not changed substantially:
1. calibration is lost with every restart
2. calibration is after restart mapping any touch to the lower left corner (opening trash)
- after recalibratin it is off (calibration shows 400/400 as min values
only after the second recalibration (which shows 400/1400 for min values) the calibration is precise.
then it works --- till the next restart or even a hibernate/rewake makes it loose calibration.

thanks for your attention

[Eric Drechsel (ericdrex)]

Confirmed, Panasonic CF-T2. Calibration works after restarting X, but isn't used on the next boot. Running

    sudo service xserver-xorg-input-evtouch start
    sudo service gdm restart

applies the calibration. This service should be started at boot but isn't?

[Eric Drechsel (ericdrex)]

Actually, the issue is that the init.d script is being run *after* gdm starts (restarting gdm makes the touchscreen work). This is tricky since:

   1. gdm and hal have been moved to upstart (/etc/init/)
   2. script must be run after hal but before gdm

I think that the calibration wrapper script needs to be updated to output a .fdi file into /etc/hal/fdi/policy. It would have the same effect as the script, except it would be automatically picked up by hal. This is simple enough that I can write a patch. Hopefully it can be put into karmic updates.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Andrew,

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 442553

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 442553 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/442553

[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.