Thank you for your bug. What version of Ubuntu do you use?
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
formatting code showing in "allow access" dialogue
https://bugs.launchpa
Sorry. Feisty Desktop i386, installed clean from daily image 20070415
(which I think became the final release). All updates applied.
Thanks
Matthew
--
formatting code showing in "allow access" dialogue
https://bugs.launchpad.net/bugs/107605
You received this bug notification because you are a me
how do you trigger the dialog? what locale do you use? does it happen
with other applications or only seahorse?
--
formatting code showing in "allow access" dialogue
https://bugs.launchpad.net/bugs/107605
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
To trigger the dialogue, I compose a new message in thunderbird, and
press send. At this point Enigmail / OpenPGP attempts to sign the
message, for which it needs to pull my pgp passphrase from the keyring,
and so the "Allow access" dialogue appears as shown in the screenshot
above.
Default langua
** Changed in: gnome-keyring (Ubuntu)
Status: Needs Info => Unconfirmed
--
formatting code showing in "allow access" dialogue
https://bugs.launchpad.net/bugs/107605
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
** Attachment added: "screenshot"
http://librarian.launchpad.net/7344763/Screenshot.png
--
formatting code showing in "allow access" dialogue
https://bugs.launchpad.net/bugs/107605
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Could you try if you still get the issue using gutsy or hardy?
** Changed in: gnome-keyring (Ubuntu)
Status: New => Incomplete
--
formatting code showing in "allow access" dialogue
https://bugs.launchpad.net/bugs/107605
You received this bug notification because you are a member of Ubuntu
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
