[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

2022-12-17 Thread brandon
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 this sender from sending this message to this recipient; 
type="method_call", sender=":1.949" (uid=1000 pid=368136 
comm="/snap/evince/1020/usr/bin/evince ./Galvanize_Stude" 
label="snap.evince.evince (enforce)") interface="org.gnome.evince.Daemon" 
member="RegisterDocument" error name="(unset)" requested_reply="0" 
destination="org.gnome.evince.Daemon" (bus)

-- 
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 "The
  document contains no pages"

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---

  1. Open a document signed with DocuSign

  Expected behaviour:
  ---

  Document opens fine

  Actual behaviour:
  ---

  Evince refuses to display the document, with the error message "The
  document contains no pages".

  If document is opened with `pdftotext`, the output is:

  ```
  Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
  Syntax Error: Invalid XRef entry 3
  Syntax Error: Top-level pages object is wrong type (null)
  Command Line Error: Wrong page range given: the first page (1) can not be 
after the last page (0).
  ```

  Other information
  ---

  This appears to be a bug in libpoppler, described at
  https://stackoverflow.com/questions/66636441/pdf2image-library-
  failing-to-read-pdf-signed-using-docusign and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I
  believe that bumping the version of Poppler and/or Evince will solve
  the issue, though I have no way to test this as compiling from source
  is a significant undertaking.

  I do not have a public sample document that I could share, but
  examples of DocuSigned documents should be available online.

  Ubuntu version: 20.04 LTS (up to date)
  Evince version: 3.36.10 (official package)
  Poppler version: 0.86.1-0ubuntu1 (official package)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

2022-12-16 Thread brandon
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 helps anyone ...

# /usr/bin/evince --version
GNOME Document Viewer 3.36.10


# sudo snap install evince
# /snap/bin/evince --version
GNOME Document Viewer 42.3

The snap version opens the PDF just fine, the apt version doesn't ...
that is all ...

-- 
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 "The
  document contains no pages"

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---

  1. Open a document signed with DocuSign

  Expected behaviour:
  ---

  Document opens fine

  Actual behaviour:
  ---

  Evince refuses to display the document, with the error message "The
  document contains no pages".

  If document is opened with `pdftotext`, the output is:

  ```
  Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
  Syntax Error: Invalid XRef entry 3
  Syntax Error: Top-level pages object is wrong type (null)
  Command Line Error: Wrong page range given: the first page (1) can not be 
after the last page (0).
  ```

  Other information
  ---

  This appears to be a bug in libpoppler, described at
  https://stackoverflow.com/questions/66636441/pdf2image-library-
  failing-to-read-pdf-signed-using-docusign and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I
  believe that bumping the version of Poppler and/or Evince will solve
  the issue, though I have no way to test this as compiling from source
  is a significant undertaking.

  I do not have a public sample document that I could share, but
  examples of DocuSigned documents should be available online.

  Ubuntu version: 20.04 LTS (up to date)
  Evince version: 3.36.10 (official package)
  Poppler version: 0.86.1-0ubuntu1 (official package)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

2022-08-12 Thread joshyg6
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 "The
  document contains no pages"

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---

  1. Open a document signed with DocuSign

  Expected behaviour:
  ---

  Document opens fine

  Actual behaviour:
  ---

  Evince refuses to display the document, with the error message "The
  document contains no pages".

  If document is opened with `pdftotext`, the output is:

  ```
  Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
  Syntax Error: Invalid XRef entry 3
  Syntax Error: Top-level pages object is wrong type (null)
  Command Line Error: Wrong page range given: the first page (1) can not be 
after the last page (0).
  ```

  Other information
  ---

  This appears to be a bug in libpoppler, described at
  https://stackoverflow.com/questions/66636441/pdf2image-library-
  failing-to-read-pdf-signed-using-docusign and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I
  believe that bumping the version of Poppler and/or Evince will solve
  the issue, though I have no way to test this as compiling from source
  is a significant undertaking.

  I do not have a public sample document that I could share, but
  examples of DocuSigned documents should be available online.

  Ubuntu version: 20.04 LTS (up to date)
  Evince version: 3.36.10 (official package)
  Poppler version: 0.86.1-0ubuntu1 (official package)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

2021-09-24 Thread Sebastien Bacher
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 we would
SRU every single fix but we don't so have to focus on important issues,
it's not likely at this point that the problem will rank high enough to
be worked on by us.

It doesn't mean a fix can't be uploaded, it's opensource and a community
project, if someone was wanting to do the work to figure out which
commit fixed the problem and work on a stable update include it then
finding a sponsor should be doable

-- 
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 "The
  document contains no pages"

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---

  1. Open a document signed with DocuSign

  Expected behaviour:
  ---

  Document opens fine

  Actual behaviour:
  ---

  Evince refuses to display the document, with the error message "The
  document contains no pages".

  If document is opened with `pdftotext`, the output is:

  ```
  Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
  Syntax Error: Invalid XRef entry 3
  Syntax Error: Top-level pages object is wrong type (null)
  Command Line Error: Wrong page range given: the first page (1) can not be 
after the last page (0).
  ```

  Other information
  ---

  This appears to be a bug in libpoppler, described at
  https://stackoverflow.com/questions/66636441/pdf2image-library-
  failing-to-read-pdf-signed-using-docusign and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I
  believe that bumping the version of Poppler and/or Evince will solve
  the issue, though I have no way to test this as compiling from source
  is a significant undertaking.

  I do not have a public sample document that I could share, but
  examples of DocuSigned documents should be available online.

  Ubuntu version: 20.04 LTS (up to date)
  Evince version: 3.36.10 (official package)
  Poppler version: 0.86.1-0ubuntu1 (official package)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

2021-09-24 Thread Peter
@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 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 "The
  document contains no pages"

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---

  1. Open a document signed with DocuSign

  Expected behaviour:
  ---

  Document opens fine

  Actual behaviour:
  ---

  Evince refuses to display the document, with the error message "The
  document contains no pages".

  If document is opened with `pdftotext`, the output is:

  ```
  Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
  Syntax Error: Invalid XRef entry 3
  Syntax Error: Top-level pages object is wrong type (null)
  Command Line Error: Wrong page range given: the first page (1) can not be 
after the last page (0).
  ```

  Other information
  ---

  This appears to be a bug in libpoppler, described at
  https://stackoverflow.com/questions/66636441/pdf2image-library-
  failing-to-read-pdf-signed-using-docusign and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I
  believe that bumping the version of Poppler and/or Evince will solve
  the issue, though I have no way to test this as compiling from source
  is a significant undertaking.

  I do not have a public sample document that I could share, but
  examples of DocuSigned documents should be available online.

  Ubuntu version: 20.04 LTS (up to date)
  Evince version: 3.36.10 (official package)
  Poppler version: 0.86.1-0ubuntu1 (official package)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

2021-09-22 Thread Sebastien Bacher
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 Released

-- 
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 "The
  document contains no pages"

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---

  1. Open a document signed with DocuSign

  Expected behaviour:
  ---

  Document opens fine

  Actual behaviour:
  ---

  Evince refuses to display the document, with the error message "The
  document contains no pages".

  If document is opened with `pdftotext`, the output is:

  ```
  Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
  Syntax Error: Invalid XRef entry 3
  Syntax Error: Top-level pages object is wrong type (null)
  Command Line Error: Wrong page range given: the first page (1) can not be 
after the last page (0).
  ```

  Other information
  ---

  This appears to be a bug in libpoppler, described at
  https://stackoverflow.com/questions/66636441/pdf2image-library-
  failing-to-read-pdf-signed-using-docusign and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I
  believe that bumping the version of Poppler and/or Evince will solve
  the issue, though I have no way to test this as compiling from source
  is a significant undertaking.

  I do not have a public sample document that I could share, but
  examples of DocuSigned documents should be available online.

  Ubuntu version: 20.04 LTS (up to date)
  Evince version: 3.36.10 (official package)
  Poppler version: 0.86.1-0ubuntu1 (official package)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp