> > > Change that 1 to 0 and key events are passed on to pbbuttonsd (I imagine
> > > the mouse register device call needs the same change to let pbbuttonsd
> > > react to mouse moves).
> >
> > I have tested this and after restarting both mouseemu and pbbuttonsd, i
> > got the pbbuttonsd keys back. This seems to fix #307068 as well.
>
> pbbuttonsd must be started after mouseemu for this to work, and #307068
Paul,
Do you use devfs/devfsd? Otherwise, please look at /dev/input to see how
many event%d devices you have. My setup had only four event devices which
were just enough for the builtin devices ... took me a while and evbug to
figure out just how many devices were in the game, and what device the
passthrough events came from.
pbbuttonsd relies on special files present in /dev/input (or devfsd making
them up on the fly) to scan for keyboard devices. In my case, the
specials for the virtual (uinput) devices weren't present, so the devices
were never registered.
With this change, and mouseemu (original 0.15) started before pbbuttonsd
(original 0.6.6 with some syslog() crap added) I get normal behavior of
both tools. When you start mouseemu after pbbuttonsd you may need to do a
/etc/init.d/mouseemu reload which rescans the event devices.
One minor nit with pbbuttonsd remains: stopping and restarting pbbuttonsd
loses all visual feedback for event response until the next login. Must
be X related.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
