[Bug]: Ncurses apps with mouse\touch-events using `mouseinterval(0)`\"disabled click resolution" malfunction since bump(main/ncurses): 6.6.20260124

[GiorgosXou]

Problem description

What the title says. It used to simply have no effect at all but as of bump 6.6 it spits out bad mouse events and messes up things. see also GiorgosXou/TUIFIManager#134 (comment)

What steps will reproduce the bug?

Using version-6.6 simply try this minimal example with mouseinterval(0) set above the mousemask(...) line. Try the same thing with 6.5

What is the expected behavior?

(As far as my termux-knowledge goes in terms of how it handles touch events) the excpected behaviour should be the exact same as if there wasn't mouseinterval(0) written at all. Simply put, it should ignore this call, unless the issue is deeper or the touch-events get translated differently when full-GUI-OSs are present.

System information

(using an old version of termux cause I thought that might was the issue all along...)

TERMUX_APK_RELEASE=GITHUB
TERMUX_APP_PACKAGE_MANAGER=apt
TERMUX_APP_PID=16765
TERMUX_IS_DEBUGGABLE_BUILD=1
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.0
TERMUX__USER_ID=0
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://mirror.albony.in/termux/termux-main stable main
Updatable packages:
All packages up to date
termux-tools version:
1.45.0
Android version:
14
Kernel build information:
Linux localhost 3.18.140-g7e4449cf0358 #1 SMP PREEMPT Thu Jun 20 23:02:18 UTC 2024 aarch64 Android
Device manufacturer:
samsung
Device model:
SM-G930F
Supported ABIs:
SUPPORTED_ABIS: arm64-v8a,armeabi-v7a,armeabi
SUPPORTED_32_BIT_ABIS: armeabi-v7a,armeabi
SUPPORTED_64_BIT_ABIS: arm64-v8a
LD Variables:
LD_LIBRARY_PATH=
LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec-ld-preload.so

[robertkirkman]

I have reproduced this, and I have bisected it to this commit,

ThomasDickey/ncurses-snapshots@04b97b0#r169954711

meaning, that the last version of ncurses that does not have this problem is this commit:

ThomasDickey/ncurses-snapshots@5f58399

unfortunately I don't know how that can easily be reverted in the newest version, and also, the solution used by OpenSUSE of bumping to the newest version of ncurses does not seem to solve it in Termux.

Maybe the Termux package of ncurses should be reverted to version 6.6.20260124+really6.5.20250830 to fix this problem in the short term.

[fornwall]

Maybe the Termux package of ncurses should be reverted to version 6.6.20260124+really6.5.20250830 to fix this problem in the short term.

👍 Sounds good to temporarily go back to an older version until the problem is fixed.

Is the problem specific to using the termux terminal (and not when e.g. ssh:ing into termux from other terminals)? Perhaps there is an issue with the terminal emulation in termux - I'll have a look.

[robertkirkman]

Maybe the Termux package of ncurses should be reverted to version 6.6.20260124+really6.5.20250830 to fix this problem in the short term.

👍 Sounds good to temporarily go back to an older version until the problem is fixed.

Is the problem specific to using the termux terminal (and not when e.g. ssh:ing into termux from other terminals)? Perhaps there is an issue with the terminal emulation in termux - I'll have a look.

Yes, as far as I could tell, the problem is not reproducible when connected to Termux remotely using SSH.

[TomJo2000]

As I understand it the issue was first reported on OpenSuSE Tumbleweed.
This seems to be a generally reproducible regression.

[robertkirkman]

Can be closed when a way to update to ncurses 6.6+ without causing the issue is found