Open rappie opened 10 months ago
Possibly related:
echidna: user error (Terminal does not define required capability "sgr0")
Is this solved in 2.2.3?
I have not had these TERM related errors for a while now since updating to the latest version
Great, let's close. Feel free to reopen if you see these again.
echidna: user error (Terminal does not define required capability "clear")
Just had this one. Should we reopen it or create a new issue?
Let's reopen, I'm not sure what can be the cause but we will be updating terminal-related dependencies soon (https://github.com/crytic/echidna/issues/1198) so it might get resolved.
@rappie if you're able to reproduce it, can you check if running stty sane
or tput reset
on the terminal help fix it?
I've only had it once so far, but I regularly get a situation where CTRL+C is not working anymore after running Echidna. If I press it, the ^C character appears but it does not stop/cancel anything, it is just a character that I can remove with backspace.
To fix it, I do reset
. I assume this is the same as tput reset
?. I will try your commands next time.
echidna: no back color support for terminal screen.xterm-256color
CallStack (from HasCallStack):
error, called at src/Graphics/Vty/Output/TerminfoBased.hs:127:32 in vty-5.38-t4uBxudScr4gwaMP3IHWw:Graphics.Vty.Output.TerminfoBased
Just had the exact same error as mentioned in the original issue. It is very rare now though.
Describe the issue:
This happens very rarely at random moments. No way to reproduce.
Might be similar to the earlier "cups" error I kept getting in the past.
Version:
Latest 2.2.1
master
built withnix-env
.Relevant log output: