[okular] [Bug 462304] New: Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 Bug ID: 462304 Summary: Okular and other poppler related tools cannot handle some pdf pages Classification: Applications Product: okular Version: 22.08.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: cipri...@gmail.com Target Milestone: --- Created attachment 154078 --> https://bugs.kde.org/attachment.cgi?id=154078&action=edit example of the pdf page Okular views as blank Okular cannot see the content of many pages of an old scanned book. they appear blank although many other tools can see them just fine (internet browser except Falkon, Adobe Reader, Foxit, Master PDF, WPS PDF, LibreOffice Draw, ImageMagick, mupdf, PDF Studio Viewer). The problem seems to be with poppler, because qpdfviewer and Falkon have the same problem. As far as I could test Evince cannot even open that pdf. I couldn't get technical details on that type of page, so I'll upload here a sample. More details at links posted here: https://www.reddit.com/r/kde/comments/z591ia/how_come_only_okular_cannot_see_this_pdf_page/?utm_source=share&utm_medium=web2x&context=3 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #1 from cipricus --- > internet browser except Falkon, Adobe Reader, Foxit, Master PDF, WPS PDF, > LibreOffice Draw, ImageMagick, mupdf, PDF Studio Viewer What I mean is: only Okular, qpdfview, Falkon and Evince seem affected; the rest of the tools that I've tested (internet browsers - excepting Falkon -, Adobe Reader, Foxit, Master PDF, WPS PDF, LibreOffice Draw, ImageMagick, mupdf, PDF Studio Viewer) are not affected. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #2 from cipricus --- Comment on attachment 154078 --> https://bugs.kde.org/attachment.cgi?id=154078 example of the pdf page Okular views as blank Open that in Okular or qpdfview: only a footer is see. Open it in an internet browser other than Falkon, in adobe Reader, Foxit reader, mupdf, Master pdf etc and the page is seen in full. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #3 from cipricus --- If that page is printed as pdf in Firefox or (after selecting "print as image") in Chromium/Chrome-based browsers, the resulting pdf is seen ok in Okular. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462312] New: Okular crash on editing form
https://bugs.kde.org/show_bug.cgi?id=462312 Bug ID: 462312 Summary: Okular crash on editing form Classification: Applications Product: okular Version: 22.08.3 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: sylvain.bouc...@gmail.com Target Milestone: --- Application: okular (22.08.3) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 5.15.0-53-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: When I edit a form (already used without problem) at the first letter I press, it crashes The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7f0bc9e24bc8 in GfxResources::doLookupFont(char const*) const () from /lib/x86_64-linux-gnu/libpoppler.so.124 #5 0x7f0bc9e24d42 in GfxResources::lookupFont(char const*) () from /lib/x86_64-linux-gnu/libpoppler.so.124 #6 0x7f0bc9e193f8 in Form::ensureFontsForAllCharacters(GooString const*, std::__cxx11::basic_string, std::allocator > const&, GfxResources*) () from /lib/x86_64-linux-gnu/libpoppler.so.124 #7 0x7f0bc9e1a4f3 in ?? () from /lib/x86_64-linux-gnu/libpoppler.so.124 #8 0x7f0bca0a630c in Poppler::FormFieldText::setText(QString const&) () from /lib/x86_64-linux-gnu/libpoppler-qt5.so.1 #9 0x7f0bf440b29d in ?? () from /lib/x86_64-linux-gnu/libOkular5Core.so.10 #10 0x7f0c05924819 in QUndoStack::push(QUndoCommand*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f0bf4578f7a in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #12 0x7f0c04a220f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0bf457d311 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #14 0x7f0c04a220f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0c056beef9 in QLineEdit::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f0c056bc3d8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f0c04a22128 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f0c056c6709 in QWidgetLineControl::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f0c056c9e9b in QWidgetLineControl::finishChange(int, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f0c056ccb34 in QWidgetLineControl::processKeyEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f0c056befff in QLineEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f0c055b6708 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f0c05572763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f0c0557a4de in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f0c049ea09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f0c055d23ff in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f0c05572763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f0c049ea09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f0c04e63bfa in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x7f0bfe0ab0a4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so #31 0x7f0c04a220f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f0c04d039d3 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #33 0x7f0c04a17afe in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f0c05572763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x7f0c049ea09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f0c049ed187 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f0c04a444a7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7f0c02f9ad1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7f0c02fef6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #40 0x7f0c02f983c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #41 0x
[okular] [Bug 462312] Okular crash on editing form
https://bugs.kde.org/show_bug.cgi?id=462312 --- Comment #1 from Sylvain Bouchet --- Created attachment 154082 --> https://bugs.kde.org/attachment.cgi?id=154082&action=edit the form is in this pdf -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Nicolas Fella --- When opening that file poppler prints "Bogus memory allocation size". Presumably because the embedded image data is too large in some way. The allocation seems to come from https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/poppler/JBIG2Stream.cc#L1575 numInputSyms is 0, numNewSyms is 3092673499. 3092673499 is larger than 2^31 and smaller than 2^32. It is stored as unsigned int, so that's fine, but when passing that to gmallocn_checkoverflow it gets converted to int causing an overflow. Once it reaches https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/goo/gmem.h#L112 count is -1202293797 and the allocation fails -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #5 from Oliver Sander --- Can you post a poppler bug for this, please? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462312] Okular crash on editing form
https://bugs.kde.org/show_bug.cgi?id=462312 --- Comment #2 from Sylvain Bouchet --- For your information, I've recently update my system to be neon based on ubuntu 22.04 LTS -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462321] New: Left panel's header is insanely thick
https://bugs.kde.org/show_bug.cgi?id=462321 Bug ID: 462321 Summary: Left panel's header is insanely thick Classification: Applications Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: shenlebantongy...@gmail.com Target Milestone: --- Created attachment 154087 --> https://bugs.kde.org/attachment.cgi?id=154087&action=edit Okular's current left panel and its insanly duplicated info Check the attachment, the left panel's head has 3 components expressing the same thing. I think that huge head is the reason why i feel okular's "top area" is so "heavy". I propose to remove the the word "Thumbnail", "Contents" which are completely useless after reading the icon meanings. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #6 from cipricus --- (In reply to Oliver Sander from comment #5) > Can you post a poppler bug for this, please? Are you addressing me or the previous comment? Should I post that bug? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 436709] Autoplaying of renditions (audio/video)
https://bugs.kde.org/show_bug.cgi?id=436709 Cimbali changed: What|Removed |Added CC||m...@cimba.li --- Comment #3 from Cimbali --- I can also confirm that Acrobat does treat the /A flag as “autoplay when activated” and not “activate automatically” as Okular does. The flag is poorly named, but the spec says (quote is from 1.7, table 9.15): > A boolean (Optional) If true, the media should automatically play when > activated. If false, the media should be initially paused when activated (for > example, the first frame is displayed). Relevant only for media that may be > paused. Default value: true. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462342] New: Smart index to support multi document research
https://bugs.kde.org/show_bug.cgi?id=462342 Bug ID: 462342 Summary: Smart index to support multi document research Classification: Applications Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: thorsten.s...@email.de Target Milestone: --- I want to be able to generate an index on a document by marking a word/phrase and select "add to index". In this document and other documents I open those words will then be marked and become a link to this document and page. This index could be stored in the Okular document archive. And all documents belonging together will also be stored there. A "back" button/hotkey would also be convenient so I can travel back to where the trip through the documents started. Reason: I have several research projects spanning multiple documents. It would be much simpler when I could just create the index to the main source. Later I can just hop between the documents by clicking the generated links to those indexed positions. Thanks -- You are receiving this mail because: You are the assignee for the bug.
