https://bugs.documentfoundation.org/show_bug.cgi?id=159587
kolAflash <kolafl...@kolahilft.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kolafl...@kolahilft.de
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=15
| |6979
--- Comment #2 from kolAflash <kolafl...@kolahilft.de> ---
Confirming on Debian-12 + KDE-Plasma where Kleopatra is being opened.
The dialog window was added in this commit.
https://git.libreoffice.org/core/+/92b6ffcd9f687cc54a0fc3801ca85c7e4d77512f%5E%21/#F6
(In reply to steve from comment #0)
> [...]
> Expected Results:
> [...]
> Showing a dialog is a great idea, but only when there is a problem and
> things need fixing. When things work as expected I'd prefer to not
> complicate user workflows unnecessarily.
At the moment there seems to be no additional dialog if starting the
Certificate Manager fails!
Actually when starting the Certificate Manager fails, the standard dialog comes
up anyway. Telling you
You have opened the certificate manager at ...
Although no certificate manager was started.
TESTING THE CERTIFICATE MANAGER FAILING TO START:
It looks like, if a Certificate Manager is available, it gets automatically set
in
Tools > Options > LibreOffice > Security
as "Certificate Manager". For Debian-12 with KDE-Plasma that's
/usr/bin/kleopatra
But if you uninstall the certificate manager afterwards, LibreOffice keeps that
setting. And if you click on "Certificate Manager" it unsuccessfully tries to
start the configured Certificate Manager.
see also: related bug 156979
certificate manager path reset to default when certificate manager opened
So I'd say, first an error message must be provided in case starting the
certificate manager fails.
And the field in the Options should behave in a more intuitive way. I think the
best choice is not to permanently set a "Certificate Manager" automatically.
But to use the automatic choice only for that very moment (not storing it).
--
You are receiving this mail because:
You are the assignee for the bug.
