Bug#754596: libc6 package upgrade sends ISO-2022 escape sequences to a terminal which doesn't support them (PuTTY in UTF-8 mode)
On 2014-07-12 23:30 +0200, Stephen Powell wrote:
> The problem occurs when libc6 must be upgraded during "apt-get upgrade"
> or "apt-get dist-upgrade". I see a screen which looks like this:
>
> -----
>
> lqqqqqqqqqqqqqqqqqqqqqqqqu Configuring libc6:s390x tqqqqqqqqqqqqqqqqqqqqqqqqk
> x Running services and programs that are using NSS need to be restarted, x
> x otherwise they might not be able to do lookup or authentication any more x
> x (for services such as ssh, this can affect your ability to login). x
> x Please review the following space-separated list of init.d scripts for x
> x services to be restarted now, and correct it if needed. x
> x x
> x Note: restarting sshd/telnetd should not affect any existing x
> x connections. x
> x x
> x Services to restart for GNU libc library upgrade: x
> x x
> x vsftpd exim4 cron atd____________________________________________________ x
> x x
> x <Ok> x
> x x
> mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
>
> -----
>
> As you can see, PuTTY was sent the traditional ISO-2022 box-drawing escape
> sequences to draw the box, which does not work when PuTTY is operating in
> UTF-8 mode. These need to be converted into equivalent UTF-8 sequences to
> look right. I wish to emphasize that libc6 is the *only* package which does
> this.
Seems logical, see below.
> If the bug is not in package libc6, then why is libc6 the *only* package
> which doesn't use the proper box-drawing technique?
Because your UTF-8 locale isn't available at the time the above screen
is shown. It comes from the libc6 preinst, and libc6 declares a Breaks
on the old locales package (see #585737 for details).
Cheers,
Sven
Reply to: