Bug 118478 - OpenPGP / GnuPG issues
Summary: OpenPGP / GnuPG issues
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-01 07:19 UTC by brian
Modified: 2019-02-21 10:07 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Digital Signatures window (27.82 KB, image/png)
2018-07-01 07:19 UTC, brian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description brian 2018-07-01 07:19:17 UTC
Created attachment 143245 [details]
Digital Signatures window

Ubuntu 18.04 MATE
LibreOffice Version: 6.0.5.2
Build ID: 1:6.0.5~rc2-0ubuntu0.18.04.1~lo1
CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group

OpenPGP does not appear to be working at all. This report appears to be a semi duplication of other reports, but they are only similar and not mentioning Linux, but MacOS and Windows.

1) Go to Tools -> Options -> User Data, under Cryptography there is OpenPGP Signing Key and OpenPGP Encryption Key. Both show "No Key" and the pull down lists nothing more to select, ie. none of my keys appear.

2) Go to File -> Digital Signatures -> Digital Signatures, I an given a window, blank in content, with the options of "Sign Document" and "Start Certificate Manager" [see attached screenshot]. I click to start certificate manager, and from there Seahorse opens and I can see and verify all of the keys and certificates I expect to see and have available to me. So, I click to sign document. I am then asked to select a certificate, and only X.509 options are there.

Unless I am missing something, those are the only places I find to use PGP keys to sign a document. I currently have numerous X.509 certs and PGP keysets on my system, all working properly. I have enigmail, gnupg, seahorse, gpg, and other key management and dev tools installed. I am able to generate and manage keys without issues, and use keys PGP and SSH keys without issue for basic messages, email, remote connectivity, etc. This issue is not new for me to this version, it has been existing for a while. I am reporting now as the need to use came up again and it is still not functional.
Comment 1 Xisco Faulí 2018-10-19 10:37:42 UTC Comment hidden (obsolete)
Comment 2 brian 2018-10-19 13:12:24 UTC
My current version is:
Version: 6.1.3.1
Build ID: 1:6.1.3~rc1-0ubuntu0.18.04.1

Nothing has changed in what I reported 3 months ago throughout all of the updates/upgrades received since then.
Comment 3 Thorsten Behrens (allotropia) 2018-11-11 23:51:42 UTC
It seems LibreOffice is unable to discover a working gpg setup on your machine. To further troubleshoot this, it would be easiest if you could install a debug-enabled version, e.g. from here:

https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86@87-TDF-dbg/current/

Then run it from a terminal, with the following environment variable set:

export SAL_LOG="+WARN.+INFO.xmlsecurity"

and provide a link to the output (please review for potential private information, the log can be quite verbose).
Comment 4 brian 2019-02-19 02:43:37 UTC
I would prefer not to do such steps as I use the software. I have this same issue on all laptops I have LibreOffice installed on, and also use GPG on all as well with no issues on Thunderbird, manual signing, file encryption, etc. If LibreOffice cannot find it, there seems to be a bigger issue as the install is all default, nothing changed or modified in any way except for the import and export of keys, and in some cases, a newly generated key.

I am currently using Version: 6.1.5.2, Build ID: 1:6.1.5~rc2-0ubuntu0.18.04.1~lo3 on this laptop which was a fresh install on a new hard disk about 3 months ago. Everything as reported is identical, as well as everything else working just fine.

Is there any way to see any debug into without needing to install a "new" product? It seems odd as if it wants to find gpg, it just needs to look in the default location. I also cannot find any settings on how I might make sure it is looking there.
Comment 5 Thorsten Behrens (allotropia) 2019-02-19 12:24:35 UTC
6.1.5~rc2-0ubuntu0.18.04.1~lo3 seems to be a pre-release build provided by the Ubuntu community, so we have no control over how that build is done. It does appear not to be a general problem though with LibreOffice on that system.

For any further insight, we'd need the requested info.
Comment 6 brian 2019-02-20 04:43:49 UTC
Do you have a working PPA I could install future updates from where the product would be supported? FYI- the link previously provided is not / no longer valid.

I do see this:
https://launchpad.net/df-libreoffice

which then directs at the bottom to where I have installed from:
"LibreOffice packaging for Ubuntu can be found at: https://launchpad.net/~libreoffice"
Comment 7 Olivier Tilloy 2019-02-20 15:15:30 UTC
Please note that packages from PPAs are not officially supported, they are a community best effort to provide up-to-date packages on older versions of Ubuntu.
If you're after an officially supported package, you should stick to the (older) version in the Ubuntu repositories.

That said, this bug is being tracked in Ubuntu at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772683.
Comment 8 Thorsten Behrens (allotropia) 2019-02-21 10:07:38 UTC
Thx for the pointer Olivier - closing then on this side.