Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1318615
| Summary: | gnome-initial-setup crashes after choosing a language | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Petr Schindler <pschindl> | ||||
| Component: | gnome-initial-setup | Assignee: | Rui Matos <tiagomatos> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 24 | CC: | awilliam, i18n-bugs, jstpierr, kparal, mcatanzaro+wrong-account-do-not-cc, mfabian, petersen, pschindl, robatino, tiagomatos | ||||
| Target Milestone: | --- | Keywords: | i18n | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | RejectedBlocker AcceptedFreezeException | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-06-28 15:32:53 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1230432 | ||||||
| Attachments: |
|
||||||
|
Description
Petr Schindler
2016-03-17 11:12:30 UTC
Created attachment 1137347 [details]
output of journalctl -f during the crash
Discussed at 2016-03-17 Go/No-Go meeting, acting as a blocker review meeting: https://meetbot.fedoraproject.org/fedora-meeting/2016-03-17/f24-alpha-go_no_go-meeting.2016-03-17-17.00.html . Rejected as an Alpha blocker; we agreed this is a conditional violation of the criteria but too narrow to qualify as an Alpha blocker, it requires you to both not create a user in anaconda *and* change the language in g-i-s, we thought for an Alpha, that's too narrow. By an oversight we didn't consider it for FE status, but I'm nominating it for that now. It could also be re-proposed as a blocker for a later milestone if a fix doesn't show up soon. Could someone post a backtrace please? Hum, I tried to reproduce this as described, but could not...sorry. Maybe Petr can. (In reply to Adam Williamson from comment #4) > Hum, I tried to reproduce this as described, but could not...sorry. Maybe > Petr can. I could not reproduce it either. I used Fedora-Workstation-Live-x86_64-24_Alpha-5.iso, installed in Japanese, did *not* create a user in Anaconda (I entered the root password in Anaconda), and then selected German in gnome-initial-setup. No crash. It is strange that glibc-langpack-en-2.23.1-5.fc24.x86_64 *and* glibc-all-langpacks-2.23.1-5.fc24.x86_64 are installed. If glibc-all-langpacks is installed, then glibc-langpack-en is redundant. And why glibc-langpack-en, why not glibc-langpack-ja if the installation was done in Japanese? Probably because we added something somewhere to make sure glibc-langpack-en is pulled in for anaconda, I'm guessing. Using NEEDINFO to request a backtrace (you might need to use 'sudo abrt-cli' to get it) Discussed at today's blocker review meeting [1]. Voted as AcceptedFreezeException (Alpha) - though this one seems a bit vague at present, there's certainly a potential serious issue here, so we accept it as FE and if a clearly reproducible case is found and fixed, we will look at taking the fix [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-03-21 I reproduced this with final release. I clicked on few languages in g-i-s and it crashed. I tried to reproduce after restart and it happened again (spanish -> german -> english -> crash) I reported this with abrt-cli - bug 1350873 *** This bug has been marked as a duplicate of bug 1350873 *** |