ranger (curses file manager) segfaults. Workaround inside.
Ranger - http://ranger.nongnu.org/ segfaults. The only info I can find about it is commit 1151eb80 which moved ranger to unmaintained due to this segfault.
This is the line which causes the PAX related segfault (`ranger/gui/ui.py`:41 @ranger-git-912e26b4):
# This line solves this problem:
# If a mouse click triggers an action that disables curses and
# starts curses again, (e.g. running a ## file by clicking on its
# preview) and the next key is another mouse click, the bstate of this
# mouse event will be invalid. (atm, invalid bstates are recognized
# as scroll-down, so this avoids an errorneous scroll-down action)
curses.ungetmouse(0, 0, 0, 0, 0)
Commenting it out makes it work fine as far as I can tell, including with the mouse. I didn’t notice a spurious scroll which this line is supposed to prevent, even when trying to trigger the specific case it describes (though I only tested briefly).
Another solution is to completely disable mouse support, e.g. by `set mouse_enabled false` at `ranger/config/rc.conf`.
I didn’t try to investigate further why this call causes a segfault.
(from redmine: issue id 6839, created on 2017-02-10)