Comment 11 for bug 1657874

I always worry signal changes might have side effects but this patch looks straightforward enough. su_v says the bug is marked Low priority because an easy workaround exists, but that the user impact of this is severe enough to warrant inclusion in the point release. On the basis of the two independent testers' +1s, this is ack'd for landing on 0.92.x for inclusion in 0.92.1. Get it in quickly though.