[Expired for seahorse (Ubuntu) because there has been no activity for 60
days.]
** Changed in: seahorse (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.lau
** Changed in: seahorse (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/231502
Title:
Passphrase dialog d
Hello Micah,
Thank you for submitting this bug and reporting a problem with the seahorse
package. You made this bug report in 2008 and there have been several versions
of Ubuntu since then.
Could you confirm that this is no longer a problem and that we can close the
ticket?
If it is still a
I'm currently using these three, as unsetting just GPG_AGENT_INFO no
longer seems sufficient.
unset GPG_AGENT_INFO
unset SSH_AUTH_SOCK
unset GNOME_KEYRING_SOCKET
(Not all of these necessarily relate to seahorse? I dunno, I just fix
what breaks for me. :)
--
Passphrase dialog doesn't accep
This bug still persist in Jaunty when using Thunderbird + Enigmail + gpg
--use-agent.
It can be also experienced when you try to change passphrase of already
created PGP key within Seahorse.
Synopsis:
0) Launch Seahorse
1) Right-click on your PGP key -> Properties
2) Change Passphrase
3) Passphra
** Changed in: seahorse (Ubuntu)
Status: Invalid => New
--
Passphrase dialog doesn't accept input
https://bugs.launchpad.net/bugs/231502
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
