[Aptitude-devel] Bug#466594: Uncaught exception: Unable to read from stdin: Success

[Daniel Hartwig]

On 8 February 2013 20:58, Matthias Fritzsche <txt.file at txtfile.eu> wrote:
> Package: aptitude
> Version: 0.6.9.1-1
> Followup-For: Bug #466594
>
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
>
>    * What led up to the situation?
>    I am running a ssh session (from windows with kitty) to my debian box
>    when I got this error.
>
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    I run aptitude and did open the search dialog. Then I pressed
>    accidently the german ß key which, for unknown reasons, is not
>    displayed as this char. Therefore aptitude does receive a unknown
>    char or some other weird stuff.

What is the effective locale in the ssh session set up by kitty?
Please provide the output from:

  $ locale

just before you would run aptitude.

Also, does typing ‘ß’ in the shell produce the expected output?

>    * What was the outcome of this action?
>    Right after aptitude receives the key code it crashed with given
>    error message.

Does that error message include the line:

  sh: reportbug: command not found

>
>    * What outcome did you expect instead?
>    aptitude does not crash but ignore the received keys or show a ? as
>    with most other special characters which I tried (including german
>    big ß (ẞ))
>
>    * I reported this bug also to the developer of kitty because
>    I think that it sends the wrong key code for this character. I have
>    not found another way to reproduce this error except using putty
>    which is the same code base.

There are reports of similar problems with putty.  Perhaps this is related.

Regards