reassign 613074 src:linux-2.6
thanks

Tayroni Francisco de Alencar <tayroni.alves@gmail.com> (13/02/2011):
> and the output of "evtest /dev/input/event7" (on tty1)
>
> Input driver version is 1.0.0
> Input device ID: bus 0x11 vendor 0x2 product 0x8 version 0x7321
> Input device name: "AlpsPS/2 ALPS GlidePoint"
> Supported events:
> Event type 0 (Sync)
> Event type 1 (Key)
> Event code 272 (LeftBtn)
> Event code 273 (RightBtn)
> Event code 274 (MiddleBtn)
> Event code 325 (ToolFinger)
> Event code 330 (Touch)
> Event type 2 (Relative)
> Event code 0 (X)
> Event code 1 (Y)
> Event type 3 (Absolute)
> Event code 0 (X)
> Value 238
> Min 0
> Max 1023
> Event code 1 (Y)
> Value 343
> Min 0
> Max 767
> Event code 24 (Pressure)
> Value 0
> Min 0
> Max 127
> Testing ... (interrupt to exit)
> Event: time 1297647718.798783, type 1 (Key), code 272 (LeftBtn), value 1
> Event: time 1297647718.798787, type 1 (Key), code 273 (RightBtn), value 1
> Event: time 1297647718.798790, -------------- Report Sync ------------
> Event: time 1297647718.957825, type 1 (Key), code 272 (LeftBtn), value 0
> Event: time 1297647718.957829, type 1 (Key), code 273 (RightBtn), value 0
> Event: time 1297647718.957831, -------------- Report Sync ------------
> Event: time 1297647720.472790, type 1 (Key), code 272 (LeftBtn), value 1
> Event: time 1297647720.472793, type 1 (Key), code 273 (RightBtn), value 1
> Event: time 1297647720.472796, -------------- Report Sync ------------
> Event: time 1297647720.642271, type 1 (Key), code 272 (LeftBtn), value 0
> Event: time 1297647720.642274, type 1 (Key), code 273 (RightBtn), value 0
> Event: time 1297647720.642276, -------------- Report Sync ------------
> Event: time 1297647721.340442, type 1 (Key), code 272 (LeftBtn), value 1
> Event: time 1297647721.340445, type 1 (Key), code 273 (RightBtn), value 1
> Event: time 1297647721.340447, -------------- Report Sync ------------
> Event: time 1297647721.549657, type 1 (Key), code 272 (LeftBtn), value 0
> Event: time 1297647721.549660, type 1 (Key), code 273 (RightBtn), value 0
> Event: time 1297647721.549662, -------------- Report Sync ------------
> Event: time 1297647722.167348, type 1 (Key), code 272 (LeftBtn), value 1
> Event: time 1297647722.167351, type 1 (Key), code 273 (RightBtn), value 1
> Event: time 1297647722.167354, -------------- Report Sync ------------
> Event: time 1297647722.296923, type 1 (Key), code 272 (LeftBtn), value 0
> Event: time 1297647722.296926, type 1 (Key), code 273 (RightBtn), value 0
> Event: time 1297647722.296928, -------------- Report Sync ------------
>
> I've pressed two times the left physical button and then, two times
> the right button.

Thanks, Tayroni.

As you can see, LeftBtn+RightBtn is sent every time, so that's not a
bug on the X side, rather on the kernel side. Reassigning there.

KiBi.

found 613074 linux-2.6/2.6.32-30
quit

Cyril Brulebois wrote:
> Tayroni Francisco de Alencar <tayroni.alves@gmail.com> (13/02/2011):

>> and the output of "evtest /dev/input/event7" (on tty1)
>>
>> Input driver version is 1.0.0
>> Input device ID: bus 0x11 vendor 0x2 product 0x8 version 0x7321
>> Input device name: "AlpsPS/2 ALPS GlidePoint"
[...]
>> Event: time 1297647718.798783, type 1 (Key), code 272 (LeftBtn), value 1
>> Event: time 1297647718.798787, type 1 (Key), code 273 (RightBtn), value 1
>> Event: time 1297647718.798790, -------------- Report Sync ------------
>> Event: time 1297647718.957825, type 1 (Key), code 272 (LeftBtn), value 0
>> Event: time 1297647718.957829, type 1 (Key), code 273 (RightBtn), value 0
>> Event: time 1297647718.957831, -------------- Report Sync ------------
[... snip the above repeated three more times ...]
>> I've pressed two times the left physical button and then, two times
>> the right button.
>
> Thanks, Tayroni.
>
> As you can see, LeftBtn+RightBtn is sent every time, so that's not a
> bug on the X side, rather on the kernel side. Reassigning there.

Thanks for a clear report. Basic questions:

- has this always acted this way since you started using Debian, or
did the problem begin with an upgrade (i.e., is it a regression)?

- can you reproduce this with the kernel from sid or experimental?
(It should be possible to test on a squeeze system by just
installing recent versions of the linux-image-<foo>, linux-base,
and initramfs-tools packages.) If so, we can report this upstream,
and if not, we can try to find the fix and backport it.

- please attach output of

/usr/share/bug/linux-image-$(uname -r)/script 3>&1

so we can get to know the hardware and drivers involved.

- any hunches, workarounds, or other weird symptoms?

Sorry for the delay, and hope that helps,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110912080445.GA25904@elie">http://lists.debian.org/20110912080445.GA25904@elie