2nd Additionally ... this is the error that I get in the console when
launching the snap version ... I'm wondering if this particular document
is trying to phone home or something ...
Error registering document:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy
prevents
20.04.5 has evince 3.36.10. Opening a doc signed with docusign fails
in this version of evince, but google chrome opens it fine. The error is
"PDF document is damaged"
don't know if this will help but there it is. If anyone wants the pdf
causing the error, let me know.
Addionally ... if this
Did anyone reply? This bug affects many people.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1944453
Title:
PDF documents signed with DocuSign show the error message
It's not right, basically it's the case described in
https://wiki.ubuntu.com/Bugs/Responses#Fixed_in_Development_release_while_still_existing_in_a_previous_release.
The report here is the first one we get about the issue and no other
user marked itself as affected. If we had unlimited resources
@seb128 I am aware that this has been fixed in hirsuite, but it remains
unfixed in focal. I am committed to staying on an LTS release.
If this is not the right place to report this bug, could you please
point me to how I can navigate the relevant backporting request process?
--
You received
Thanks, trying using the example from
https://sec.report/lux/doc/102081415.pdf the issue is fixed in hirsute
** Package changed: evince (Ubuntu) => poppler (Ubuntu)
** Changed in: poppler (Ubuntu)
Importance: Undecided => High
** Changed in: poppler (Ubuntu)
Status: New => Fix
6 matches
Mail list logo
