On 5 September 2012 07:31, David Cheney <david.cheney at canonical.com> wrote: > Heck, it could be SIGWINCH that's a thought, but i don't think so. my terminal sessions don't generate SIGWINCH signals as there's no WIN to CH. nonetheless i have seen the issue, albeit very occasionally. it would be nice if the error message printed the signal number.