Bug 327192 - GPG - PGP Key-Pair Generation Failure Ubuntu T-Bird AND Kleopatra
Summary: GPG - PGP Key-Pair Generation Failure Ubuntu T-Bird AND Kleopatra
Status: RESOLVED WORKSFORME
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-05 20:55 UTC by Leo Rivers
Modified: 2023-02-15 03:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-14988-0.html (195 bytes, text/html)
2023-01-16 05:37 UTC, Leo Rivers
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leo Rivers 2013-11-05 20:55:11 UTC
GPG - PGP Key-Pair Generation Failure
Creating key-pair in Thunderbird with GPG enabled running Ubuntu 13.10 fails.
I installed Kleopatra and generating key paiR FAILS, so I ran self check.
The display reads:  "Gpg-Agent Connectivity    not reachable."
It  advises: "Check that gpg-agent is running and the GPG-AGENT_INFO variable is set and up to date."
How do I do this?
Will this help/ I am running Ubuntu 13.10 on an Intel Centrino ThinkPad from Emperor Linux with plentry ram.

Leo  l_rivers@efn.org

Reproducible: Always

Steps to Reproduce:
1. Be me
2. Use my setup
3. 
Actual Results:  
NOTE:  sometimes I am allowed to type in box awhile before FAIL. Trying to run a video or "disk intensive activity" fails MAYBE a little faster. Some fails are immediate. No pattern.

I ought mention the T-Bird efforts simply hung in space until I quit waiting for it to finsh. I waited several hours last night.

Expected Results:  
A Key Pair

I know this is just a report and you don't give support. But If you were to e-mail me with how to follow Kelopatra's advice that would be a real kindness.  Thanks

l_rivers@efn.org\
Comment 1 Andrew Crouthamel 2018-11-10 03:15:19 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-20 04:05:17 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-01 04:19:56 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-16 05:14:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Leo Rivers 2023-01-16 05:37:56 UTC
Created attachment 155343 [details]
attachment-14988-0.html

>  REPORTED
Comment 6 Bug Janitor Service 2023-01-31 05:04:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-02-15 03:48:35 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!