Getting error when ran btop

[Vansh0134]

awh thanks <3

one more thing i was getting this error when ran btop

ERROR: No UTF-8 locale detected!
Use --utf-force argument to force start if you're sure your terminal can handle it.

[NaN]

@Vansh0134

Use --utf-force argument

Yes, you need to use the --utf-force flag to launch btop in terminal emulator. It works without this flag in a TTY but not in terminal emulator. I am not sure about the specific reason behind that but you can just make this an alias in you shell’s rc.

alias btop="btop --utf-force"

For fish this file is in

~/.config/fish/config.fish

and for bash,

~/.bashrc

[BluishHumility]

@NaN

Yes, you need to use the --utf-force flag to launch btop in terminal emulator.

Wait, what? I do not get this message when launching btop.

This might be a stupid question, but do you guys have a UTF-8 locale set? Check:

locale

If not, uncomment one in /etc/locale.gen and then regenerate the locale:

sudo locale-gen

[NaN]

Yes just checked and you were right.

[BluishHumility]

Does it come that way out of a fresh install? Maybe depending on the language selected in Calamares? I wonder if we should make a change somewhere so it sets a UTF-8 locale by default.

According to the ArchWiki:

• UTF-8 is recommended over other character sets. [2]

[NaN]

@BluishHumility

Does it come that way out of a fresh install?

I believe that depends on the locale you choose while installing. I have en_IN as my locale.

/etc/locale.gen

###
#
# Locales enabled by Calamares
en_IN UTF-8
en_US.UTF-8 UTF-8

locale
LANG=en_IN
LC_CTYPE="en_IN"
LC_NUMERIC=en_IN
LC_TIME=en_IN
LC_COLLATE="en_IN"
LC_MONETARY=en_IN
LC_MESSAGES="en_IN"
LC_PAPER=en_IN
LC_NAME=en_IN
LC_ADDRESS=en_IN
LC_TELEPHONE=en_IN
LC_MEASUREMENT=en_IN
LC_IDENTIFICATION=en_IN
LC_ALL=

[BluishHumility]

@NaN

# Locales enabled by Calamares
en_IN UTF-8
en_US.UTF-8 UTF-8

Hmm, it does say UTF-8 next to it though. But not with a period like the en_US one. I guess I am realizing I don’t really know how to read these values.

It does seem that UTF-8 has some advantages as a character set: ubuntu - Linux locale: en_US.UTF-8 vs en_US - Server Fault

Still, choosing a “not correct” language just to get a better character set would be insane I think. I guess I’m not sure what a good solution would be.