Salut,
la capture d’écran parlera mieux que moi 
locale:
J’ai configuré console-setup en UTF-8 et toujours impossible d’avoir la bonne fenêtre…
J’ai cherché sur le net et tous dise pareil, je ne vois pas quoi faire de plus…
et je n’ai que ce problème avec ce VPS… 
J’ai importé la liste des paquets d’un autre VPS et pareil, pas moyen de rétablir ce bug d’affichage…
Si vous avez des suggestions car je sèche un peu…
Merci
Tenter
$ setupcon[mono]con[/mono] de [mono]console[/mono] (non, ce n’est pas le setup Toulousain con ).
$ man setupcon
L’encadrement de la fenêtre fait penser à Microsoft.
Si tu utilises putty sous Microsoft, le préciser ne serait pas un détail à omettre. Voir les réglages de putty.
En effet, c’est dans les options de putty qu’il faut régler le jeu de caractères à UTF-8 pour qu’il corresponde à celui utilisé par Debian. Category “Window”, section “Translation”.
Exact, c’est bien puttY et il est bien réglé.
Remote character set: UTF-8
Use unicode line drawing code points est coché
Choisis aussi [mono]UTF-8[/mono] dans [mono]Putty Configuration[/mono] -> [mono]Window[/mono] -> [mono]Translation[/mono]
(désolé, j’ai pas la traduction française, et j’ai plus windows. Mais tu devrais trouver facilement)
comme dit précédemment, puttY est correctement configuré…
Que ce soit en VM, VPS, cela fonctionne sauf qu’avec celui-ci, non et je ne trouve pas pourquoi…
users.wowway.com/~zlinuxman/putty.htm
Using PuTTY with Debian GNU/Linux Systems
[quote]
this web page is designed to address the environment of PuTTY running under the Microsoft® Windows® operating system and used to login to a remote host which is running Debian GNU/Linux.[/quote]
Il ne s’agit pas vraiment d’«utiliser putty sous debian» mais sous Microsoft. Il y a fort à parier que l’écrasante majorité des debianistes n’utilise JAMAIS putty de $CLIENT_SSH debian à $SERVEUR_SSH…
[quote]
If the application sends VT100 graphic character escape sequences to a terminal which does not support it, such as PuTTY, you will see something 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
instead of something like this:
┌─────────────────────┤ Configuring libssl1.0.0:s390x ├─────────────────────┐
│ This release of OpenSSL fixes some security issues. Services will not │
│ use these fixes until they are restarted. Please note that restarting │
│ the SSH server (sshd) should not affect any existing connections. │
│ │
│ Please check the list of detected services that need to be restarted and │
│ correct it, if needed. The services names must be identical to the │
│ initialization script names in /etc/init.d and separated by spaces. No │
│ services will be restarted if the list is empty. │
│ │
│ Any service that later fails unexpectedly after this upgrade should be │
│ restarted. It is recommended to reboot this host to avoid any │
│ SSL-related trouble. │
│ │
│ Services to restart to make them use the new libraries: │
│ │
│ vsftpd ssh exim4_________________________________________________________ │
│ │
│ <Ok> │
│ │
└───────────────────────────────────────────────────────────────────────────┘
The box-drawing characters can be displayed with PuTTY, but not via VT100 graphic character escape sequences. Instead, the application must send the proper UTF-8 codes to produce the box-drawing characters, just as this web page has done. If you encounter problems such as this, report it as an application bug.
Sometimes, one can get problems such as in the example above during a Debian system upgrade. If the locales package is upgraded, the old version of the package has been removed, the new version of the package is not yet configured, and the locales package is needed to draw a box, you may get results such as above. The problem can usually be circumvented by manually upgrading the locales package first, then upgrading the rest of the system. See Debian bug report 754596 for details. [/quote]
La solution suggérée est de mettre à jour les locales avant de mettre à jour le reste du système.
@etxeberrizahar a pars être en uTF-8 dans les locales, je dois faire quoi ?
dpkg-reconfigure locales a été fait.
dpkg-query -s locales
[quote]Package: locales
Status: install ok installed
Priority: standard
Section: localization
Installed-Size: 15120
Maintainer: GNU Libc Maintainers debian-glibc@lists.debian.org
Architecture: all
Source: eglibc
Version: 2.13-38+deb7u8
Replaces: base-config, lliurex-belocs-locales-data
Depends: glibc-2.13-1, debconf (>= 0.5) | debconf-2.0
Conflicts: base-config, belocs-locales-bin, belocs-locales-data
Conffiles:
/etc/locale.alias f48c7816371493dabaae9fd0d272cccd
Description: Embedded GNU C Library: National Language (locale) data [support]
Machine-readable data files, shared objects and programs used by the
C library for localization (l10n) and internationalization (i18n) support.
.
This package contains the libc.mo i18n files, plus tools to generate
locale definitions from source files (included in this package). It
allows you to customize which definitions actually get
generated. This is a space-saver over how this package used to be,
with all locales generated by default. This created a package that
unpacked to an excess of 30 megs.
Homepage: eglibc.org
[/quote]