On Fri, 2014-03-07 at 10:21 +0100, Vincent Lefevre wrote: > On 2014-03-02 19:10:54 +0100, Vincent Lefevre wrote: > > Note that they are not the same bugs. In 740485, the touchpad was > > correctly recognized as "AlpsPS/2 ALPS DualPoint TouchPad" according > > to syslog information. The problem was that some events (when moving > > the finger on the touchpad) were not generated -- a bit randomly: the > > problem was occurring for several seconds, then the touchpad worked > > again... until the problem reappeared several dozens of seconds later. > > Something that never occurred before. > > > > The problem completely disappeared after a suspend + resume. > > While everything was OK for several days, the problem has just > reappeared, and a suspend + resume didn't change anything. Like > when the problem first occurred, it occurs in the train (whether > it is moving or not). But I don't see why a train would have an > influence on the touchpad. It could be affected by vibration, electromagnetic fields, noise on the power line (if you use a socket on the train). But I wouldn't expect so. I would guess that you usually have the laptop plugged into a socket, except on the train, and that's what makes the difference. Ben. > Notes: > * Same problem in the text virtual terminals, so that it is not > specific to X. > * The DualPoint Stick doesn't have such a problem. > -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody.
Attachment:
signature.asc
Description: This is a digitally signed message part