The "not moving at all" problem is bug 1528109, fixed in Mir 0.22.0.
The remaining issue is that the libinput acceleration curve is subjectively not a pleasant one to use, and the cursor soon (non-linearly) moves too quickly. That's bug 1524145 still open. But the fix for that is simple -- we just need to default to acceleration 'off'. Then the cursor will move exactly like it does in Unity7.
The "not moving at all" problem is bug 1528109, fixed in Mir 0.22.0.
The remaining issue is that the libinput acceleration curve is subjectively not a pleasant one to use, and the cursor soon (non-linearly) moves too quickly. That's bug 1524145 still open. But the fix for that is simple -- we just need to default to acceleration 'off'. Then the cursor will move exactly like it does in Unity7.