Bug 375964 - Okular crashed when I hit Escape
Summary: Okular crashed when I hit Escape
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2017-02-03 17:14 UTC by bastien.maubert
Modified: 2017-02-06 21:51 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
LICS_2017_paper_36.pdf (deleted)
2017-02-03 19:37 UTC, bastien.maubert
Details
valgrind-output.txt (1.72 MB, text/plain)
2017-02-04 14:01 UTC, bastien.maubert
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bastien.maubert 2017-02-03 17:14:08 UTC
Application: okular (0.24.2)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-59-generic x86_64
Distribution: Linux Mint 18.1 Serena

-- Information about the crash:
- What I was doing when the application crashed:
I was reading and annotating a pdf. I hit escape (or did I hit the mute key instead?) and it crashed. It told me Segfault, and the terminal from which I opened Okular shows me :

bastien@Arya ~/Documents/Boulot/bastien00sophie/Reviews/Confs/LICS/LICS17 $ KCrash: Application 'okular' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/bastien/.kde/socket-Arya/kdeinit4__0
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f01a8aa0a64 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f01a94b0fbc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8  0x00007f01a94b9263 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007f01aa2166aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#10 0x00007f01a8aa090d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007f01a94e7ff0 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007f01a94b92ee in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007f01aa2166aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#14 0x00007f01a8aa090d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#15 0x00007f01a8aa43c6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x00007f01a8ad113e in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x00007f01a511b197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f01a511b3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f01a511b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f01a8ad12ae in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x00007f01a955e616 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#22 0x00007f01a8a9f18f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x00007f01a8a9f4f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x00007f01a8aa54b9 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#25 0x0000000000409858 in ?? ()
#26 0x00007f01a7f68830 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#27 0x000000000040b489 in _start ()

Possible duplicates by query: bug 371981, bug 368398, bug 365949, bug 365152, bug 363687.

Reported using DrKonqi
Comment 1 bastien.maubert 2017-02-03 17:42:09 UTC
Now I know more precisely what causes the crash : every time I close a pop-up note by hitting escape after I have finished writing it, it crashes. It does not crash if I close with a click instead.
Comment 2 Oliver Sander 2017-02-03 19:15:12 UTC
I cannot reproducethis.  Can you post the file?
Comment 3 bastien.maubert 2017-02-03 19:28:27 UTC
Unfortunately it's a conference paper I'm reviewing, so I think I'm not really supposed to circulate it... But I see you're in a different field so probably it's not that bad :-) You don't know people that attend the LICS conference do you?
Comment 4 Oliver Sander 2017-02-03 19:32:07 UTC
I don't even know what LICS is.  But be aware that I am not a skilled okular hacker.  Therefore most likely I won't be able to do more than confirm (or not) the bug.
Comment 5 bastien.maubert 2017-02-03 19:37:47 UTC
Created attachment 103796 [details]
LICS_2017_paper_36.pdf

Here it is.

Best,
Bastien

On 03/02/2017 20:32, Oliver Sander wrote:
> https://bugs.kde.org/show_bug.cgi?id=375964
>
> --- Comment #4 from Oliver Sander <oliver.sander@tu-dresden.de> ---
> I don't even know what LICS is.  But be aware that I am not a skilled okular
> hacker.  Therefore most likely I won't be able to do more than confirm (or not)
> the bug.
>
Comment 6 Nicolás Alvarez 2017-02-03 19:42:47 UTC
The content of attachment 103796 [details] has been deleted for the following reason:

PDF that shouldn't be published
Comment 7 Luigi Toscano 2017-02-03 19:44:11 UTC
Please use the email (possibly encrypted), not a public bugtracker for confidential messages.
Comment 8 Oliver Sander 2017-02-03 19:44:47 UTC
Thanks, I didn't even know you can delete attachments.  Bastien, this is a public bugtracker.  Anything you post here is visible to everyone.
Comment 9 Oliver Sander 2017-02-03 19:46:10 UTC
In any case, I got the file, and pressing escape to close an open pop-up annotation didn't make my Okular crash.  Neither the one from Debian testing nor the self-compiled git master.

I didn't see those warnings about 'linearGradient' either.
Comment 10 bastien.maubert 2017-02-03 19:49:18 UTC
Yep sorry, since Thunderbird showed me your mail address as sender I 
thought that by hitting reply it would be sent just to you, and I didn't 
check.
Thanks for removing the pdf.

On 03/02/2017 20:46, Oliver Sander wrote:
> https://bugs.kde.org/show_bug.cgi?id=375964
>
> --- Comment #9 from Oliver Sander <oliver.sander@tu-dresden.de> ---
> In any case, I got the file, and pressing escape to close an open pop-up
> annotation didn't make my Okular crash.  Neither the one from Debian testing
> nor the self-compiled git master.
>
> I didn't see those warnings about 'linearGradient' either.
>
Comment 11 Albert Astals Cid 2017-02-03 23:11:53 UTC
linearGradient4582 warnings are icons/SVG parsing warnings, totally not relevant.
Comment 12 Albert Astals Cid 2017-02-03 23:16:25 UTC
Sadly the backtrace is close to worthless.

Can you reproduce the crash every single time?

If you can reproduce the crash every single time, can you run okular with valgrind (give it some time, it'll be slow), can you paste the trace here?
Comment 13 bastien.maubert 2017-02-04 14:01:51 UTC
Created attachment 103821 [details]
valgrind-output.txt

So yes, the bug occurs every time. Well, strangely, it's almost every 
time, as yesterday it happened once that I closed the pop-up with escape 
without getting the error. But since then it happened every time I tried.

So I ran valgrind, here is the log. I just oppened the file with okular, 
pressed F6 and 1 to select the pop-up tool, clicked somewhere, pressed 
enter to close the window telling me that the changes would not be saved 
automatically, and then pressed escape. Strangely it seems that when 
running with valgrind, okular does not collapse. I don't know if 
valgrind can catch errors or something?

Best,
Bastien

On 04/02/2017 00:16, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=375964
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Resolution|---                         |WAITINGFORINFO
>               Status|UNCONFIRMED                 |NEEDSINFO
>
> --- Comment #12 from Albert Astals Cid <aacid@kde.org> ---
> Sadly the backtrace is close to worthless.
>
> Can you reproduce the crash every single time?
>
> If you can reproduce the crash every single time, can you run okular with
> valgrind (give it some time, it'll be slow), can you paste the trace here?
>
Comment 14 Albert Astals Cid 2017-02-04 16:23:42 UTC
Can you please, uninstall whatever package is providing libqspiaccessiblebridge.so (probably named qt-at-spi) (unless you really need the accessibility features) the valgrind trace points to it, and it's most probably buggy.

If you uninstall it can you reproduce the crash?
Comment 15 bastien.maubert 2017-02-06 14:09:33 UTC
Indeed, I purged qt-at-spi and now it seems to work. Thanks! I don't 
know what Qt accessibility does exactly, it seems it is especially for 
users with sight / hearing problems. I don't know what it does by 
default, but for the moment everything seems to work normally.

Bastien

On 04/02/2017 17:23, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=375964
>
> --- Comment #14 from Albert Astals Cid <aacid@kde.org> ---
> Can you please, uninstall whatever package is providing
> libqspiaccessiblebridge.so (probably named qt-at-spi) (unless you really need
> the accessibility features) the valgrind trace points to it, and it's most
> probably buggy.
>
> If you uninstall it can you reproduce the crash?
>
Comment 16 Albert Astals Cid 2017-02-06 21:51:02 UTC
qt-at-spi is something we can't control and is not maintainer anymore, so nothing we can do to fix it.