Bug 483083
Summary: | Freezes when trying to change a key's passphrase. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | George Notaras <gnot> |
Component: | seahorse | Assignee: | Tomáš Bžatek <tbzatek> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | bugs.michael, martikj2, tbzatek, trojanfoe, tsmetana |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-18 07:44:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
George Notaras
2009-01-29 16:45:41 UTC
I have a similar problem in seahorse for f11, any point where I would be asked to put in my passphrase results in seahorse locking up and a process named pinentry, which i presume to be the command line gpg util asking for my passphrase, eating up half of my processor cycles. I also have this problem with Seahorse under F11 (amd64) whenever I am expected to enter the passphrase for my key. Does installing "pinentry-gtk" help? -> bug 474419 Yes, it does, might want to add pinentry-gtk as a dependency to seahorse. (In reply to comment #4) > Yes, it does, might want to add pinentry-gtk as a dependency to seahorse. Sorry for the self-reply but it provides a partial fix. a dialogue box asking for the key password comes up and if the user puts in a new key everything works fine. However if the user cancels out, while the program won't hang, pinentry does not go away gracefully and needs to be manually killed as before. This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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. Thank you for reporting this bug and we are sorry it could not be fixed. |