[Reportbug-maint] Bug#548533: reportbug: Ctrl+c doesn't exit until after pressing enter

[Sandro Tosi]

clone 548533 -1
reassing -1 libreadline6
retitle -1 libreadline6: break reportbug Ctrl+c
block 548533 by -1
thanks

Hello libreadline6 maintainer,
the library broke the Ctrl+c in reportbug, so now we have to Ctrl+c +
ENTER to let the program exit (instead of just Ctrl+c). Information
about the packages that broke reportbug are below, and the bug is
easily replicable. If you need any further information, just ask.

Regards,
Sandro

On Sat, Oct 31, 2009 at 22:38, Josh Triplett <josh at joshtriplett.org> wrote:
> On Sat, Oct 31, 2009 at 08:14:31PM +0100, Sandro Tosi wrote:
>> Hi Josh,
>> thanks for your report.
>>
>> On Sat, Sep 26, 2009 at 21:56, Josh Triplett <josh at joshtriplett.org> wrote:
>> > Package: reportbug
>> > Version: 4.8
>> > Severity: normal
>> >
>> > Reportbug says:
>> > Please briefly describe your problem (max. 100 characters allowed; you can elaborate in a moment; an empty response will stop reportbug). This will be the bug
>> > email subject, so write a concise summary of what is wrong with the package, for example, "fails to send email" or "does not start with -q option specified"
>> > (enter Ctrl+c to exit).
>> >>
>> >
>> > However, pressing Ctrl+c does not exit until after I subsequently press
>> > enter.
>>
>> Yeah, I see the same behavior, but bisecting reportbug code, up to
>> known working branch (4.6, for example), does not trigger any
>> implementation error, and even old versions are showing that behavior.
>>
>> I first thought about python2.5 upgrade, but even with 2.5.4-1 I got
>> the same situation. I fear it's something related to libreadline{5,6}.
>>
>> Last lines of 'which-pkg-broke reportbug' returns:
>>
>> python-reportbug                                       Wed Sep 16 23:06:08 2009
>> reportbug                                              Wed Sep 16 23:06:09 2009
>> install-info                                           Mon Oct  5 19:31:23 2009
>> dpkg                                                   Mon Oct  5 19:32:02 2009
>> apt                                                    Mon Oct  5 19:32:33 2009
>> readline-common                                        Mon Oct  5 19:32:56 2009
>> libreadline6                                           Mon Oct  5 19:33:00 2009
>> gpgv                                                   Mon Oct  5 20:22:50 2009
>> gnupg                                                  Mon Oct  5 20:22:53 2009
>> coreutils                                              Mon Oct  5 20:31:37 2009
>> libncurses5                                            Tue Oct  6 19:19:04 2009
>> zlib1g                                                 Tue Oct  6 19:24:47 2009
>> python2.5                                              Sat Oct 31 10:03:06 2009
>> python2.5-minimal                                      Sat Oct 31 10:03:10 2009
>>
>> Can you confirm you upgraded readline stuff around the time this issue shown up?
>
> I don't know exactly when the issue showed up.  However, readline seems
> like a likely culprit indeed.  Some searches turned up various reports
> of similar issues (ctrl-c not working until after a newline) as old as
> 2006.  The issue seems to relate either to readline or the way a program
> uses readline.
>
> - Josh Triplett
>



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi