Bug 1471916
| Summary: | Cannot start gnome-terminal when no locale is set | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Georg Sauthoff <fedora> |
| Component: | gnome-terminal | Assignee: | Debarshi Ray <debarshir> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 29 | CC: | afranke, debarshir, eclipseo, fedora, majopela, mclasen, tim, yann |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-27 23:09:15 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: | |||
|
Description
Georg Sauthoff
2017-07-17 16:12:39 UTC
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. I doubt this will ever be fixed. Is there any particular reason that you want to have an empty /etc/locale.conf? Well, the point of this bug report is: having an important GUI application that has the worst failure mode is quite bad. It isn't about eliminating /etc/locale.conf. I mean, when you are (for whatever reason, e.g. filesystem corruption, bug in the installer, accidental skipping the welcome dialog (!), ...) in the situation that you don't have the right /etc/locale.conf and gnome-terminal feels to be extravagant enough to only work with UTF-8 locales explicitly set, then the least you should expect is a properly displayed error message - e.g. in an error dialog. As-is, it just silently fails, i.e. there is no visible feedback, it just doesn't start. Improving this failure mode would increase the user-friendliness of the Gnome desktop, I would argue. “Interesting” related issue (side effect?): currently there is a bug (#1574222) which makes it so that after an upgrade to F28 the language packs are not installed as they should (glibc-language-* missing amongst other things) and one cannot launch the terminal to debug the issue. (In reply to Alexandre Franke from comment #4) > “Interesting” related issue (side effect?): currently there is a bug > (#1574222) which makes it so that after an upgrade to F28 the language packs > are not installed as they should (glibc-language-* missing amongst other > things) and one cannot launch the terminal to debug the issue. I confirm, see bug 1570924. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. I confirm, I'm hitting it now, it wasn't the case minutes ago. I don't know what changed. (In reply to Debarshi Ray from comment #9) > Bug 1574222 ? What is the question? What info do you need? This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |