Created attachment 33435 [details] The relevant part of xorg.conf without the MinY and MaxY swapped. Hi, I was using the MuTouch driver with Xorg 6.9 and everything was working perfectly. Then I updated Xorg to version 7.4 and the MuTouch driver from git (2009-07-17) and the Y axis was suddently inverted. I also tried with MuTouch version 1.2.1 and I had the same result. Is this a bug with X, the MuTouch driver or my configuration file? I tried swapping the MinY and MaxY values and it worked, but I was wondering if this is the expected behaviour, or if it is a bug. Thanks. P.S. My config and log files are attached. P.P.S. The server version is 1.6.1, protocol 11r0.
Created attachment 33436 [details] The relevant part of Xorg.0.log
are you using the same xorg.conf as you did before? there were some changes in both the server and the driver where originally (iirc) the server handled inverted axes automatically (if min > max). at some point that stopped and we had to update the drivers to do it in the driver. mutouch was one driver affected here. it still shouldn't have changed for you if you maintained the same configuration file though. the problem with mutouch is that it is essentially unmaintained, none of the active X developers have a device to even test changes on beyond compile-time checks. so the problem could very-well be in mutouch itself too.
(In reply to comment #2) > are you using the same xorg.conf as you did before? > > there were some changes in both the server and the driver where originally > (iirc) the server handled inverted axes automatically (if min > max). at some > point that stopped and we had to update the drivers to do it in the driver. > mutouch was one driver affected here. > > it still shouldn't have changed for you if you maintained the same > configuration file though. the problem with mutouch is that it is essentially > unmaintained, none of the active X developers have a device to even test > changes on beyond compile-time checks. so the problem could very-well be in > mutouch itself too. > Yes, I'm using the same exact configuration file.
This is weird. I can't see any reason why the axis should be swapped now, rather confusing. Do you have a second machine? If so, can you build with debugging symbols (simply run export CFLAGS="-g -O0 -Wall" before running configure) and attach gdb to the server. This way, you can step through the code to find out where it goes wrong. I'd like to release a new version of mutouch since the current released one doesn't even build against the current server but first I'd like to resolve this issue.
> --- Comment #4 from Peter Hutterer <peter.hutterer@who-t.net> 2010-03-03 15:40:08 PST --- > This is weird. I can't see any reason why the axis should be swapped now, > rather confusing. Do you have a second machine? If so, can you build with > debugging symbols (simply run export CFLAGS="-g -O0 -Wall" before running > configure) and attach gdb to the server. This way, you can step through the > code to find out where it goes wrong. > Christopher, did you get a chance to try this?
(In reply to comment #5) > > --- Comment #4 from Peter Hutterer <peter.hutterer@who-t.net> 2010-03-03 15:40:08 PST --- > > This is weird. I can't see any reason why the axis should be swapped now, > > rather confusing. Do you have a second machine? If so, can you build with > > debugging symbols (simply run export CFLAGS="-g -O0 -Wall" before running > > configure) and attach gdb to the server. This way, you can step through the > > code to find out where it goes wrong. > > > Christopher, did you get a chance to try this? Well, I looked at the values returned by the hardware with this driver and with the older (working) version, and they are the same... We had to release a build really soon so I went with the config file fix. I guess it is the way the driver is supposed to work.
Closing this - it's probably just a (semi :) intended behaviour of the switch to the X server doing the work the conversion_proc used to do.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.