Bug 361930

Summary: Certificates not visible in main window tabs
Product: [Applications] kleopatra Reporter: Peter Rothwell <astonpwr>
Component: generalAssignee: Andre Heinecke <aheinecke>
Status: RESOLVED FIXED    
Severity: grave CC: kdepim-bugs, mutz
Priority: NOR    
Version: 2.2.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Peter Rothwell 2016-04-18 13:01:43 UTC 
The Kleopatra main window does not display any certificates. Importing indicates that the certificates are installed.  The 'Imported Certificate' tabs are also blank but if I hover the cursor over the tab, the name of the invisible certificate appears in the pop-up; confirming that the certificate exists, it's just not being displayed.  Nothing can be selected in the certificate window and all certificate operations are greyed out in the menus.

Reproducible: Always

Steps to Reproduce:
1.Open Kleopatra on Win 10 Pro x64
2.
3.

Actual Results:  
Blank certificate tab windows

Expected Results:  
Installed certificates displayed in certificate tabs

I can use GPA for the same file handling functions that I would normally use Kleopatra for on this machine, so Kleopatra is basically unuseable, now.  Windows Explorer contect menu decrypt & verify function is also unresponsive.
Comment 1 Peter Rothwell 2016-04-18 13:19:33 UTC 
Pressing the 'Redisplay' button starts an operation that lasts a long time, without changing anything on the certificates display.
Comment 2 Andre Heinecke 2016-04-18 13:24:25 UTC 
are you using X509 Certificates or OpenPGP?
By default Kleopatra did a CRL (Certificate revocation list) check for all X509 Certificates and would not show them until this was completed. CRL checks could take an arbitrary amount of time on stalled connections. Which sounds a bit like your problem (No Certificates shown and a long running keylisting). This problem was fixed in gpg4win-2.2.5 though.

Are you using the most recent version of gpg4win? ( 2.3.1)
Comment 3 Peter Rothwell 2016-04-19 12:22:45 UTC 
Hi Andre, thanks for getting back to me.  I am using both certificate types on version 2.3.1 but your questions prompted me to check some things I had taken for granted.  Sure enough, the root certificate had not updated successfully as I thought it had when I responded to the new certificate issue.  I've updated this now and everything else has fallen into place, with Kleopatra functioning as normal.

Thanks,
Peter