Bug 193664

Summary:	Kleopatra fails to start after loading "Bridge" Certificates
Product:	[Applications] kleopatra	Reporter:	Patrick Patterson <ppatters>
Component:	general	Assignee:	Patrick Patterson <ppatters>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	emanuel, kdepim-bugs
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Patrick Patterson 2009-05-22 19:20:48 UTC

Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Ubuntu Packages

There appears to be a bug in Kleopatra for running the UI, where if you install a PKI Bridge Bundle (such as that found at: http://certipath-aia.verisign.com/CertiPathBridgeCA.p7c , and you have one of the trust anchors configured (such as the EADS Root CA cert: http://publication.certificateservices.eads.com/CAcerts/EADSRootCA2.p7c), then Kleopatra will allow you to import the bundle, but it will then error out with an error similar to:

"The Kleopatra GPG UI Server Module could not be initialised.
The error given was: The graph must be a DAG.
You can use Kleopatra as a certificate manager, but cryptographic plugins that rely on a GPG UI Server being present might not work correctly, or at all."

This is probably because, with the bridge bundle, there are multiple ways to get to and from the CertiPath CBCA.

This is a major showstopper for use of Kontact in US Government, US FBCA environment, and Aerospace, as the PKI Trust fabric for those areas is moving to a model where supporting a Bridge PKI topology is extremely important.

If you need any further information or clarification, please let me know.

Comment 1 Patrick Patterson 2009-05-22 19:22:28 UTC

Just a further comment:

After encountering the above error dialog, the following popup happens:

A Fatal Error Occurred
The application Kleopatra (kleopatra) crashed and caused the signal 6 (SIGABRT).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc

Unfortunately, I don't have debug enabled to give you the crash dump.

Comment 2 Emanuel Schütze 2013-05-08 10:41:38 UTC

Is this bug still relevant in current Kleopatra of KDE 4.10.3?

Comment 3 Andrew Crouthamel 2018-10-30 00:02:18 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 4 Bug Janitor Service 2018-11-14 11:24:47 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 Bug Janitor Service 2018-11-29 04:46:00 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!