Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#77338 - [plasma-workspace] GLIBC_LOCALE_GENERATED=ON should be set alongside GLIBC_LOCALE_GEN=OFF

Attached to Project: Arch Linux
Opened by Mike Yuan (YHNdnzj) - Monday, 30 January 2023, 17:25 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 01 February 2023, 07:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

In the current plasma-workspace packaging, GLIBC_LOCALE_GEN=OFF is set to avoid Plasma messing with locale.gen [1].
However, this results in spurious error message in plasma, announcing "this KCM doesn't support auto-locale generation on non-glibc systems".
It also breaks saving to plasma-localerc, so users would have to edit the file manually.

To fix this, GLIBC_LOCALE_GENERATED=ON should also be set. It declares that locales should be considered pre-configured for plasma, which matches the reason that "Arch users are supposed to configure locales themselves".

Additional info:
* package version(s) 5.26.5-2

[1]: https://github.com/archlinux/svntogit-packages/commit/2f2b1e3c683d489e946afacd08cea0aeda1ec15c
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 01 February 2023, 07:59 GMT
Reason for closing:  Won't implement
Comment by Antonio Rojas (arojas) - Monday, 30 January 2023, 19:29 GMT
Actually, the message is useful to let users know they need to generate the locales (and it has been fixed upstream already to no longer mention non-glibc systems)

Can you elaborate how this breaks saving to plasma-localerc?
Comment by Lakeus Dimmingtwinkle (Lakejason0) - Tuesday, 31 January 2023, 14:57 GMT
https://bugs.kde.org/show_bug.cgi?id=464983

https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2565

I'm reporting the same (actually only a bit relevant since I changing the issue title on KDE bug tracker) issue, and that according to Mike, turning GLIBC_LOCALE_GEN=OFF solely will cause the `LANG=` under `[Formats]` section in the file ~/.config/plasma-localerc to use a value that isn't the same as the preferred language, but having GLIBC_LOCALE_GEN=OFF and GLIBC_LOCALE_GENERATED=ON will solve it. I haven't tested their opinion out though, but I tested out that turning GLIBC_LOCALE_GEN=ON is fine (though not expected by the packager since you would like to avoid Plasma messing around with locale.gen). And the merge request on KDE's GitLab is going to solve the case of GLIBC_LOCALE_GEN=OFF and GLIBC_LOCALE_GENERATED=OFF (current setting).
Comment by Lakeus Dimmingtwinkle (Lakejason0) - Tuesday, 31 January 2023, 15:16 GMT
After my testing, seems like Mike's suggestion won't solve the problem (the ~/.config/plasma-localerc still behaves as before). I'd suggest "keep the complaining error", which means back to pkgrel=2.
Comment by Doug Newgard (Scimmia) - Tuesday, 31 January 2023, 15:27 GMT
Honestly, I see it not being able to write plasma-localerc as a good thing. On the support side, when people are having locale issues, one of the first questions we ask is if they're using Plasma, and if they are to delete plasma-localerc.
Comment by Lakeus Dimmingtwinkle (Lakejason0) - Tuesday, 31 January 2023, 15:30 GMT
Deleting that file isn't a good idea for language users of Chinese, since we basically use en_US.UTF-8 in `/etc/locale.conf` to prevent TTY display issue. Deleting that file would make Plasma in English this case.
Comment by Doug Newgard (Scimmia) - Tuesday, 31 January 2023, 15:33 GMT
That's an utterly ridiculous way to set up a system. So all Chinese users must use Plasma? Really?
Comment by Lakeus Dimmingtwinkle (Lakejason0) - Tuesday, 31 January 2023, 15:35 GMT
You didn't get it. Whenever WM or DE we use, we all basically use en_US.UTF-8 in `/etc/locale.conf` to prevent TTY display issue. It's just that Plasma use a standalone file to set itself in Chinese, and other DE implement a similar mechanism to use Chinese for themselves.
Comment by Doug Newgard (Scimmia) - Tuesday, 31 January 2023, 15:36 GMT
Or you can do it more sanely by setting it in .xinitrc or similar.
Comment by Lakeus Dimmingtwinkle (Lakejason0) - Tuesday, 31 January 2023, 15:41 GMT
Anyway, just revert to 5.26.5-2, it makes most sense.
Comment by Antonio Rojas (arojas) - Wednesday, 01 February 2023, 07:59 GMT
OK, it's reverted in kde-unstable for the upcoming Plasma 5.27. I'll leave it in 5.26, since the warning message there is indeed quite misleading.

Loading...