And did you plug in a new HID device?
Yes. Just to be clear, nothing untoward happens with usbhid.ko simply loaded, e.g directly via
modprobe or automagically when a device is plugged in. But the first event, be it a mouse movement
or a keystroke, causes particular applications to crash. I've tried various different USB hardware
(including putting a hub in between) and the result is always the same.
Can you test Linux 3.4, available from the experimental suite? If that
still has the problem, we can pass this on to the upstream developers;
if not, we can try to work out where it was fixed.
Yes. I've now installed linux-3.4-trunk-amd64 from Debian experimental, and the same thing happens,
reliably every time.
For reference, when I just now crashed both cairo-dock and audacious from the same mouse movement
(apparently), they report the following, with different addresses. I don't know what that means, if
anything.
*** glibc detected *** audacious: malloc(): memory corruption:
0x0000000000f167d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x75b46)[0x7f6357659b46]
/lib/x86_64-linux-gnu/libc.so.6(+0x78bb3)[0x7f635765cbb3]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x70)[0x7f635765e960]
*** glibc detected *** cairo-dock: malloc(): memory corruption:
0x00007f3fcc284020 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x75b46)[0x7f3fe1e77b46]
/lib/x86_64-linux-gnu/libc.so.6(+0x78bb3)[0x7f3fe1e7abb3]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x70)[0x7f3fe1e7c960]
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ffb1008.2040...@annaghvarn.plus.com
