This started when the new-style apt got installed. screen is running on another sid with its child ttys each ssh’ed into a remote deb. it may occurr under any UTF-8 locale, but I only ever use en_US.UTF-8 and more recently C.UTF-8, but I’ve not switched everything over yet. urxvt itself is running on a gentoo box, if relevant. (Also using en_US.UTF-8.) (Also, if relevant, all of the remotes are xen or kvm.)
Am Sun, Jul 21, 2024 at 11:02:18PM GMT, schrieb cloos@jhcloos.com: perhaps with a copy&paste or a screenshot. If APT runs with an UTF-8 codeset it now uses utf8 block characters, if it isn't it falls back to the "old" style of using #. The code is here: https://salsa.debian.org/apt-team/apt/-/blob/main/apt-pkg/install-progress.cc?ref_type=heads#L346-367 The block characters are btw: ▏ ▎ ▍ ▌ ▋ ▊ ▉ █ as in: those chars including & following "U+2588 FULL BLOCK" So, honestly, I don't see much opportunity for apt to be wrong here and would guess its either your transit layers messing up or your chosen font not supporting these characters; but I am happy to be proven wrong given utf8 isn't my expertise. Best regards David Kalnischkies
they do not remain to copy and paste, but the progress is using an accented miniscule a. it *may* have been U+E2 LATIN SMALL LETTER A WITH CIRCUMFLEX. the boxes for “overlays” also fail to use the actual block chars. and instead get what look like chars from U+80 TO U+FF. screen is explicitly run with -U and all of the locales are .UTF-8 . and everything else works correctly.