Bug 407731 - can't open amazon invoices
Summary: can't open amazon invoices
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 1.7.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
: 407903 407988 416055 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-05-19 15:48 UTC by mauro.miatello
Modified: 2020-01-09 16:31 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash report (3.99 KB, text/plain)
2019-05-19 15:48 UTC, mauro.miatello
Details
amazon invoice (39.13 KB, application/pdf)
2019-05-19 15:53 UTC, mauro.miatello
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mauro.miatello 2019-05-19 15:48:57 UTC
Created attachment 120182 [details]
crash report

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.5
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12

ADDITIONAL INFORMATION
Comment 1 mauro.miatello 2019-05-19 15:53:15 UTC
Created attachment 120183 [details]
amazon invoice

this is an invoice i cant open
Comment 2 Albert Astals Cid 2019-05-19 18:13:01 UTC
What is your poppler version?
Comment 3 David Hurka 2019-05-19 21:38:26 UTC
Same behaviour here.
libpoppler-qt5-1:
Version: 0.62.0-2ubuntu2.8
Comment 4 Albert Astals Cid 2019-05-19 21:59:04 UTC
Your poppler is more than a year old.

I guess you're not a firefox user or you don't have a ~/.mozilla/firefox/*default* profile, right?
Comment 5 Albert Astals Cid 2019-05-22 13:41:45 UTC
a very basic and lame workaround while you get your distribution to give you a newer poppler would be so this file doesn't crash would be


mkdir -p ~/.mozilla/firefox/default
certutil -N -d ~/.mozilla/firefox/default

Can anyone confirm?
Comment 6 David Hurka 2019-05-22 18:06:49 UTC
Thats interesting: Create some files somewhere in the most abandoned ~/.mozilla/ directories, and poppler opens the PDF.

Yes, this workarround works for me.

> I guess you're not a firefox user or you don't have a
> ~/.mozilla/firefox/*default* profile, right?

Not me.
Comment 7 Albert Astals Cid 2019-05-22 20:54:12 UTC
There's nothing to fix, you just need a newer poppler version
Comment 8 mauro.miatello 2019-05-23 10:10:56 UTC
libpoppler-qt5-1:amd64 0.62.0-2ubuntu2.8 is the last version in kde neon, there is newer version? :O
Comment 9 Yuri Chornoivan 2019-05-23 10:15:21 UTC
(In reply to mauro.miatello from comment #8)
> libpoppler-qt5-1:amd64 0.62.0-2ubuntu2.8 is the last version in kde neon,
> there is newer version? :O

Yep. The current version is 0.76.1. Poppler is changing rapidly. Sorry for the troubles it may produce, but developers try to fix every single problem and release as often as possible.
Comment 10 Albert Astals Cid 2019-05-24 22:05:24 UTC
*** Bug 407903 has been marked as a duplicate of this bug. ***
Comment 11 mauro.miatello 2019-05-25 17:05:13 UTC
updating to 68 version doest solve

> dpkg -l | grep poppler
ii  libpoppler-glib8:amd64                        0.68.0-0ubuntu1.6
ii  libpoppler-qt5-1:amd64                        0.68.0-0ubuntu1.6
ii  libpoppler73:amd64                            0.62.0-2ubuntu2.8
ii  libpoppler79:amd64                            0.68.0-0ubuntu1.6
ii  poppler-data                                  0.4.9-2          
ii  poppler-utils                                 0.68.0-0ubuntu1.6
Comment 12 Albert Astals Cid 2019-05-25 22:03:08 UTC
poppler 0.68 is still almost a year old.

If you're not a firefox user (and thus don't have a firefox nssdb that can be used) you want at least poppler 0.72
Comment 13 David Hurka 2019-05-25 22:32:36 UTC
The firefox nssdb is used to verify that the digital signatures are "cryptografically valid", whatever *exactly* that means, I guess?
Comment 14 Albert Astals Cid 2019-05-25 22:49:06 UTC
it's used to check for trust, not validness.
Comment 15 hds 2019-05-27 15:49:57 UTC
*** Bug 407988 has been marked as a duplicate of this bug. ***
Comment 16 Yuri Chornoivan 2020-01-09 16:31:18 UTC
*** Bug 416055 has been marked as a duplicate of this bug. ***