Bug 827728
| Summary: | Needs to depend on usermode-gtk | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sergio <ikisham> |
| Component: | gparted | Assignee: | Deji Akingunola <dakingun> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | dakingun, joe, kparal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gparted-0.16.1-2.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-04 08:59:59 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
Sergio
2012-06-02 17:10:36 UTC
In Fedora 18 if I remove usermode-gtk, gparted silently fails to run from the application menu. It can still be run from the console. Gparted should have an explicit dependency on usermode-gtk. This is a packaging issue, can you please fix it? It has been opened for 10 months! Thanks. gparted-0.14.1-1.fc18.x86_64 usermode-gtk-1.111-1.fc18.x86_64 Thank you! This one bugged me to no end. I can confirm both the bug and the workaround. You may get a faster response by changing the title to something like "gparted missing dependency on usermode-gtk." Also, I'm using Fedora 18, so this bug impacts that version too. gparted-0.16.1-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gparted-0.16.1-2.fc18 gparted-0.16.1-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gparted-0.16.1-2.fc19 gparted-0.16.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gparted-0.16.1-1.fc17 Package gparted-0.16.1-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gparted-0.16.1-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10621/gparted-0.16.1-2.fc18 then log in and leave karma (feedback). Confirmed fixed with gparted-0.16.1-2.fc18. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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. gparted-0.16.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. gparted-0.16.1-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. gparted-0.16.1-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |