So, I just confirmed that the code that once worked on Gutsy for touchscreen does not work on Hardy. Worse yet, the elographics driver used in Hardy has a bug, see:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-elographics/+bug/218671 In order to get this going, you will need to upgrade the elographics driver in your Hardy chroot, and remove the line in /opt/ltsp/i386/usr/lib/ltsp/configure-x.sh that adds the: Option "AlwaysCore" "true" to the touchscreen configuration. The buggy elographics driver doesn't work at all with that line in there. It looks like the elographics driver is getting fixed, if you follow that thread, but unless a backport for hardy is requested when it is fixed, you will need to use a different package (perhaps Debian's package) in the chroot. Hope that helps explain things, -Gadi On Wed, 2008-09-03 at 14:02 -0400, Gideon Romm wrote: > Tom, > > Hi. I apologize. I have been on vacation from the computer for the > past two weeks. Every now and then - ya gotta get away ;) > > Anyhow, I was the one who added the touchscreen code to configure-x.sh > (the X configuration script used in Ubuntu LTSP5). At the time of the > merge, I was on a Gutsy (7.10) chroot, and frankly still am for my > development platform. > > I have begun retesting some things on a Hardy (8.04.1) platform, but > have not touched touchscreen, yet. Frankly, I wasn't clear that I was > not the only one in the galaxy using it. :) > > I will try to setup a test soon, so I can see what is going on. > > You should note that Gutsy uses X.org version 1.3, while in Hardy, they > are up to 1.4. X.org and ubuntu have been changing a lot recently in > the way various things are handled. Sometimes, options that made sense > in previous versions, like "AlwaysCore" cause problems in later > versions. To the X.org guys it's just something that a user should > change in their configs. To LTSP, however, where we generate a config, > it means modifying/updating the script. > > Thanks for testing - this is how we fix things from version to version! > > -Gadi > > > On Thu, 2008-08-21 at 12:04 +0100, Tom Knowles wrote: > > Kevin, > > First of all, the non recognition of the lts.conf was down to my > > stupidity. > > That aside, I cannot get any touch on my 'other' system at all, doing, > > as I perceive, all the same things. The screen is another ELO model, but > > that shouldn't make any diff. Taking my previous experience of > > touchscreens on ltsp<=4, I believe there is a fundamental issue, and, > > unless we are very lucky, we'll not get to understand why & how to > > comfortably reproduce it. That decidedly unnerves me. > > I have tried reversing the MinX/MaxX in a number of combinations (on the > > 'working' system) but with all alternatives, the cursor just disappears > > when I touch the screen. So I'm back to the point of initial excitement > > and then deflation, and my dodgy Y-axis. I'm very puzzled by the > > differences and inconsistencies. Unless I/we can get some confirmatory > > input from someone who KNOWS, then I may have to abandon for the time > > being. You can only spend so much time reinventing the wheel, and, when > > the discoveries are accidents, there isn't really much progress. Gideon > > Romm seems to understand quite a lot, but at the mo, I don't know > > whether that's practical or theoretical. I hope he responds, and, I > > wonder, has anybody got this working consistently in a real environment? > > Stay in touch, just maybe there will be answers before I concede. > > Regards > > Tom > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _____________________________________________________________________ > > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > > For additional LTSP help, try #ltsp channel on irc.freenode.net > -- > -------------------------------------------------------- > Gideon Romm | Proud LTSP Developer > [EMAIL PROTECTED] > > Support LTSP! Buy your hardware at: > > www.DisklessWorkstations.com > www.DisklessThinClients.com > > (use coupon code: LTSP5P for 5% off thin clients from DisklessThinClients.com) > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.freenode.net -- -------------------------------------------------------- Gideon Romm | Proud LTSP Developer [EMAIL PROTECTED] Support LTSP! Buy your hardware at: www.DisklessWorkstations.com www.DisklessThinClients.com (use coupon code: LTSP5P for 5% off thin clients from DisklessThinClients.com) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
