Bug 469898

Summary:	Regional settings issue - defaults to American English
Product:	[Applications] systemsettings	Reporter:	Len North <len.north>
Component:	kcm_users	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	minor	CC:	uhhadd
Priority:	NOR
Version First Reported In:	5.24.7
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	System Information Screenshot

Description Len North 2023-05-17 16:08:55 UTC

Created attachment 159035 [details]
System Information Screenshot

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
My Location is Western Australia  UCT+8hrs.
My time is correct but an update has changed all Regional Language settings to UCT -8hrs

STEPS TO REPRODUCE
1. AstroPhotos show date taken as tomorrow, 8 hours ahead of actual capture time
2. I cannot reset regional language settings as all choices default to UCT -8hrs
3. Wish it would work on horse racing...

OBSERVED RESULT
I cannot correct it, Regional language just defaults to -8 hrs.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 22.04
(available in About System)
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

Comment 1 Bug Janitor Service 2023-05-17 16:34:31 UTC

Thank you for the bug report!

However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report.