Red Hat Bugzilla – Bug 474419
Seahorse don't prompt for passwords, show "Bad password" error.
Last modified: 2015-03-03 17:33:39 EST
Description of problem:
Seahorse don't prompt for gpg passwords, showing a "Bad password" error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
show "Bad password"
This issue occurs in systems where pinentry-gtk is not installed, in the xfce spin for example.
Seahorse package currently not require pinentry-gtk, and this is needed to solve this problem.
I've got similar caused problems because pinentry-gtk is not installed. When trying to sign a foreign key with seahorse without pinentry-gtk installed, seahorse freezes and doesn't react on any input, neither on mouse nor on keyboard. A prompt for the passphrase of the own key is missing.
After killing seahorse there is still a pinentry-process which needs 100% of cpu load, but without any output.
Installing pinentry-gtk solved that problem. I think it would be a good idea to declare pinentry-gtk as a dependency of seahorse.
I've added explicit pinentry-gtk dependency to the rawhide package (seahorse-2.27.1-2.fc12), want to get some testing before pushing to stable Fedora releases.
> After killing seahorse there is still a pinentry-process which
> needs 100% of cpu load, but without any output.
seahorse requires gpgme, which in turn requires gnupg2, which in turn requires pinentry, which by default is only for ncurses.
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:
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.