Bug 1225825 - Migrated systems do not apply language to it's full extend
Summary: Migrated systems do not apply language to it's full extend
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Aeon
Classification: openSUSE
Component: Installation (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Richard Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-03 11:28 UTC by Imo Hester
Modified: 2024-06-03 11:32 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Imo Hester 2024-06-03 11:28:00 UTC 
Hey there,

I just found that systems migrated from RC 1 to RC 2 do not apply the preferred user language to it's full extend.

1) In gnome-settings everything is set to be the default, English.
It seems the preferred language from the former home of the user seems not to be carried over properly

2) Since /usr/bin/aeon-firstboot is not executed either, additional packages for more locales are missing as well.

This can be fixed manually as the user can change the language any time and then manually execute aeon-firstboot.

Might be a wont fix, as there are probably not too many users migrating from RC 1 to RC 2. But I guess it's up to you to decide.
Comment 1 Richard Brown 2024-06-03 11:32:07 UTC 
/usr/bin/aeon-mig-firstboot is executed after migrations, regardless of where they migrated from

This was checked in already, so you must have been using an old image.. even snapshot 0524/tik 1.0.2 has this fix