Sorry @j4james, I’m just trying to imply that I didn’t put a full measure of thought into my fix-strategy for this yet and am just heuristically answering based on the text content of this discussion.

I’ve assigned it to myself to investigate in full either later today or tomorrow and come up with a suitable proposal, whether that’s a fix on the surface or a fix in depth which likely, in some form, will use saturating math. I just need some time to think about it and I haven’t had any yet. I’m trying to burn out the giant list of PRs that people want my attention on.

I have the same issue when I connect from my Win terminal with ssh to another box (pure linux). After entering a correct pass the app crashes. Reading the comments I may add that after I log into another box I get a neofetch info…

You know, there was discussion of some other related crashes (namely in printf "\e[999999999L") in this thread, but those look like they’ve been fixed in the meantime as well. Unclear when exactly. But the OP, and the follow-up crashes have been fixed, so I’m gonna close this one out.

As a user (store-installed), I just want to thank everybody for the work here. Much appreciated!

I wasn’t sure what was happening the other day when Terminal started crashing but running the Ubuntu app (also store-installed) still worked. Ubuntu was my default-opening tab, neofetch was running as part of .bashrc, womp womp…

I blasted my old profiles JSON, discovered the blog post saying it needed to be updated to the current format anyway, and when that didn’t work I started commenting out .bashrc lines until I found the offending one (neofetch). Leading me to here, where I’m delighted to find this thread I can subscribe to.

Thanks again.