Hm, it could be related. But the problem is more like comment #4 than
the original comment, as we're not running gpm and it takes a lot longer
than 4 seconds to un-hang. If the patch attached to that bug is not
already in the 4.3.0 patches, I could try it out and see what happens.
On Fri, Aug 1
Hm, it could be related. But the problem is more like comment #4 than
the original comment, as we're not running gpm and it takes a lot longer
than 4 seconds to un-hang. If the patch attached to that bug is not
already in the 4.3.0 patches, I could try it out and see what happens.
On Fri, Aug 1
On Sat, 2003-08-09 at 02:21, Ari Pollak wrote:
>
> I have configured Debian X 4.2.1 packages on a group of machines here
> such that two mice are configured - one on /dev/psaux, and one on
> /dev/input/mice, both configured as ImPS/2 and with core events. This
> worked fine when either port di
On Sat, 2003-08-09 at 02:21, Ari Pollak wrote:
>
> I have configured Debian X 4.2.1 packages on a group of machines here
> such that two mice are configured - one on /dev/psaux, and one on
> /dev/input/mice, both configured as ImPS/2 and with core events. This
> worked fine when either port di
[ Please CC me on all replies ]
I have configured Debian X 4.2.1 packages on a group of machines here
such that two mice are configured - one on /dev/psaux, and one on
/dev/input/mice, both configured as ImPS/2 and with core events. This
worked fine when either port did not have a mouse connect
[ Please CC me on all replies ]
I have configured Debian X 4.2.1 packages on a group of machines here
such that two mice are configured - one on /dev/psaux, and one on
/dev/input/mice, both configured as ImPS/2 and with core events. This
worked fine when either port did not have a mouse connect
6 matches
Mail list logo
