[okular] [Bug 342003] Trim margins confuses ordering of zoom steps while zooming out
https://bugs.kde.org/show_bug.cgi?id=342003 Luca Weiss changed: What|Removed |Added CC||l...@z3ntu.xyz --- Comment #17 from Luca Weiss --- Still an issue in Okular v1.11.1 (KDE Applications 20.08.1) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 401999] Pictures inserted into PDF with other PDF Editor covered by stamp icon
https://bugs.kde.org/show_bug.cgi?id=401999 Luca Weiss changed: What|Removed |Added CC||l...@z3ntu.xyz --- Comment #9 from Luca Weiss --- I believe I'm seeing the same problem with a PDF document with Okular 1.10.3 on Arch Linux. Right clicking on the "stamp" shows "Stamp symbol: #clipboard". Moving the stamp keeps the actual image underneath (making it possible to view it), but the image likes to just disappear completely when scrolling/zooming and the document has to be re-opened to view the image again. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 416176] Find menu: Shift + numpad enter does not go to previous match
https://bugs.kde.org/show_bug.cgi?id=416176 --- Comment #2 from Luca Weiss --- Yes, Shift+F3 works as well but as Shift+Enter is a standard shortcut (and it *mostly* works in Okular) I am quite used to using Enter & Shift+Enter. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 416176] New: Find menu: Shift + numpad enter does not go to previous match
https://bugs.kde.org/show_bug.cgi?id=416176
Bug ID: 416176
Summary: Find menu: Shift + numpad enter does not go to
previous match
Product: okular
Version: 19.12.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-devel@kde.org
Reporter: l...@z3ntu.xyz
Target Milestone: ---
SUMMARY
In the Okular search field (Ctrl+F) you can press Enter to go to the next match
and Shift+Enter to go to the previous match. Pressing the enter key on the
numpad goes to the next match but pressing Shift+numpad Enter still goes to the
next match and not to the previous.
STEPS TO REPRODUCE
1. Open search bar on a .pdf document and enter a search string
2. Press Shift+Enter ("Return") to get to the previous match
3. Press Shift+numpad enter ("KP_Enter") and observe that Okular jumps to the
next match instead of the previous
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0
ADDITIONAL INFORMATION
I've just checked in KMail in the mail view search field and funnily enough
there the behavior is the other way around, numpad enter doesn't work but
shift+numpad enter works.
Also I've read through the Okular source code a bit and it doesn't seem like
the bug is caused by Okular because it uses the returnPressed signal from
KLineEdit (which is QLineEdit?, didn't check that) and then checks
"QApplication::keyboardModifiers() == Qt::ShiftModifier" and not much more.
Still, it's a bug that's present in Okular :)
Also maybe
https://cgit.kde.org/falkon.git/commit/?id=a237c8ff874a2adeed8588709f14fdb3b766fa2f
is useful
--
You are receiving this mail because:
You are the assignee for the bug.
[okular] [Bug 392826] Crash when opening .xps file
https://bugs.kde.org/show_bug.cgi?id=392826 --- Comment #2 from Luca Weiss --- Thanks for the quick fix! :) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 392826] New: Crash when opening .xps file
https://bugs.kde.org/show_bug.cgi?id=392826 Bug ID: 392826 Summary: Crash when opening .xps file Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: XPS backend Assignee: okular-devel@kde.org Reporter: l...@z3ntu.xyz Target Milestone: --- Created attachment 111885 --> https://bugs.kde.org/attachment.cgi?id=111885&action=edit demo file Just opening the attached .xps file makes Okular crash. Version is master branch today (revision b25979121fd3f28788a2958b0faed250f1d1054c) Backtrace: #0 0x7f99642bd89c in loadEntry(KZip*, QString const&, Qt::CaseSensitivity) [clone .constprop.299] () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #1 0x7f99642c2d6b in XpsPage::loadImageFromFile(QString const&) () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #2 0x7f99642c301c in XpsHandler::processImageBrush(XpsRenderNode&) () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #3 0x7f99642c3b0e in XpsHandler::processEndElement(XpsRenderNode&) () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #4 0x7f99642c425d in XpsHandler::endElement(QString const&, QString const&, QString const&) () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #5 0x7f99876dc478 in ?? () from /usr/lib/libQt5Xml.so.5 #6 0x7f99876e58ff in ?? () from /usr/lib/libQt5Xml.so.5 #7 0x7f99876e4e48 in ?? () from /usr/lib/libQt5Xml.so.5 #8 0x7f99876e5880 in ?? () from /usr/lib/libQt5Xml.so.5 #9 0x7f99876e4e48 in ?? () from /usr/lib/libQt5Xml.so.5 #10 0x7f99876e5880 in ?? () from /usr/lib/libQt5Xml.so.5 #11 0x7f99876e4e48 in ?? () from /usr/lib/libQt5Xml.so.5 #12 0x7f99876e5880 in ?? () from /usr/lib/libQt5Xml.so.5 #13 0x7f99876e845c in ?? () from /usr/lib/libQt5Xml.so.5 #14 0x7f99876e8977 in QXmlSimpleReader::parse(QXmlInputSource const*, bool) () from /usr/lib/libQt5Xml.so.5 #15 0x7f99642c2850 in XpsPage::renderToPainter(QPainter*) () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #16 0x7f99642c2a32 in XpsPage::renderToImage(QImage*) () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #17 0x7f99642c2b4d in XpsGenerator::image(Okular::PixmapRequest*) () from /usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so #18 0x7f996eca15f5 in Okular::PixmapGenerationThread::run() () from /usr/lib/libOkular5Core.so.9 #19 0x7f993acd in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7f998517508c in start_thread () from /usr/lib/libpthread.so.0 #21 0x7f998818be7f in clone () from /usr/lib/libc.so.6 If the backtrace in the Qt5 libs is needed, I can recompile it. -- You are receiving this mail because: You are the assignee for the bug.
