Hi Jonathan,
Thanks. The `xinput list` output shows that my proposed Ignore section did
not actually remove /dev/wsmouse:
TrackPoint and buttons id=6
/dev/wsmouse0 id=8
/dev/wsmouse1 id=9
/dev/wsmouse id=10
So this was not yet a clean test of wsmouse0 plus wsmouse2. The multiplexor
remained active, and that would explain why every movement now causes a
jump: X is receiving the direct device events as well as the multiplexed
copy. Could you try, in that same X session: xinput disable 10 and then
test the touchpad, its buttons and the TrackPoint again?
I would also disable /dev/wsmouse1, since that was the secondary HID
interface which failed to enter native mode in the original Xorg log:
xinput disable 9. The intended state is therefore:
TrackPoint and buttons enabled
/dev/wsmouse0 enabled
/dev/wsmouse1 disabled
/dev/wsmouse disabled
If everything works in that state, then opening wsmouse2 directly is
probably fine and the remaining question is why the two Ignore sections
were not applied. Could you also check the new Xorg.0.log for lines
mentioning:
ignore wsmouse mux
/dev/wsmouse1
/dev/wsmouse
Applying InputClass
That should show whether X matched the Ignore section at all. Sorry, I
should have noticed that the presence of /dev/wsmouse in `xinput list`
meant the proposed exclusion had not taken effect.
Regards,
Kihaguru
On Wed, 5 Aug 2026, 07:35 Jonathan Thornburg, <[email protected]>
wrote:
> Hi Kihaguru,
>
> On Tue, Aug 04, 2026 at 05:53:55PM +0300, Kihaguru Gathura wrote:
> > Perhaps the next test is to ignore the multiplexed /dev/wsmouse, but open
> > /dev/wsmouse2 directly:
> >
> > Section "InputClass"
> > Identifier "ignore wsmouse mux"
> > MatchDevicePath "/dev/wsmouse"
> > Option "Ignore" "true"
> > EndSection
> >
> > Section "InputDevice"
> > Identifier "TrackPoint and buttons"
> > Driver "ws"
> > Option "Device" "/dev/wsmouse2"
> > Option "AutoServerLayout" "true"
> > EndSection
> >
> > This would leave /dev/wsmouse0 handling the touchpad through synaptics,
> > while /dev/wsmouse2 handles the TrackPoint and its buttons without going
> > through the multiplexor.
> >
> > After restarting X, does `xinput list` show both /dev/wsmouse0 and the
> > separately configured wsmouse2, but not /dev/wsmouse?
>
> --- begin `xinput list` output ---
> + Virtual core pointer id=2 [master pointer
> (3)]
> | + Virtual core XTEST pointer id=4 [slave pointer
> (2)]
> | + TrackPoint and buttons id=6 [slave pointer
> (2)]
> | + /dev/wsmouse0 id=8 [slave pointer
> (2)]
> | + /dev/wsmouse1 id=9 [slave pointer
> (2)]
> | + /dev/wsmouse id=10 [slave pointer
> (2)]
> + Virtual core keyboard id=3 [master keyboard
> (2)]
> + Virtual core XTEST keyboard id=5 [slave keyboard
> (3)]
> + /dev/wskbd id=7 [slave keyboard
> (3)]
> --- end `xinput list` output ---
>
> > If so, it would be interesting to see whether the touchpad, buttons and
> > TrackPoint then work without the jumps.
>
> In this state,
> * the touchpad buttons all work fine
> * but now *every* movement of the trackpoint or touchpad causes the cursor
> to jump:
> - a horizontal movement causes the cursor to jump to the left screen edge
> - a vertical movement causes the cursor to jump to the top screen edge
> - any other (diagonal) movement causes the cursor to jump to the left
> edge, the top edge, or the top left corner; which of these it is seems
> * this behavior is the same between twm (base) and ctwm (ports)
>
> > I haven't tested this particular setup, so please keep the previous
> > xorg.conf handy in case X does not add wsmouse2 this way.
>
> Yes indeed!
>
> ciao, -- Jonathan
>
