Comment 1 for bug 1595607

I am quite willing to work on this issue, but... don't make me jump through hoops just to see the crash report. (Take an example from Fedora, where such reports are freely accessible (for example, https://retrace.fedoraproject.org/faf/reports/1181921/). I don't need heaps of information -- a backtrace is normally enough.)

Anyway, I'm guessing your users are hitting a bug that is fixed by the first patch attached to this message: https://lists.gnu.org/archive/html/nano-devel/2016-04/msg00075.html. That patch (and the other three) were already applied to nano in Debian.