[okular] [Bug 449709] Print Color Mode: not possible to print in black-white
https://bugs.kde.org/show_bug.cgi?id=449709 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #9 from Erik Quaeghebeur --- Created attachment 171292 --> https://bugs.kde.org/attachment.cgi?id=171292&action=edit system-config-printer printer option window on job options page with print-color-mode option highlighted My guess is, that this bug is related to a changed CUPS behavior. See https://github.com/OpenPrinting/cups/issues/421 and https://github.com/OpenPrinting/system-config-printer/issues/312. Namely, a default job option is set (print-color-mode monochrome/color) that does not seem to be overridden when selecting the color mode in the Advanced settings tab. It is not clear to me whether Okular is at fault here, but it possibly is, as system-config-printer does expose this job option. In any case—but this is likely bigger than this bug—it would be good if the print dialog also exposes the color mode for physical printers as it now does for print-to-pdf in the Options tab, next to the Double Sided Printing option. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449709] Print Color Mode: not possible to print in black-white
https://bugs.kde.org/show_bug.cgi?id=449709 Erik Quaeghebeur changed: What|Removed |Added CC||aman...@kde.org --- Comment #8 from Erik Quaeghebeur --- *** Bug 478631 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 478631] Printing settings are ignored
https://bugs.kde.org/show_bug.cgi?id=478631 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 449709 *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 481362] Okular crashes right after adding signature
https://bugs.kde.org/show_bug.cgi?id=481362 Erik Quaeghebeur changed: What|Removed |Added Version|23.08.4 |23.08.5 --- Comment #4 from Erik Quaeghebeur --- Still present in 23.08.5 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 481362] Okular crashes right after adding signature
https://bugs.kde.org/show_bug.cgi?id=481362 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #1) > Can you share the pdf you signed (before signing it) or it contains private > info? Sorry, it contains private info. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 481362] New: Okular crashes right after adding signature
https://bugs.kde.org/show_bug.cgi?id=481362 Bug ID: 481362 Summary: Okular crashes right after adding signature Classification: Applications Product: okular Version: 23.08.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: okular (23.08.4) (Compiled from sources) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 6.6.13-gentoo-a x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I was signing a pdf form. Right after signing, Okular crashed. (The signed pdf was properly generated, though.) In all recent times I used Okular to sign a pdf, it did not crash. The only thing that was different now is that I had mistyped my smartcard pin code once. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7b225c7857d3 in Okular::Page::number (this=0x56d4feb285e0) at /var/tmp/portage/kde-apps/okular-23.08.4/work/okular-23.08.4/core/page.cpp:162 #5 0x7b226ff86126 in SignaturePartUtils::signUnsignedSignature (form=0x56d4febece70, pageView=0x56d4fe1f7950, doc=0x56d4fe0608d0) at /var/tmp/portage/kde-apps/okular-23.08.4/work/okular-23.08.4/part/signaturepartutils.cpp:409 #6 0x7b22818c6b64 in QtPrivate::QSlotObjectBase::call (a=0x7fff560a4ed0, r=0x56d4fecc7f40, this=0x56d4fecc7d90) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x56d4fecc7f40, signal_index=9, argv=0x7fff560a4ed0) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3925 #8 0x7b22818c0897 in QMetaObject::activate (sender=sender@entry=0x56d4fecc7f40, m=m@entry=0x7b2282896240 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff560a4ed0) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3985 #9 0x7b228245b182 in QAbstractButton::clicked (this=this@entry=0x56d4fecc7f40, _t1=) at .moc/moc_qabstractbutton.cpp:308 #10 0x7b228245b3da in QAbstractButtonPrivate::emitClicked (this=0x56d4fe12f520) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qabstractbutton.cpp:416 #11 0x7b228245cf97 in QAbstractButtonPrivate::click (this=0x56d4fe12f520) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qabstractbutton.cpp:409 #12 0x7b228245d1c3 in QAbstractButton::mouseReleaseEvent (this=0x56d4fecc7f40, e=0x7fff560a5480) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qabstractbutton.cpp:1045 #13 0x7b22823a6fa8 in QWidget::event (this=0x56d4fecc7f40, event=0x7fff560a5480) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:9045 #14 0x7b22823631ee in QApplicationPrivate::notify_helper (this=this@entry=0x56d4fdd026e0, receiver=receiver@entry=0x56d4fecc7f40, e=e@entry=0x7fff560a5480) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3640 #15 0x7b228236b8f2 in QApplication::notify (this=, receiver=0x56d4fecc7f40, e=0x7fff560a5480) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3084 #16 0x7b2281893a08 in QCoreApplication::notifyInternal2 (receiver=0x56d4fecc7f40, event=0x7fff560a5480) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1064 #17 0x7b2281893c0e in QCoreApplication::sendSpontaneousEvent (receiver=, event=) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1474 #18 0x7b2282369bf4 in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x56d4fecc7f40, event=event@entry=0x7fff560a5480, alienWidget=, nativeWidget=0x56d4fde232d0, buttonDown=buttonDown@entry=0x7b22828bf9d0 , lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:2622 #19 0x7b22823c0553 in QWidgetWindow::handleMouseEvent (this=this@entry=0x56d4fe9627e0, event=event@entry=0x7fff560a5750) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidgetwindow.cpp:684 #20 0x7b22823c396f in QWidgetWindow::event (this=0x56d4fe9627e0, event=0x7fff
[okular] [Bug 475798] Okular crashes right after applying digital signature
https://bugs.kde.org/show_bug.cgi?id=475798 --- Comment #8 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #3) > Any chance you can upgrade to KF5 5.111 and see if that fixes the issue? Tried with 5.112 and I could not reproduce the issue. (Running with Valgrind still gives many “blocks are possibly lost in loss record” messages.) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 475798] Okular crashes right after applying digital signature
https://bugs.kde.org/show_bug.cgi?id=475798 Erik Quaeghebeur changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #3) > Any chance you can upgrade to KF5 5.111 and see if that fixes the issue? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 475798] Okular crashes right after applying digital signature
https://bugs.kde.org/show_bug.cgi?id=475798 --- Comment #6 from Erik Quaeghebeur --- (In reply to Bug Janitor Service from comment #5) > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. Please keep this open. I'm aware, but just awaiting stabilization for my distribution. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 475798] Okular crashes right after applying digital signature
https://bugs.kde.org/show_bug.cgi?id=475798 --- Comment #4 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #3) > Any chance you can upgrade to KF5 5.111 and see if that fixes the issue? I'll do that once my distribution stabilizes it. I'll report back once that happens. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 475798] Okular crashes right after applying digital signature
https://bugs.kde.org/show_bug.cgi?id=475798 --- Comment #2 from Erik Quaeghebeur --- Created attachment 162445 --> https://bugs.kde.org/attachment.cgi?id=162445&action=edit output of valgrind when running okular to sign a document using a smartcard (In reply to Albert Astals Cid from comment #1) > Can you install valgrind and run > > valgrind okular > > It will be slow. And then do the same thing you do to make it crash? > > Once done, even if it doesn't crash, please attach the output of valgrind > here. Attached. It did not crash this time. (I closed the okular windows, so also the one opened after creating the signed document, to stop the processing by valgrind.) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 475798] New: Okular crashes right after applying digital signature
https://bugs.kde.org/show_bug.cgi?id=475798 Bug ID: 475798 Summary: Okular crashes right after applying digital signature Classification: Applications Product: okular Version: 23.04.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: okular (23.04.3) (Compiled from sources) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.1.53-gentoo-r1-a x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: When signing a pdf form in okular (with a certificate on a smartcard), it often but not always crashes right after the signature is applied. So I can reopen pdf and verify that the signature has been applied. The crash can be reproduced sometimes. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7a6152f368e3 in Okular::Page::number (this=0x5ccebd63cc90) at /var/tmp/portage/kde-apps/okular-23.04.3/work/okular-23.04.3/core/page.cpp:162 #5 0x7a615238649d in SignaturePartUtils::signUnsignedSignature (form=0x5ccebda8beb0, pageView=0x5ccebcc68350, doc=0x5ccebca9d8b0) at /var/tmp/portage/kde-apps/okular-23.04.3/work/okular-23.04.3/part/signaturepartutils.cpp:120 #6 0x7a617a4c5ea4 in QtPrivate::QSlotObjectBase::call (a=0x7ffeea71a4d0, r=0x5ccebd87ac30, this=0x5ccebd87aa80) at /var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x5ccebd87ac30, signal_index=9, argv=0x7ffeea71a4d0) at /var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3925 #8 0x7a617a4bfbd7 in QMetaObject::activate (sender=sender@entry=0x5ccebd87ac30, m=m@entry=0x7a617b496240 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffeea71a4d0) at /var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3985 #9 0x7a617b05b0a2 in QAbstractButton::clicked (this=this@entry=0x5ccebd87ac30, _t1=) at .moc/moc_qabstractbutton.cpp:308 #10 0x7a617b05b2fa in QAbstractButtonPrivate::emitClicked (this=0x5ccebd084c10) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/widgets/qabstractbutton.cpp:416 #11 0x7a617b05ceb7 in QAbstractButtonPrivate::click (this=0x5ccebd084c10) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/widgets/qabstractbutton.cpp:409 #12 0x7a617b05d0e3 in QAbstractButton::mouseReleaseEvent (this=0x5ccebd87ac30, e=0x7ffeea71aa80) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/widgets/qabstractbutton.cpp:1045 #13 0x7a617afa6fa8 in QWidget::event (this=0x5ccebd87ac30, event=0x7ffeea71aa80) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qwidget.cpp:9045 #14 0x7a617af631de in QApplicationPrivate::notify_helper (this=this@entry=0x5ccebc7606e0, receiver=receiver@entry=0x5ccebd87ac30, e=e@entry=0x7ffeea71aa80) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qapplication.cpp:3640 #15 0x7a617af6b8e2 in QApplication::notify (this=, receiver=0x5ccebd87ac30, e=0x7ffeea71aa80) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qapplication.cpp:3084 #16 0x7a617a492d48 in QCoreApplication::notifyInternal2 (receiver=0x5ccebd87ac30, event=0x7ffeea71aa80) at /var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qcoreapplication.cpp:1064 #17 0x7a617a492f4e in QCoreApplication::sendSpontaneousEvent (receiver=, event=) at /var/tmp/portage/dev-qt/qtcore-5.15.10-r2/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qcoreapplication.cpp:1474 #18 0x7a617af69be4 in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x5ccebd87ac30, event=event@entry=0x7ffeea71aa80, alienWidget=, nativeWidget=0x5ccebc89a1c0, buttonDown=buttonDown@entry=0x7a617b4bf9d0 , lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qapplication.cpp:2622 #19 0x7a617afc0573 in QWidgetWindow::handleMouseEvent (this=this@entry=0x5ccebd39ee60, event=event@entry=0x7ffeea71ad50) at /var/tmp/portage/dev-qt/qtwidgets-5.15.10-r3/work/qtbase-everywhere-src-5.15.10/src/widgets/kernel/qwidgetwindow.cpp:684 #20 0x7a617afc398f in QWidgetWindow::event (this=0x5ccebd39ee60, event=0x7ffeea71ad50) at /var/tmp/portage/dev-qt/
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 435104] Removing author for annotations in settings is undone almost immediately
https://bugs.kde.org/show_bug.cgi?id=435104 --- Comment #7 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #4) > (In reply to Yuri Chornoivan from comment #3) > > > > In the "Annotations" page of the configuration dialog, remove all data from > > the "Author" field. Press "OK" to close the dialog. Although no messages > > appear, Okular restores the previous "Author" field content. It can be seen > > in the new annotations. > > That doesn't happen here. Which version is that on? So that likely means that this bug was fixed somewhere after 1.11.3. I guess this may be closed as fixed then. I can reopen in case it is still present after I upgrade. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 435104] New: Removing author for annotations in settings is undone almost immediately
https://bugs.kde.org/show_bug.cgi?id=435104 Bug ID: 435104 Summary: Removing author for annotations in settings is undone almost immediately Product: okular Version: 1.11.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- SUMMARY I need to create a review of a paper with anonymous annotations. If I remove the author field content in Okular settings, it is put back automatically, so that it becomes undoable to create anonymous annotations. That should not happen; my preferences should persist. I could live with it persisting only for as long as the Okular instance is open. STEPS TO REPRODUCE 1. Remove author in Okular settings 2. Annotate 3. Annotate … OBSERVED RESULT At some point, new annotations get my name as author again, instead of an empty string. EXPECTED RESULT Annotations keep having no author. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 198427] Hyperlink hopping is inaccurate when "trim margins" is on
https://bugs.kde.org/show_bug.cgi?id=198427 Erik Quaeghebeur changed: What|Removed |Added Version|0.8.4 |1.11.3 --- Comment #6 from Erik Quaeghebeur --- (In reply to Justin Zobel from comment #5) > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. The issue still persists (I tested again). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 340513] [wish] cursor based navigation
https://bugs.kde.org/show_bug.cgi?id=340513 Erik Quaeghebeur changed: What|Removed |Added Version|0.19.3 |1.7.3 CC||k...@equaeghe.nospammail.net --- Comment #4 from Erik Quaeghebeur --- Still a very interesting wishlist item for 1.7.3. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 332835] Feature request: Insert text and replace text annotation
https://bugs.kde.org/show_bug.cgi?id=332835 --- Comment #7 from Erik Quaeghebeur --- (In reply to Simone Gaiarin from comment #5) > - Red underline means deletion N.B.: You can configure available annotations in Okular (Settings->Configure Okular->Annotations). Deletion should be available (add a 'Text markup' annotation tool with Type 'Strike out'). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 376459] Add crossout and replace annotations
https://bugs.kde.org/show_bug.cgi?id=376459 Erik Quaeghebeur changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||k...@equaeghe.nospammail.net --- Comment #2 from Erik Quaeghebeur --- Given that cross-out is available as mentioned by Jonathan, this is a duplicate of Bug 332835. *** This bug has been marked as a duplicate of bug 332835 *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 332835] Feature request: Insert text and replace text annotation
https://bugs.kde.org/show_bug.cgi?id=332835 Erik Quaeghebeur changed: What|Removed |Added CC||paole...@gmail.com --- Comment #6 from Erik Quaeghebeur --- *** Bug 376459 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396002] Review/Annotation tool selection with double click not persisting on page scroll
https://bugs.kde.org/show_bug.cgi?id=396002 Erik Quaeghebeur changed: What|Removed |Added Version|1.4.2 |1.7.3 CC||k...@equaeghe.nospammail.net --- Comment #3 from Erik Quaeghebeur --- Still present in 19.04/1.73. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 403914] Crash when closing okular trying to show file accessed via sftp
https://bugs.kde.org/show_bug.cgi?id=403914 --- Comment #2 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #1) > can you reproduce this crash? No, currently not (on 1.6.3). Feel free to close. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 405502] New: Okular crashes when trying to reopen document on unmounted filesystem
https://bugs.kde.org/show_bug.cgi?id=405502 Bug ID: 405502 Summary: Okular crashes when trying to reopen document on unmounted filesystem Product: okular Version: 1.5.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- Application: okular (1.5.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.27-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: The desktop environment was restarting. Previously, some pdfs were open in Okular. Before the restart, the filesystem on which those files were located was unmounted, so they were not there anymore. I guess Okular should just report that the file is not present instead of crashing because of it. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f51be01a180 (LWP 7009))] Thread 3 (Thread 0x7f5195145700 (LWP 7101)): #0 0x7f51b701056c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f51958901eb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f519588ff17 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f51b700996a in start_thread () from /lib64/libpthread.so.0 #4 0x7f51b9daa92f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f51a0c03700 (LWP 7026)): #0 0x7f51b9d9ed63 in poll () from /lib64/libc.so.6 #1 0x7f51b4a100b9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f51b4a101cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f51ba70965b in QEventDispatcherGlib::processEvents (this=0x7f519c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f51ba6b985b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f51ba5326c6 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f51bab52de5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f51ba53b69b in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #8 0x7f51b700996a in start_thread () from /lib64/libpthread.so.0 #9 0x7f51b9daa92f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f51be01a180 (LWP 7009)): [KCrash Handler] #6 0x7f51bc2099c3 in QMapData::findNode (this=0x20, akey=...) at /usr/include/qt5/QtCore/qmap.h:284 #7 0x7f51bc20ecab in QMap::constFind (akey=..., this=0x55a50872c5f0) at /usr/include/qt5/QtCore/qmap.h:869 #8 QMap::find (akey=..., this=0x55a50872c5f0) at /usr/include/qt5/QtCore/qmap.h:876 #9 KEntryMap::findEntry (this=this@entry=0x55a50872c5f0, group=..., key=..., flags=..., flags@entry=...) at /var/tmp/portage/kde-frameworks/kconfig-5.54.0-r1/work/kconfig-5.54.0/src/core/kconfigdata.cpp:74 #10 0x7f51bc2032f7 in KConfigPrivate::lookupData (this=this@entry=0x55a50872c5d0, group=..., key=key@entry=0x55a507f8bb42 "ActiveTab", flags=..., flags@entry=...) at /var/tmp/portage/kde-frameworks/kconfig-5.54.0-r1/work/kconfig-5.54.0/src/core/kconfig.cpp:1024 #11 0x7f51bc2187dc in KConfigGroup::readEntry (this=this@entry=0x7fff51f7c0f0, key=key@entry=0x55a507f8bb42 "ActiveTab", aDefault=...) at /var/tmp/portage/kde-frameworks/kconfig-5.54.0-r1/work/kconfig-5.54.0/src/core/kconfiggroup.cpp:725 #12 0x55a507f84de3 in KConfigGroup::readEntry (defaultValue=@0x7fff51f7c03c: 0, key=0x55a507f8bb42 "ActiveTab", this=0x7fff51f7c0f0) at /usr/include/KF5/KConfigCore/kconfiggroup.h:723 #13 Shell::readProperties (this=0x55a5084aea90, group=...) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/shell/shell.cpp:392 #14 0x7f51bd191858 in KMainWindow::readPropertiesInternal (this=this@entry=0x55a5084aea90, config=0x55a5084b7720, number=number@entry=1) at /var/tmp/portage/kde-frameworks/kxmlgui-5.54.0-r1/work/kxmlgui-5.54.0/src/kmainwindow.cpp:652 #15 0x7f51bd1918a2 in KMainWindow::restore (this=0x55a5084aea90, number=1, show=) at /var/tmp/portage/kde-frameworks/kxmlgui-5.54.0-r1/work/kxmlgui-5.54.0/src/kmainwindow.cpp:473 #16 0x55a507f800db in kRestoreMainWindows () at /usr/include/KF5/KXmlGui/kmainwindow.h:719 #17 0x55a507f7d822 in main (argc=, argv=) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/shell/main.cpp:64 The reporter indicates this bug may be a duplicate of or related to bug 402397. Possible duplicates by query: bug 402397, bug 395913, bug 395869, bug 395779, bug 395613. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 403914] New: Crash when closing okular trying to show file accessed via sftp
https://bugs.kde.org/show_bug.cgi?id=403914 Bug ID: 403914 Summary: Crash when closing okular trying to show file accessed via sftp Product: okular Version: 1.5.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- Application: okular (1.5.3) Qt Version: 5.11.3 Frameworks Version: 5.52.0 Operating System: Linux 4.14.83-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I was closing okular, which was trying to show file accessed via sftp. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0383b0f180 (LWP 20084))] Thread 4 (Thread 0x7f035ad55700 (LWP 20087)): #0 0x7f037cb2b56c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f035b4a01eb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f035b49ff17 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f037cb2496a in start_thread () from /lib64/libpthread.so.0 #4 0x7f037f8bd92f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f038700 (LWP 20086)): #0 0x7f037f8b1d63 in poll () from /lib64/libc.so.6 #1 0x7f037a52e0b9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f037a52e1cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0380217f5b in QEventDispatcherGlib::processEvents (this=0x7f036b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f03801c3ffa in QEventLoop::exec (this=this@entry=0x7f037cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f0380027f5a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f0380650de5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f03800319af in QThreadPrivate::start (arg=0x7f03808c8d60) at thread/qthread_unix.cpp:367 #8 0x7f037cb2496a in start_thread () from /lib64/libpthread.so.0 #9 0x7f037f8bd92f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f03709fe700 (LWP 20085)): #0 0x7f037f8b1d63 in poll () from /lib64/libc.so.6 #1 0x7f037d3a17f7 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f037d3a342a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f0372f71779 in QXcbEventReader::run (this=0x55bbd2402d70) at qxcbconnection.cpp:1391 #4 0x7f03800319af in QThreadPrivate::start (arg=0x55bbd2402d70) at thread/qthread_unix.cpp:367 #5 0x7f037cb2496a in start_thread () from /lib64/libpthread.so.0 #6 0x7f037f8bd92f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0383b0f180 (LWP 20084)): [KCrash Handler] #6 0x7f0364c231d7 in Okular::Generator::hasFeature (this=0x0, feature=feature@entry=Okular::Generator::SupportsCancelling) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/core/generator.cpp:425 #7 0x7f0364c0a2de in Okular::DocumentPrivate::clearAndWaitForRequests (this=0x55bbd24fa2a0) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/core/document.cpp:2189 #8 0x7f0364c0b5a0 in Okular::Document::closeDocument (this=0x55bbd25083d0) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/core/document.cpp:2646 #9 0x7f0364f26e15 in Okular::Part::closeUrl (this=0x55bbd24e2730, promptToSave=) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/part.cpp:1831 #10 0x55bbd172b7b4 in Shell::closeTab (this=0x55bbd2464e60, tab=0) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/shell/shell.cpp:631 #11 0x55bbd172b8eb in Shell::closeUrl (this=) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/shell/shell.cpp:303 #12 0x55bbd1732e55 in Shell::qt_static_metacall (_o=, _id=, _a=0x7ffdc43fccf0, _c=QMetaObject::InvokeMetaMethod) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3_build/shell/okular_autogen/EWIEGA46WW/moc_shell.cpp:189 #13 0x55bbd173300a in Shell::qt_static_metacall (_o=, _c=, _id=, _a=) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3_build/shell/okular_autogen/EWIEGA46WW/moc_shell.cpp:171 #14 0x7f03801ee6e3 in QMetaObject::activate (sender=sender@entry=0x55bbd27a19e0, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdc43fccf0) at kernel/qobject.cpp:3771 #15 0x7f03801eed57 in QMetaObject::activate (sender=sender@entry=0x55bbd27a19e0, m=m@entry=0x7f03817d1840 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdc43fccf0) at kernel/qobject.cpp:3633 #16 0x7f03810ff682 in QAction::triggered (this=this@entry=0x55bbd27a19e0, _t1=) at .moc/moc_qaction.cpp:376 #17 0x7f0381101cbc in QAction::activate (this=0x55bbd27a19
[okular] [Bug 395765] Crash when closing okular
https://bugs.kde.org/show_bug.cgi?id=395765 Erik Quaeghebeur changed: What|Removed |Added CC||k...@equaeghe.nospammail.net --- Comment #11 from Erik Quaeghebeur --- I'm constantly being hit by this in 1.5.3 (18.08.3). In what version is this fixed? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #15 from Erik Quaeghebeur --- I need further assistance in testing the proposed fontconfig-related modifications. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 233806] I can't verify digital signature(s) in PDF files
https://bugs.kde.org/show_bug.cgi?id=233806 Erik Quaeghebeur changed: What|Removed |Added CC||k...@equaeghe.nospammail.net -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 --- Comment #13 from Erik Quaeghebeur --- (In reply to Christoph Feck from comment #12) > […], but did you check if file > '/usr/share/fonts/liberation-fonts/LiberationSans-Regular.ttf' exists? Yes, and it does exist. Also, I think that font is not the problem, as per my comment 11. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 --- Comment #11 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #6) > You probably have a wrong Helvetica font substitution configured on your > system, […] When I open the file in inkscape, it appears that the text that is missing for me uses Arial and so the embedded font should be used, I would think. (In reply to Albert Astals Cid from comment #8) > it works for with with Nimbus provided by gsfonts, give it a try and make > sure you tweak your fontconfig I can't seem to get my fontconfig to choose Nimbus, even though it is installed. But perhaps that is another issue. I did manage to get TeX Gyre and Linux Libertine instead of Liberation Sans as replacements for Helvetica, but neither gave a difference, possibly because the Helvetica substitution is not the problem here. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 394917] Confusing message about ‘internal storage’
https://bugs.kde.org/show_bug.cgi?id=394917 --- Comment #2 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #1) > Your message seems nice, the last sentence can't be "pdf file" since it > needs to be generic, so it'll be just "file". Certainly. > And i think "this kind of storage" is a bit better than "this type of > storage". What do you think? No preference, so use what you think fits best. (Thanks for picking this up.) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 394917] New: Confusing message about ‘internal storage’
https://bugs.kde.org/show_bug.cgi?id=394917 Bug ID: 394917 Summary: Confusing message about ‘internal storage’ Product: okular Version: 1.3.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- I opened a pdf file with a form that I had filled with an earlier version of okular and got the message "This document contains annotations or form data that were saved internally by a previous Okular version. Internal storage is no longer supported. Please save to a file in order to move them if you want to continue to edit the document." It is not clear at all what is meant by ‘internal storage’. I first thought it was ‘internal to the pdf’. It is only after searching on-line that it referred to ‘internal to okular configuration files’ *external* to the file. (I didn't even know okular did that. It explains a lot of trouble I had with filling in forms with okular and not being able to get rid of ‘zombie data’.) The current message is totally confusing and should be replaced with something that is not confusing and also indicates where the data is stored ‘internally’. I suggest something like the following: "For this document, annotations or form data were saved by a previous Okular version to the local file "/home/user/.local/share/okular/file.pdf.xml". This type of storage is no longer supported. Please save to a file in order to preserve the annotations and form data; these will be saved inside the pdf file itself." -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 --- Comment #10 from Erik Quaeghebeur --- (In reply to Christoph Feck from comment #9) > Erik, did comment #8 help to resolve the issue? I have not managed to try it out. My initial attempts stranded because I do not know how to get Nimbus to be selected for substitution. I inquired on the Gentoo forums, but did not get a response that helped me understand what I needed to do. Currently, I do not have the time to try further. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 --- Comment #7 from Erik Quaeghebeur --- Created attachment 112245 --> https://bugs.kde.org/attachment.cgi?id=112245&action=edit screenshot of file fonts in viewer -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 --- Comment #5 from Erik Quaeghebeur --- Created attachment 112229 --> https://bugs.kde.org/attachment.cgi?id=112229&action=edit screenshot of file in viewer with (invisible) text selected -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 --- Comment #4 from Erik Quaeghebeur --- Created attachment 112228 --> https://bugs.kde.org/attachment.cgi?id=112228&action=edit screenshot of file in viewer -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 --- Comment #2 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #1) > Does pdftoppm have the same behaviour of not showing the text? No, the ppm file do show the text. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393459] New: text in file not shown in viewer
https://bugs.kde.org/show_bug.cgi?id=393459 Bug ID: 393459 Summary: text in file not shown in viewer Product: okular Version: 1.3.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- I have a pdf whose text is not shown in the viewer. However, when selecting text, the text can be selected. Also, in the print-preview the text is visible. When viewing the file with mupdf, the text is rendered. It may be a bug in Okular, poppler, or a problem with the file. I cannot share the pdf here, but can send it to a developer upon request. -- You are receiving this mail because: You are the assignee for the bug.
[Okular-devel] [okular] [Bug 365654] New: Search for character or string in a specific font or style
https://bugs.kde.org/show_bug.cgi?id=365654 Bug ID: 365654 Summary: Search for character or string in a specific font or style Product: okular Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: kdeb...@equaeghe.nospammail.net (I mainly have okular as a pdf viewer in mind.) It would be useful to be able to search a text viewed for a specific character or string in a specific font or font style. An example of what I would like to do is find an italic ‘x’, not just any ‘x’. In my example the difference is just style, upright vs. slanted/italic, but I am certainly also interested in the capability of having the search procedure being able to take into account differences in font. This feature would be especially useful when trying to search a pdf for the occurrence of a mathematical variable, which is usually denoted in a different style or font. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 198427] Hyperlink hopping is inaccurate when "trim margins" is on
https://bugs.kde.org/show_bug.cgi?id=198427 Erik Quaeghebeur changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 240549] New: Okular crashes when opening pdf file
https://bugs.kde.org/show_bug.cgi?id=240549 Summary: Okular crashes when opening pdf file Product: okular Version: 0.10.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: kdeb...@equaeghe.nospammail.net Application: okular (0.10.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic x86_64 Distribution: Ubuntu 10.04 LTS -- Information about the crash: http://www.ctan.org/tex-archive/graphics/pgf/contrib/pgfplots/doc/latex/pgfplots/pgfplots.pdf crashes okular consistently The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #5 Object::free (this=0x1) at Object.cc:124 #6 0x7f3c5debd1b4 in ~ObjectStream (this=0x10197c0, __in_chrg=) at XRef.cc:211 #7 0x7f3c5debe98a in XRef::fetch (this=0x13793d0, num=2, gen=0, obj=0x7fffe22ae120) at XRef.cc:1001 #8 0x7f3c5de48cd1 in Catalog::getJS (this=0x1424e90, i=) at Catalog.cc:439 #9 0x7f3c5e1c2612 in Poppler::Document::scripts (this=) at poppler-document.cc:570 #10 0x7f3c5e42fc82 in PDFGenerator::metaData (this=0x1422c10, key=, option=...) at ../../../../okular/generators/poppler/generator_pdf.cpp:1001 #11 0x7f3c60cb5d1d in Okular::Document::openDocument (this=0x113e490, docFile=, url=, _mime=) at ../../okular/core/document.cpp:1718 #12 0x7f3c60f7086c in Okular::Part::openFile (this=0x1077f10) at ../../okular/part.cpp:930 #13 0x7f3c6c74d117 in KParts::ReadOnlyPart::openUrl (this=0x1077f10, url=) at ../../kparts/part.cpp:557 #14 0x7f3c60f6504a in Okular::Part::openUrl (this=0x1077f10, _url=) at ../../okular/part.cpp:1049 #15 0x00409a8a in Shell::openUrl (this=0x1114d60, url=...) at ../../../okular/shell/shell.cpp:130 #16 0x0040a3ac in Shell::qt_metacall (this=0x1114d60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffe22af0a0) at ./shell.moc:94 #17 0x7f3c6b1f9e3f in QMetaObject::activate (sender=0x13ff8e0, m=, local_signal_index=, argv=0x7fffe22ae120) at kernel/qobject.cpp:3293 #18 0x7f3c6b20165f in QSingleShotTimer::timerEvent (this=0x13ff8e0) at kernel/qtimer.cpp:308 #19 0x7f3c6b1f6a63 in QObject::event (this=0x13ff8e0, e=0x7fffe22af800) at kernel/qobject.cpp:1212 #20 0x7f3c6a5a022c in QApplicationPrivate::notify_helper (this=0xfc49b0, receiver=0x13ff8e0, e=0x7fffe22af800) at kernel/qapplication.cpp:4300 #21 0x7f3c6a5a66fb in QApplication::notify (this=0x7fffe22afb50, receiver=0x13ff8e0, e=0x7fffe22af800) at kernel/qapplication.cpp:4183 #22 0x7f3c6be48526 in KApplication::notify (this=0x7fffe22afb50, receiver=0x13ff8e0, event=0x7fffe22af800) at ../../kdeui/kernel/kapplication.cpp:302 #23 0x7f3c6b1e706c in QCoreApplication::notifyInternal (this=0x7fffe22afb50, receiver=0x13ff8e0, event=0x7fffe22af800) at kernel/qcoreapplication.cpp:704 #24 0x7f3c6b213d42 in QCoreApplication::sendEvent (this=0xfc8680) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #25 QTimerInfoList::activateTimers (this=0xfc8680) at kernel/qeventdispatcher_unix.cpp:603 #26 0x7f3c6b210824 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:184 #27 0x7f3c665118c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #28 0x7f3c66515748 in ?? () from /lib/libglib-2.0.so.0 #29 0x7f3c665158fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #30 0x7f3c6b210513 in QEventDispatcherGlib::processEvents (this=0xfacfb0, flags=) at kernel/qeventdispatcher_glib.cpp:412 #31 0x7f3c6a65046e in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x7f3c6b1e5992 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #33 0x7f3c6b1e5d6c in QEventLoop::exec (this=0x7fffe22afaa0, flags=) at kernel/qeventloop.cpp:201 #34 0x7f3c6b1e9aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #35 0x0040889c in main (argc=, argv=) at ../../../okular/shell/main.cpp:82 This bug may be a duplicate of or related to bug 235805. Possible duplicates by query: bug 240125, bug 235805. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
