Created attachment 171995 [details] Result of try to digitally sign and introduce key to LO I am using Ubuntu20.04LTS and obtained a key with Seahorse. Try to digitally sign a document by using File>Digital Signatures>Digital Signatures and get empty Digital Signatures window. When I click the Start Certificate Manager button I get a window stating that "Could net find any certificate manager" I tried few forums and been advised to report a bug.
Maybe duplicate of bug 133941, but I'm not familiar with digital signature and help has no content for "Start Certificate Manager" button: https://help.libreoffice.org/7.2/en-GB/text/shared/01/digitalsignatures.html?System=WIN&DbPAR=WRITER&HID=xmlsec/ui/digitalsignaturesdialog/dialog-action_area1#bm_@@nowidget@@
(In reply to Dieter from comment #1) > and help has no content for "Start Certificate Manager" button: Report in bug 142562.
Bug 133941 is Windows only. This was already mentioned in Bug 125636, please see. Not sure if Linux needs a bug or you have to install GnuPG or Kleopatra.
Bug 133941 is Windows for Start Certifcate Manager. This one can be Linux per https://bugs.documentfoundation.org/show_bug.cgi?id=125636#c19 So I set New. Bug 125636 is Documentation, with explanation. Until that one is resolved, I wouldn't keep a separate bug 142562. Bug 133851 is for Help for Certificate Path-Certificate.. dialog.
*** Bug 142621 has been marked as a duplicate of this bug. ***
Bug 142621 has an info that digital signatures work with appimage, using Seahorse as a certificate manager. That's Ubuntu 20.04.2 64-bit and Mate 1.24.0.
I am on a similar system, 64 bit architecture, Ubuntu 20.04, Seahorse 3.36 but I can't reproduce with the following versions: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b57307e8f3553fcb292c9c11fcf58bcef3a6cb3c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.1.8.1 / LibreOffice Community Build ID: e1f30c802c3269a1d052614453f260e49458c82c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.0.6.2 Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Seahorse (aka "Passwords and Keys") opens normally. How did you install LibreOffice, Osman? I installed from .deb files. Could you please copy and paste here the information in Help > LibreOffice, and re-test with a recent version that we currently support ? (7.3 or 7.4) Cheers!
Dear Osman Kemal Kadiroglu, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
This might have to do with how Seahorse was installed (although I am aware it should be there by default on Ubuntu 20.04). For example, I installed Kleopatra as a flatpak. Clicking "Start Certificate Manager" in LO would still open Seahorse. However, after installing Kleopatra from the official repositories, LO would use Kleopatra as a default. There should be more control available to determine which tool is preferred if several are installed, and to point to the executable (e.g. for flatpak users who will find the executable in /var/lib/flatpak/exports/bin/...) Setting back to New before it is closed for insufficient data.
I think there is a problem about the UI and also in the help: The Start certificate manager button is mostly useful on Windows. On Linux, LO only use the certificate store from Firefox or Thunderbird, as it is described in (an old) OpenOffice documentation: https://wiki.openoffice.org/wiki/How_to_use_digital_Signatures . LO doesn't use the system default certificate manager on Linux! Workaround: You can select the certificate store from menu: Tools, Options and (in the left) LibreOffice\Security. There is „Certificate path” section (this is Linux (and maybe Mac?) only!), where (using the Certificate button) you can select between the Firefox and Thunderbird certificate store(s). There can be more certificate store if more Thunderbird/Firefox profile folders exists. Then you should import your certificates into the selected cert store. I think in LibreOffice on Linux (and Mac?), needs two improvements: (1) the help should describe this situation on non-windows platform, and (2) the Start Certificate Manager button should open the currently selected certificate store (and not the system default). Or at least warn the user that the certificate store is defined in Tools, Options, LibreOffice\Security, Certificate Path, and nothing to do with the default certificate manager. (The current UI is very confusing right now.) Or an alternative is to modify LO to use the system default certificate manager. But maybe it is more challenging because of the different Linux systems.
MacOS shows a message box with "Could not find any certificate manager.". Linux doesn't but starts Kleopatra if this tool is installed. I suggest to disabled the button, ie. check on initialization if any of the hard-coded tools is available, and show/amend the tooltip with the information why. Ideally we also make the list variable. For now it checks for kleopatra.exe, launch-gpa.exe, and gpa.exe on Windows and kleopatra, seahorse, gpa, kgpg otherwise. According the online help "On macOS, the default certificate manager is Keychain Access." but apparently it is ignored (and none of the keys is listed). Likely an extra topic. See xmlsecurity/source/dialogs/digitalsignaturesdialog.cxx at CertMgrButtonHdl
This bug has been solved in recent patches where it tries detecting an installed certificate manager in Linux, if not, you can set its location manually in the options. See https://gerrit.libreoffice.org/c/core/+/153798
Thanks TokieSan! I see the new option, so marking as verified for: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e7496f41562b75ea9732ca48f9aa0c07b69e424f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded