(It seems like this problem only just arose in the weeks since the middle of June, maybe more recently, but at least a month ago.)
I often find them replaced by other characters, as in the attachment. The SS is from Tumbleweed, but it happens also in Leap, and also in KDE3's Konsole. Is this an absence of some specific font? If not, what needs to be differently configured for Konsole to always use boxdraw characters when an app or utility is supposed to be using them when used in Konsole?
What follows is all from one multiboot PC:
# grep RETT /etc/os-release PRETTY_NAME="openSUSE Tumbleweed" # wpctl status PipeWire 'pipewire-0' [0.3.75, root@ab250, cookie:1948030365] ââ Clients: 31. WirePlumber [0.3.75, root@ab250, pid:850] 32. WirePlumber [export] [0.3.75, root@ab250, pid:850] 47. PipeWire ALSA [tdeinit] [0.3.75, root@ab250, pid:1086] 48. wpctl [0.3.75, root@ab250, pid:1371]
Audio ââ Devices: â 38. Built-in Audio [alsa] â ââ Sinks: â * 39. Built-in Audio Analog Stereo [vol: 0.46] â ââ Sink endpoints: â ââ Sources: â 40. Built-in Audio Analog Stereo [vol: 1.00] â ââ Source endpoints: â ââ Streams:
Video ââ Devices: â ââ Sinks: â ââ Sink endpoints: â ââ Sources: â ââ Source endpoints: â ââ Streams:
Settings ââ Default Configured Node Names: # systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character.
graphical.target @4.115s `-multi-user.target @4.114s `-kbdsettings.service @2.052s +2.062s `-basic.target @2.045s `-sockets.target @2.045s `-telnet.socket @2.044s `-sysinit.target @2.014s `-wtmpdb-update-boot.service @1.802s +138ms `-systemd-tmpfiles-setup.service @1.724s +43ms `-local-fs.target @1.723s `-run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.728s `-local-fs-pre.target @1.105s `-systemd-tmpfiles-setup-dev.service @864ms +66ms `-kmod-static-nodes.service @524ms +80ms `-systemd-journald.socket `-system.slice `--.slice #
# grep RETT /etc/os-release PRETTY_NAME="Fedora Linux 38 (Thirty Eight)" # wpctl status PipeWire 'pipewire-0' [0.3.77, root@ab250, cookie:1539572309] └─ Clients: 31. WirePlumber [0.3.77, root@ab250, pid:849] 32. WirePlumber [export] [0.3.77, root@ab250, pid:849] 47. artsd [0.3.77, root@ab250, pid:1026] 53. PipeWire ALSA [tdeinit] [0.3.77, root@ab250, pid:1088] 54. wpctl [0.3.77, root@ab250, pid:1240]
Audio ├─ Devices: │ 38. Built-in Audio [alsa] │ ├─ Sinks: │ * 39. Built-in Audio Analog Stereo [vol: 0.46] │ ├─ Sink endpoints: │ ├─ Sources: │ 40. Built-in Audio Analog Stereo [vol: 1.00] │ ├─ Source endpoints: │ └─ Streams:
Video ├─ Devices: │ ├─ Sinks: │ ├─ Sink endpoints: │ ├─ Sources: │ ├─ Source endpoints: │ └─ Streams:
Settings └─ Default Configured Node Names: #
# grep RETT /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" # wpctl status Could not connect to PipeWire # systemd-analyze critical-chain ... graphical.target @2.171s └─watchdog.service @2.156s +14ms └─multi-user.target @2.137s └─smbd.service @2.026s +110ms └─nmbd.service @1.779s +246ms └─basic.target @1.748s └─sockets.target @1.748s └─dbus.socket @1.747s └─sysinit.target @1.737s └─systemd-timesyncd.service @1.653s +81ms └─systemd-tmpfiles-setup.service @1.550s +43ms └─local-fs.target @1.493s └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.562s └─local-fs-pre.target @849ms └─keyboard-setup.service @313ms +364ms └─systemd-journald.socket @295ms └─system.slice @253ms └─-.slice @253ms #