This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1977785 - [CJK] - The input method engine is not added by default, in case user is created during anaconda setup for CJK(Asian) locales
Summary: [CJK] - The input method engine is not added by default, in case user is crea...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome (assorted, untriaged)
Version: 9.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: beta
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1947788
Blocks: 2027125
TreeView+ depends on / blocked
 
Reported: 2021-06-30 13:30 UTC by Bhushan Barve
Modified: 2023-09-15 16:55 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1947788
Environment:
Last Closed: 2023-09-15 16:55:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-initial-setup issues 12 0 None None None 2021-08-30 13:39:18 UTC
GNOME Gitlab GNOME gnome-initial-setup merge_requests 113 0 None None None 2021-08-16 12:44:04 UTC
Red Hat Issue Tracker   RHEL-4097 0 None Migrated None 2023-09-15 16:54:55 UTC

Description Bhushan Barve 2021-06-30 13:30:53 UTC
Cloning the scenario for RHEL 9-Beta
RHEL-9.0.0-20210616.0
gnome-initial-setup-40.1-1.el9.x86_64

If user is created during anaconda setup, g-i-s does not run. Please see the additional comment below and ignore the description part in the cloned bug.


+++ This bug was initially created as a clone of Bug #1947788 +++

Description of problem: Did the f34 WS installation (vm, ja_JP locale) with network installation method. Observed that gnome-initial-setup did not run after first time login. Same issue was observed when installation done using with boot.iso. Tried reboot many times but did not help.

However when the installation was done using live image, g-i-s ran properly. 

F34 network installation done using - http://download.eng.pnq.redhat.com/fedora/linux/development/34/Everything/x86_64/os/

F34 live image - http://download.eng.pnq.redhat.com/fedora/linux/development/34/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-34-20210408.n.0.iso

Here are the contents 0f - 
[test@fedora ~]$ cat /etc/xdg/autostart/gnome-initial-setup-first-login.desktop 
[Desktop Entry]
Name[af]=Aanvanklike opstelling
Name[an]=Configuración inicial
Name[ar]=الإعداد الأولي
Name[as]=আৰম্ভণিৰ সংস্থাপন
Name[be]=Пачатковая настройка
Name[bg]=Първоначални настройки
Name[bn_IN]=প্রাথমিক সেটআপ
Name[bs]=Početna postavka
Name[ca]=Configuració inicial
Name[ca@valencia]=Configuració inicial
Name[ckb]=ڕێکخستنی سەرەتایی
Name[cs]=Prvotní nastavení
Name[da]=Førstegangsopsætning
Name[de]=Ersteinrichtung
Name[el]=Αρχική ρύθμιση
Name[en_GB]=Initial Setup
Name[eo]=Komenca agordado
Name[es]=Configuración inicial
Name[et]=Esialgne seadistus
Name[eu]=Hasierako konfigurazioa
Name[fa]=برپاسازی نخستین
Name[fi]=Alkuasetukset
Name[fr]=Configuration initiale
Name[fur]=Configurazions iniziâls
Name[ga]=Socrú Tosaigh
Name[gd]=Suidheachadh tòiseachaidh
Name[gl]=Configuración inicial
Name[gu]=પ્રારંભિક સુયોજન
Name[he]=התקנה ראשונית
Name[hi]=आरंभिक सेटअप
Name[hr]=Početno postavljanje
Name[hu]=Kiinduló beállítások
Name[ia]=Configuration initial
Name[id]=Penyiapan Awal
Name[is]=Upphafsstillingar
Name[it]=Impostazioni iniziali
Name[ja]=初期セットアップ
Name[kk]=Бастапқы баптау
Name[kn]=ಆರಂಭಿಕ ಏರ್ಪಾಡು
Name[ko]=초기 설정
Name[lt]=Pradinis nustatymas
Name[lv]=Sākotnējā iestatīšana
Name[mjw]=Aphrangsi pangchengsi ke-ot
Name[ml]=ആദ്യ ക്രമീകരണം
Name[mr]=प्रारंभिक सेटअप
Name[ms]=Persediaan Awalan
Name[nb]=Førstegangsoppsett
Name[ne]=सुरुको सेटअप
Name[nl]=Instellingen voor eerste gebruik
Name[oc]=Configuracion iniciala
Name[or]=ପ୍ରାରମ୍ଭିକ ବ୍ୟବସ୍ଥା
Name[pa]=ਮੁੱਢਲਾ ਸੈਟਅੱਪ
Name[pl]=Początkowa konfiguracja
Name[pt]=Configuração Inicial
Name[pt_BR]=Definições iniciais
Name[ro]=Configurare inițială
Name[ru]=Первоначальная настройка
Name[sk]=Prvotné nastavenie
Name[sl]=Začetna nastavitev
Name[sr]=Почетно подешавање
Name[sr@latin]=Početno podešavanje
Name[sv]=Initial konfiguration
Name[ta]=தொடக்க அமைவு
Name[te]=ఆరంభ అమరిక
Name[tg]=Танзимоти ибтидоӣ
Name[th]=ตั้งค่าเริ่มแรก
Name[tr]=İlk Kurulum
Name[ug]=دەسلەپكى تەڭشەش
Name[uk]=Перший запуск
Name[vi]=Cài đặt lần đầu
Name[zh_CN]=初始配置
Name[zh_HK]=初始設定
Name[zh_TW]=初始設定
Name=Initial Setup
# Translators: Do NOT translate or transliterate this text (this is an icon file name)!
Icon=preferences-system
Exec=/usr/libexec/gnome-initial-setup --existing-user
Terminal=false
Type=Application
StartupNotify=true
Categories=GNOME;GTK;System;
OnlyShowIn=GNOME;
NoDisplay=true
AutostartCondition=unless-exists gnome-initial-setup-done
X-GNOME-HiddenUnderSystemd=true

Not really sure what is the issue here. Please re-assign the component if required.


Version-Release number of selected component (if applicable):
[test@fedora ~]$ rpm -qa gnome-initial-setup
F34
gnome-initial-setup-40.0-1.fc34.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Bhushan Barve on 2021-06-30 13:19:45 UTC ---

Checked it again and found that if user is created during anaconda setup, the g-i-s does not run after installation. If user is not created during anaconda, g-i-s runs properly. 

For CJK locales, if g-i-s does not run, then the default input method is not set accordingly. These locales require input method to be set along with the keyboard for input in native language. In that case user manually needs to select the IM from settings.

Updating the summary accordingly and also cloning it for RHEL-9.

Comment 23 RHEL Program Management 2022-12-30 07:27:55 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 30 RHEL Program Management 2023-09-15 16:53:08 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 31 RHEL Program Management 2023-09-15 16:55:00 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.