[okular] [Bug 452095] Firefox user certificate store not recognized in Snap

[noliver]

https://bugs.kde.org/show_bug.cgi?id=452095

--- Comment #5 from noliver  ---
Thanks for the suggestion, but I've already tried snap installing -
originally my
 firefox (which is by default snap installed)  didn't load pkcs11 module
and needed
to manually install the latest version in order to be able to load and work
with it.

I was hoping that Okular would have the same behavior but unfortunately even
after installing from flatpak it still doesn't find my installed
certificates as firefox does.

I wonder if it would have something to do with Ubuntu 22.04 or something
misconfigured
on Poppler.

Em qui., 15 de dez. de 2022 às 05:10, ferdymercury 
escreveu:

> https://bugs.kde.org/show_bug.cgi?id=452095
>
> --- Comment #4 from ferdymercury  ---
> > Is there something that could be done about this?
>
> I ended up installing Okular via flatpak instead of snap, there it works.
>
> If you prefer to continue with snap, you might try to establish a symlink
> between what snap considers its HOME folder and what your actual HOME
> folder
> is, maybe it detects that then. See
> https://askubuntu.com/a/1257529/1179344
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 452095] Firefox user certificate store not recognized in Snap

[noliver]

https://bugs.kde.org/show_bug.cgi?id=452095

noliver  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu
Version|21.12.1 |22.08.3
 CC||nil...@rogow.com.br

--- Comment #3 from noliver  ---
Same problem here on Ubuntu 22.04, Firefox v108, Poppler 22.12.0 and Okular
22.08.3 installed from flatpak. 

In my system, both $USER/.pki/nssdb (used by default on Okular backend) and
$USER/.mozilla/firefox/vkre7ysu.default-release have .so pksc11 library of usb
token installed and working - I can sign and verify libreoffice documents with
them - but no certificate is listed when Okular's infrastructure backend pops
up and thus, and thus, not possible to sign any pdf.

Is there something that could be done about this? unfortunately running from
command line does not show any warnings nor errors. Its possible to verify
documents already signed but not possible to sign once no certificate is found
by Okular.

Thanks in advance for any help.

-- 
You are receiving this mail because:
You are watching all bug changes.