[solved] Sudo localization

Cvlc · 2023-07-11 15:43:25

Hi,

I just noticed that the "wrong password" password prompt is not localized on my system, when the regular password prompt is properly translated to french. Can this be due to some improper configuration, or is it a bug ? Or is this more related to PAM than sudo ?

$ sudo -i
[sudo] Mot de passe de bob : **** 
Password incorrect or not sufficient for authentication of user bob.
Sorry, try again:

$ locale
LANG=fr_FR.UTF-8
LC_CTYPE="fr_FR.UTF-8"
LC_NUMERIC="fr_FR.UTF-8"
LC_TIME="fr_FR.UTF-8"
LC_COLLATE="fr_FR.UTF-8"
LC_MONETARY="fr_FR.UTF-8"
LC_MESSAGES="fr_FR.UTF-8"
LC_PAPER="fr_FR.UTF-8"
LC_NAME="fr_FR.UTF-8"
LC_ADDRESS="fr_FR.UTF-8"
LC_TELEPHONE="fr_FR.UTF-8"
LC_MEASUREMENT="fr_FR.UTF-8"
LC_IDENTIFICATION="fr_FR.UTF-8"
LC_ALL=

$ localectl 
System Locale: LANG=fr_FR.UTF-8
    VC Keymap: fr-latin1
   X11 Layout: fr

Last edited by Cvlc (2023-07-13 10:34:47)

seth · 2023-07-11 20:52:26

https://github.com/systemd/systemd/issues/21813

Cvlc · 2023-07-13 10:34:30

Thanks, seems related indeed. I do have the same problem with sudo insults, which I had never managed to solve.

I'll file something to systemd then. Thanks !

seth · 2023-07-13 10:39:58

You'tre intentionally using homed?

Cvlc · 2023-07-13 10:46:40

haha yes. it's really not so bad

Trilby · 2023-07-13 13:00:32

Cvlc wrote:

it's really not so bad

He says after tracing two very odd bugs to it.

seth · 2023-07-13 13:47:05

https://bbs.archlinux.org/viewtopic.php … 1#p2098611
https://bbs.archlinux.org/viewtopic.php … 2#p2030412

There're coupled of others more, but the 2nd one is funny…

Trilby · 2023-07-13 13:56:50

Pretty soon if we want to get a list of files in a given directory in arch we'll have to use systemd-lsd ... and the files will be printed out with flashing rotating colors.

seth · 2023-07-13 14:38:56

And it'll read directories through a dbus daemon that provides a local cache, but you can make it act as a shim for ls by adding a real file /etc/ls.conf (otherwise systemd-lsd will create a symlink /etc/ls.conf -> /etc/lsd.conf when the daemon starts)

https://archlinux.org/packages/extra/x86_64/lsd/
https://archlinux.org/packages/extra/x86_64/exa/
(both are OF COURSE! written in rust!)

Cvlc · 2023-07-13 21:56:11

I don't really disagree, but it seems odd to only embrace parts of systemd and reject others. I'm still pretty new to this and have only known the linux world with systemd already being a significant part of it. I understand the problems that come with it taking over so many functions, but I wouldn't say that it doesn't work. Anyway, I really don't see any reason why it's ok to use journalctl and systemctl, but not ok to use homectl.

Cvlc · 2023-07-13 22:00:54

Anyway, it's really not my say whether this is good nor not good. homectl comes preinstalled with Arch. Might as well use it, and report upstream to fix things that don't work to make it better.

seth · 2023-07-13 22:17:35

It's ok to use whatever you want, but you're expressing a seriously concerning sentiment that reflects some of the criticism repeatedly brought against systemd.
The idea that "oh, my distro uses systemd as init daemon, so I guess the properbest way to use my network must be systemd-networkd" might superficially seem reasonable, but is actually just naive.
There's no functional connection between these tasks and you generally want to use the tool that suits you best.

If you truely found the problem that systemd-homed searches for (no, it's not pam_mount), you should absolutely use it - but not just because it heads "systemd-" and /especially/ not if it causes you only problems and no benefit at all.

Trilby · 2023-07-13 23:11:06

Cards on table of my view of the beast in question: systemd is a great init - really, it's a really excellent init. It also works pretty darn good as a service manager, though the configuration is quite complex for my tastes. But all it's other functions is where I've grown more and more (and more) critical as it really really sucks at almost everything else it does. And worse yet, it's displacing tools that do those tasks well.

That displacement is accelerated by people just using systemd-stuff just because. This then accelerates a lack of modularity and inter-operability. Systemd (now) does not work side by side with countless tools have have been around for decades. The use of systemd accessories is gradually imposing more requirements / restrictions on what *other* software can be used. It's becoming it's own walled garden ... or an 800-pound gorilla that no longer needs to even try to cooperate with other software but instead expects all other software to cooperate with it.

Udev? Nope, that's been assimilated. Another device manager? No such luck, you need to use systemd-udevd. Alternative logins? Maybe, but probably not for long, and even now it's a hell of an up-hill battle if you don't use systemd-logind. Systemd-homed? Sure, it's totally optional today ... but I don't give it long before countless tasks will become unmangageable on a system with systemd without using homed.

All joking aside, this trend is dangerous, and it disturbs me greatly.

Last edited by Trilby (2023-07-13 23:18:57)

Arch Linux

#1 2023-07-11 15:43:25

[solved] Sudo localization

#2 2023-07-11 20:52:26

Re: [solved] Sudo localization

#3 2023-07-13 10:34:30

Re: [solved] Sudo localization

#4 2023-07-13 10:39:58

Re: [solved] Sudo localization

#5 2023-07-13 10:46:40

Re: [solved] Sudo localization

#6 2023-07-13 13:00:32

Re: [solved] Sudo localization

#7 2023-07-13 13:47:05

Re: [solved] Sudo localization

#8 2023-07-13 13:56:50

Re: [solved] Sudo localization

#9 2023-07-13 14:38:56

Re: [solved] Sudo localization

#10 2023-07-13 21:56:11

Re: [solved] Sudo localization

#11 2023-07-13 22:00:54

Re: [solved] Sudo localization

#12 2023-07-13 22:17:35

Re: [solved] Sudo localization

#13 2023-07-13 23:11:06

Re: [solved] Sudo localization

Board footer