Launchpad has imported 6 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=118478.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2018-07-01T07:19:17+00:00 Brian wrote: Created attachment 143245 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772683/comments/4 ------------------------------------------------------------------------ On 2018-10-19T10:37:42+00:00 Xiscofauli wrote: Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772683/comments/5 ------------------------------------------------------------------------ On 2018-10-19T13:12:24+00:00 Brian wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772683/comments/6 ------------------------------------------------------------------------ On 2018-11-11T23:51:42+00:00 Thb-b wrote: 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). Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772683/comments/7 ------------------------------------------------------------------------ On 2019-02-19T02:43:37+00:00 Brian wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772683/comments/8 ------------------------------------------------------------------------ On 2019-02-19T12:24:35+00:00 Thb-b wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772683/comments/9 ** Changed in: df-libreoffice Status: Unknown => Incomplete ** Changed in: df-libreoffice Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772683 Title: [snap] Cannot sign a document, gpg keys are not listed To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
