On Sun, Jun 11, 2006 at 02:39:40AM -0600, Warren Turkal wrote: > On Sunday 11 June 2006 01:30, Mattia Dongili wrote: > > I strongly suspect an interaction with something else. Do you have any > > of the graphical configuration client installed > > (gsynaptics/ksynaptics/qsynaptics)? > > Can you attach an Xorg.0.log of a session? > > All of the testing was done from a failsafe session started from kdm. The > failsafe session starts some X terminal (maybe the gnome one) and nothing > else. Also, I do not have ksynaptics or qsynaptics installed as they were my > first recipient of blame. I have attached Xorg.0.log. Here is a paste of the > most relevant thing in the log, I think. > > (II) Synaptics touchpad driver version 0.14.5 (1405) > (--) Synaptics Touchpad auto-dev sets device to /dev/input/event1 > (**) Option "Device" "/dev/input/event1" > (**) Option "SHMConfig" "true" > (**) Option "RightEdge" "5980" > (**) Option "HorizScrollDelta" "0" > (--) Synaptics Touchpad touchpad found > > It may be important to notice that it sets the parameters before the > Synaptics > Touchpad is found. There is another reference to the touchpad near the botton > of the log.
this is normal :) The driver usually need some piece of configuration to detect the proper device. > Synaptics DeviceOn called > (--) Synaptics Touchpad auto-dev sets device to /dev/input/event1 > (**) Option "Device" "/dev/input/event1" > (--) Synaptics Touchpad touchpad found > > There is no mention of setting the options here, but I guess it really > wouldn't make sense to set the options again. BTW, here is the output > of "synclient -l | grep RightEdge" for reference on the same X session this > log covers. > > [EMAIL PROTECTED]:~$ synclient -l | grep RightEdge > RightEdge = 5300 but this is definitely weird. The default for that option is "5400" so there _must_ be something external intervening. Can you disable SHMConfig and see if you're able to tell if the behaviour is correct or not? I mean, can you tell without the help of synclient if the right edge is what you defined or not? [...] > I would also like to say that this has been a long term problem. I am pretty > sure this was happening with the 6.9 version of X before 7.0 hit unstable, > but I really don't remember with absolute certainty. I think this bug may > also be the same problem as bug #370795. The same bug could potentially be > causing #335209, but I can't really tell since #335209 involves ksynaptics. Yes, I mostly agree, but I'd need more insight before merging them. I'm still convinced there's something external playing dirty here, the configuration routines are pretty straightforward and such weird things are hard to happen in the driver itself... thanks again -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
