In Void Linux, when I use Midnight Commander in tty with themes which support double-line box characters (like darkfar or double-lines), those box characters are substituted with rectangles, and this ruins apperance a little bit, so to say. In other distros (Debian/Devuan, Gentoo), those double-line box characters in tty are replaced with single-line ones, which is OK. I use the same config across all distros. In tty, terminus font is used.

In /etc/rc.conf, I specify:

KEYMAP="ruwin_alt_sh-UTF-8"
FONT="ter-v16b"

Locale is set to en_IE.UTF-8.

So, that's the question: what do I need to do in order to fix this issue? Maybe, I need to specify certain font map/inimap? At the same time, I need that Russian keyborad layout and also support for Cyrillic symbols in UTF in the tty, so that not every keymap would satisfy my needs, I presume?

Kernel: 7.2.2_1

[loginctl suspend] works fine.

What I've tried:

1] Disable acpid

2] Uncommented options in [Sleep] section of [/etc/elogind/sleep.conf]

3] [resume=UUID=] in kernel commandline options. Using a swap partition

4] using ZZZ -H and ZZZ

- command executed from within [sway]. Got mixed results from outside of sway in tty. Sometimes it will work, but there is no consistency. Starting sway with [dbus-run-session] does not help.

- svlogtail returns:

e-hybrid-sleep[1637]: Entering sleep state 'hybrid-sleep'...
e-hybrid-sleep[1637]: System returned from sleep state.
e-hybrid-sleep[1637]: Operation 'hybrid-sleep' finished.

- system frozen and I usually magic SysRq REISUB to reboot system.

- running services:

acpid  
agetty-tty1-6 
chronyd  
cronie  
dbus  
dhcpcd  
irqbalance  
rtkit  
runit-swap  
socklog-unix  
udevd  
vnstatd

I have started to see a lot of content about Void linux in my feed recently. And I do not understand the hype it is getting. Not that I tried it but it just seems like any other distros. What am I missing here or not missing?

Hi, I have been running void for half a year now and all is great, except for the issue with internet connection. It happens when I try to connect to institutional wifi.

The NM applet shows "Configuring interface" and after a while a password-demanding pop-up shows up. After entering my password (The correct one, I`ve checked) the cycle repeats.

I use kde with NetworkManager.
This is my NM config file:

[main]
plugins=keyfile
#,ifupdown

# [ifupdown]
# managed=false

[device]
wifi.scan-rand-mac-address=no
wifi.backend=wpa_supplicant
# wifi.backend=iwd

These are the logs that precede the inevitable disconnect/password pop-up:

NetworkManager[1188]: <info>  [1788260270.8272] device (wlp3s0): supplicant interface state: disconnected -> authenticating
 NetworkManager[1188]: <info>  [1788260270.8273] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> authenticating
 NetworkManager[1188]: <info>  [1788260270.8651] device (wlp3s0): supplicant interface state: authenticating -> associating
 NetworkManager[1188]: <info>  [1788260270.8652] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating
 NetworkManager[1188]: <info>  [1788260270.9685] device (wlp3s0): supplicant interface state: associating -> associated
 NetworkManager[1188]: <info>  [1788260270.9686] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> associated
 NetworkManager[1188]: <warn>  [1788260295.8480] device (wlp3s0): Activation: (wifi) association took too long
 NetworkManager[1188]: <info>  [1788260295.8480] device (wlp3s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
 NetworkManager[1188]: <warn>  [1788260295.8484] device (wlp3s0): Activation: (wifi) asking for new secrets
 NetworkManager[1188]: <info>  [1788260295.9028] device (wlp3s0): supplicant interface state: associated -> disconnected
 NetworkManager[1188]: <info>  [1788260295.9029] device (p2p-dev-wlp3s0): supplicant management interface state: associated -> disconnected

I have tried the official python script for eduroam network, iwd. Both 'solutions' didn`t work.
This issue also existed on arch installation. Is there anything else I can try?

Is this issue a hardware one? If it is, what can I do?

If necessary, I can provide additional/full logs.
Thanks.