Bug 370365 - American language with German locales: Date is in German
Summary: American language with German locales: Date is in German
Status: RESOLVED DUPLICATE of bug 340982
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-09 17:59 UTC by Roman Gilg
Modified: 2021-06-21 21:57 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Gilg 2016-10-09 17:59:20 UTC 
I'm using American English in KCM Language and tried de_DE aswell as en_DE in KCM Formats. In the lockscreen the date is always in German language instead of English. For example it's Mittwoch instead of wednesday.

The same is true for sddm by the way. But this might be independent of Kscreenlocker.

Reproducible: Always
Comment 1 Martin Flöser 2016-10-10 05:17:53 UTC 
I think that's a Qt problem, @Kai do you know anything?
Comment 2 Roman Gilg 2016-10-10 11:41:41 UTC 
Yea, probably related to https://bugs.kde.org/show_bug.cgi?id=365139 and the most infamous bug https://bugs.kde.org/show_bug.cgi?id=340982

I just thought it's still useful to create an extra report for the lockscreen aswell. Maybe the reason is here something else or if not, it atleast shows, that the issue is wider spread and not only affecting the digital clock widget. For me personally I find it only to be mildly annoying, but still, it affects several key components of the Plasma desktop.
Comment 3 Neousr 2018-11-01 19:49:47 UTC 
Replicable on a pair of systems running 5.14.2 even if I'm not using the same combination of locales German/American, got the same symptoms along Bug 365139.

The language chose from the original installation stays after the locale is changed system wide from the settings.
Comment 4 Nate Graham 2021-06-21 21:57:03 UTC 

*** This bug has been marked as a duplicate of bug 340982 ***