Closed Mte90 closed 8 months ago
I have this same issue since a few days, on debian testing.
If this can be helpful these are the last errors in journalctl
:
dic 06 16:23:23 KITT nccm[98608]: <DEBUG> (2023-12-06 16:23:23.738 , PN: MainProcess , MN: nccm , FN: LogPositions , LI: 1848 , TN: MainThread): Comment == Enter key , self.Name = ConnectionsList , self.YOff>
dic 06 16:23:23 KITT nccm[98608]: <DEBUG> (2023-12-06 16:23:23.738 , PN: MainProcess , MN: nccm , FN: GetCommandLine , LI: 1656 , TN: MainThread): SelectedEntry = <__main__.ServerXS object at 0x7f781a8d9690>
dic 06 16:23:23 KITT nccm[98608]: <DEBUG> (2023-12-06 16:23:23.738 , PN: MainProcess , MN: nccm , FN: GetCommandLine , LI: 1713 , TN: MainThread): ServerXSNum (this is the connection list line number) == 0 ,>
lines 19198
I'm trying to investigate more, for now what I can say is that evidence points to Ncurses patch 20231121 breaking NCCM
https://invisible-island.net/ncurses/NEWS.html#index-t20231121
NCCM broke when I updated ncurses-related packages from 6.4+20231016-1
to 6.4+20231121-1
(in debian's versioning system) so the breaking patch must be one of those in there, at least.
I can confirm that, at least as a stopgap measure, downgrading ncurses work
on Debian, for example:
sudo apt install libncurses6=6.4-4 libncursesw6=6.4-4 libtinfo6=6.4-4 ncurses-bin=6.4-4
I've found the problem and suggested a fix here: https://github.com/flyingrhinonz/nccm/pull/24
Would appreciate if you could test it!
After selecting the server I am getting this error:
I don't see a requirements.txt orr pyproject.toml so I can't check the dependencies I need or the version I have is compatible.