Bug 120046 - GPG keys are not available to LO after kernel update
Summary: GPG keys are not available to LO after kernel update
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-22 06:12 UTC by Timur Davletshin
Modified: 2019-08-09 08:54 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timur Davletshin 2018-09-22 06:12:46 UTC 
Description:
GPG signing functionality becomes unavailable after kernel update.

Steps to Reproduce:
System: Debian 9.5, x86-64
1. Stock kernel 4.9 — GPG keys are listed as expected in Preferences → User data → Cryptography.
2. Install backported kernel 4.18 — GPG is not available to LO.

Actual Results:
GPG keys are not listed

Expected Results:
GPG keys should be listed regardless kernel version


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Xisco Faulí 2019-05-22 14:54:42 UTC 
A new major release of LibreOffice is available since this bug was reported.
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.
Comment 2 Timur Davletshin 2019-08-09 08:53:59 UTC 
(In reply to Xisco Faulí from comment #1)
> A new major release of LibreOffice is available since this bug was reported.
> 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.

This bug can be closed. Problem was in apparmor enabled by default in new kernels. Disabling it or allowing access to ~/.gnupg fixed described problem.