Hi Axel, On Sun, Jul 03, 2011 at 11:23:20PM +0200, a...@users.sourceforge.net wrote: > Thanks for writing so quickly. Unfortunately I really depend on the > stability of the system so I don't want to install anything that is > not in the stable distribution, so I suppose I'll just have to > wait.
I understand your concern. I'm unlikely to be able to get anything into the stable distribution's updates to fix this though, so if you want to wait it would have to be until Debian Wheezy is released... Would building an updated inputattach.c and testing it, locally, without installing it, meet with your requirements? Just so you can measure the impact, here are the steps involved: 1. Download http://sourceforge.net/projects/linuxconsole/files/linuxconsoletools-1.4.1.tar.bz2/download 2. Extract it, for example to /tmp: cd /tmp tar xjf ${PATH_TO_FILE}/linuxconsoletools-1.4.1.tar.bz2 3. Build inputattach (this requires gcc to be installed to, the version in Debian stable is fine): cd linuxconsoletools-1.4.1/utils make inputattach 4. Kill the running inputattach and run the newly-built version: sudo ./inputattach --daemon -msc /dev/ttyS0 If you don't want to do this, could you tell me if, when you see the failure on the version of inputattach you have installed already, and you try to run it again, does it print an error message? Is there anything in the kernel log which might indicate the source of the problem? There should at least be a message in /var/log/kern.log when the mouse is initially attached, something like input: Microsoft Mouse as /devices/pnp0/00:06/tty/ttyS1/serio2/input/input8 which is what I get with my Microsoft mouse using inputattach. Any other message regarding /dev/ttyS0 on your system may be relevant as well. Thanks in advance, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
