I have encountered this bug too, and have investigated further.
The problem is caused by ttytter's use of SIGPWR to communicate between the backend and frontend. As soon as this signal is sent, the frontend is killed with a "Power failure" error.
I have made the author of ttytter aware of this and he is going to look at other methods of signalling.
I suggested using SIGUSR1, but apparently that causes breakage if ttytter is used with Term::ReadLine::TTYtter.
(I don't use Term::ReadLine::TTYtter, and altered the program to use SIGUSR1, which now runs correctly).
-- Dom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
