Public bug reported:
I'm having an occasional issue with evince, and since the issue is
clearly related to the PDF engine underneath which it uses (*this), I
got a tip to run a PDF directly with 'poppler-glib-demo' in the
'poppler-demos' package.
However, this tip was NOT suitable for Ubuntu, as there is nothing like a
'poppler-demos' package, but the whole package structure is different.
So this is one more for the wishlist.
poppler-glib-demo is not just a demo for developers, but will also show errors
that evince may be blamed for (for no reason at all). evince simply uses lots
of things under the hood, and one of them is poppler for PDF rendering.
ISTR that our Fedora colleagues do have this tool compiled in binary form and
included in the package.
As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no
longer do without it when building the Ubuntu poppler package.
Thanks for considering.
** Affects: poppler (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I'm having an occasional issue with evince, and since the issue is
clearly related to the PDF engine underneath which it uses (*this), I
got a tip to run a PDF directly with 'poppler-glib-demo' in the
'poppler-demos' package.
This is one more for the wishlist.
poppler-glib-demo is not just a demo for developers, but will also show
errors that evince may be blamed for (for no reason at all). evince simply uses
lots of things under the hood, and one of them is poppler for PDF rendering.
ISTR that our Fedora colleagues do have this tool compiled in binary form and
included in the package.
- As I think it might be pretty useful for bug-hunting, I'd ask you kindly to
no longer omit it when building the package.
+ As I think it might be pretty useful for bug-hunting, I'd ask you kindly to
no longer omit it when building the Ubuntu poppler package.
Thanks for considering.
** Description changed:
I'm having an occasional issue with evince, and since the issue is
clearly related to the PDF engine underneath which it uses (*this), I
got a tip to run a PDF directly with 'poppler-glib-demo' in the
'poppler-demos' package.
This is one more for the wishlist.
poppler-glib-demo is not just a demo for developers, but will also show
errors that evince may be blamed for (for no reason at all). evince simply uses
lots of things under the hood, and one of them is poppler for PDF rendering.
ISTR that our Fedora colleagues do have this tool compiled in binary form and
included in the package.
- As I think it might be pretty useful for bug-hunting, I'd ask you kindly to
no longer omit it when building the Ubuntu poppler package.
+ As I think it might be pretty useful for bug-hunting, I'd ask you kindly to
no longer do without it when building the Ubuntu poppler package.
Thanks for considering.
** Description changed:
I'm having an occasional issue with evince, and since the issue is
clearly related to the PDF engine underneath which it uses (*this), I
got a tip to run a PDF directly with 'poppler-glib-demo' in the
'poppler-demos' package.
- This is one more for the wishlist.
+ However, this tip was NOT suitable for Ubuntu, as there is nothing like a
'poppler-demos' package, but the whole package structure is different.
+ So this is one more for the wishlist.
poppler-glib-demo is not just a demo for developers, but will also show
errors that evince may be blamed for (for no reason at all). evince simply uses
lots of things under the hood, and one of them is poppler for PDF rendering.
ISTR that our Fedora colleagues do have this tool compiled in binary form and
included in the package.
As I think it might be pretty useful for bug-hunting, I'd ask you kindly to
no longer do without it when building the Ubuntu poppler package.
Thanks for considering.
--
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/1537895
Title:
Please include poppler-glib-demo tool in standard package
Status in poppler package in Ubuntu:
New
Bug description:
I'm having an occasional issue with evince, and since the issue is
clearly related to the PDF engine underneath which it uses (*this), I
got a tip to run a PDF directly with 'poppler-glib-demo' in the
'poppler-demos' package.
However, this tip was NOT suitable for Ubuntu, as there is nothing like a
'poppler-demos' package, but the whole package structure is different.
So this is one more for the wishlist.
poppler-glib-demo is not just a demo for developers, but will also show
errors that evince may be blamed for (for no reason at all). evince simply uses
lots of things under the hood, and one of them is poppler for PDF rendering.
ISTR that our Fedora colleagues do have this tool compiled in binary form and
included in the package.
As I think it might be pretty useful for bug-hunting, I'd ask you kindly to
no longer do without it when building the Ubuntu poppler package.
Thanks for considering.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1537895/+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
