On Wed, 27 Jul 2016 12:41:24 +0200 Vincent Lefevre wrote: > Package: apt-listbugs > Version: 0.1.18 > Severity: normal
Hello Vincent and thanks for your bug report! > > When I run aptitude, start an upgrade, then hit Ctrl-C just after > apt-listbugs is started, I get: > > root@zira:/home/vinc17# aptitude > Interruptedactions... > Faileving bug reports... 0%^C > Error retrieving bug reports from the server with the following error message: > E: exit > It could be because your network is down, or because of broken proxy servers, > or the BTS server itself is down. Check network configuration and try again > Retry downloading bug information? [Y/n] > root@zira:/home/vinc17# This was somewhat intended: hitting [Ctrl-C] was supposed to interrupt the bug report retrieval, while giving the user a chance to decide what to do (retry and/or aborting and/or going on with the installation/upgrade)... > > but apt-listbugs is still running and attached to the terminal: > > UID PID PPID C STIME TTY TIME CMD > root 702 701 1 12:36 pts/6 00:00:00 /usr/bin/ruby > /usr/sbin/apt-listbugs apt ... this is instead unexpected! I managed to reproduce the misbehavior, but I have no idea why it happens. :-( The shell prompt should not reappear, while apt-listbugs is still running! > > Now, if I type Return, it is grabbed by apt-listbugs though I have > my shell prompt, and I get an additional error message: > > root@zira:/home/vinc17# aptitude > Interruptedactions... > Faileving bug reports... 0%^C > Error retrieving bug reports from the server with the following error message: > E: exit > It could be because your network is down, or because of broken proxy servers, > or the BTS server itself is down. Check network configuration and try again > Retry downloading bug information? [Y/n] > root@zira:/home/vinc17# E: Input/output error @ io_fillbuf - fd:0 <STDIN> > This is even more awkward: I tried to understand where this error is coming from, but I haven't yet succeeded. Anyway, I am considering the possibility to change the "exit 130" statement into "exit! 130" at /usr/bin/apt-listbugs:325 That way, a [Ctrl+C] would make apt-listbugs exit (unsuccessfully) immediately, without asking the user what to do. But, at least, it seems that it would not trigger the strange behavior you experienced. I'll let you know, as soon as I make up my mind. Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpG8YNN7TJdv.pgp
Description: PGP signature
