NiLuJe

It's a 1072x1448 screen @ 300dpi, if that helps ;).

The configure script should never have picked up LIBUUID in the first place, it's part of `util-linux`, which we don't build...

Then again, that's a 7 years old czmq snapshot, so, who knows...

I have a mild hunch that a clean checkout from scratch would work just fine ^^.

It's a design simplification, as this should be an exceedingly rare occurrence in practice. (Also, we also clobber slots on contact losses on some Kobo protocols later, anyway).

> Want me to close this? Not necessarily, base's issue tracker isn't crowded, so leaving this open isn't really problematic. As far as I'm concerned, this would be fairly low...

Could *possibly* be as simple as passing along the fd number from the C module to Lua-land and simply using `fd + ABS_MT_SLOT` in GestureManager, as we don't actually care...

Might need to be slightly more complex, because of the initial state in https://github.com/koreader/koreader/blob/19a607b5484299623cc57563f7a4baa3f49faff5/frontend/device/input.lua#L220-L226 (among possibly other things). If we had a guarantee that the first event device we open...

It would *probably* not be too gnarly to deal with, I just have zero time to devote to this (or anything else, really :/) for the foreseeable future.

There might be a similar issue with cross-device `ABS_MT_TRACKING_ID` values, too (although a collision there is possibly much rarer).