Bug 338825 - crash when click on pdf file from dolphin
Summary: crash when click on pdf file from dolphin
Status: RESOLVED DUPLICATE of bug 338264
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-05 13:11 UTC by Maxi Schimmel
Modified: 2014-09-06 16:04 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxi Schimmel 2014-09-05 13:11:36 UTC
When I wish to open a PDF file from dolphin5 clickin on it or right clickin and selecting "open with Okular", the only result I get is DrKonqui (trace below).
But if I opens empty okular then drag and drop same file its open normally.

Application: okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
gobject.py: gdb was not built with custom backtrace support, disabling.
[Current thread is 1 (Thread 0x7f62748e0880 (LWP 1120))]

Thread 2 (Thread 0x7f6261978700 (LWP 1121)):
#0  0x00007f6270dd3b3d in poll () from /lib64/libc.so.6
#1  0x00007f626f4490e2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f626f44a77f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f62636a3de9 in QXcbEventReader::run (this=0x1912d00) at qxcbconnection.cpp:1043
#4  0x00007f627144f06f in QThreadPrivate::start (arg=0x1912d00) at thread/qthread_unix.cpp:345
#5  0x00007f626c3500db in start_thread () from /lib64/libpthread.so.0
#6  0x00007f6270ddc90d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f62748e0880 (LWP 1120)):
[KCrash Handler]
#5  0x00007f62608c5640 in ?? ()
#6  0x00007f627143a103 in QInternal::activateCallbacks (cb=cb@entry=QInternal::EventNotifyCallback, parameters=parameters@entry=0x7ffff0099810) at global/qglobal.cpp:2914
#7  0x00007f627162d282 in QCoreApplication::notifyInternal (this=0x7ffff0099ca0, receiver=0x1943ec0, event=event@entry=0x7ffff0099880) at kernel/qcoreapplication.cpp:924
#8  0x00007f627166347e in sendEvent (event=0x7ffff0099880, receiver=<optimized out>) at kernel/qcoreapplication.h:237
#9  QObjectPrivate::setParent_helper (this=this@entry=0x18f7bb0, o=o@entry=0x0) at kernel/qobject.cpp:1961
#10 0x00007f6271663a03 in QObject::~QObject (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:1033
#11 0x00007f6271668e19 in QSocketNotifier::~QSocketNotifier (this=0x1945720, __in_chrg=<optimized out>) at kernel/qsocketnotifier.cpp:203
#12 0x00007f62729d6897 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x00007f626bf0f253 in ?? () from /lib64/libdbus-1.so.3
#14 0x00007f626bf0d99e in ?? () from /lib64/libdbus-1.so.3
#15 0x00007f626bf0da19 in ?? () from /lib64/libdbus-1.so.3
#16 0x00007f626bf0cea7 in ?? () from /lib64/libdbus-1.so.3
#17 0x00007f626bef8d82 in ?? () from /lib64/libdbus-1.so.3
#18 0x00007f62729d8e0a in ?? () from /usr/lib64/libQt5DBus.so.5
#19 0x00007f62729cbe72 in ?? () from /usr/lib64/libQt5DBus.so.5
#20 0x00007f62729cbef9 in ?? () from /usr/lib64/libQt5DBus.so.5
#21 0x00007f6270d2d3d9 in __run_exit_handlers () from /lib64/libc.so.6
#22 0x00007f6270d2d425 in exit () from /lib64/libc.so.6
#23 0x00007f6271462d66 in QCommandLineParser::process (this=this@entry=0x7ffff0099c20, arguments=...) at tools/qcommandlineparser.cpp:495
#24 0x00007f6271462df5 in QCommandLineParser::process (this=0x7ffff0099c20, app=...) at tools/qcommandlineparser.cpp:516
#25 0x000000000040e5ba in main ()


Reproducible: Always

Steps to Reproduce:
1. open dolphin and look for a PDF file
2. click over it or right click and select "open with okular"
3. done.
Comment 1 Luigi Toscano 2014-09-05 13:18:11 UTC
Is it the Qt5 version of Okular? Both Qt5 version of dolphin and even more okular are under heavy development. Please consider the packages are highly experimental (Plasma 5 has been released, those applications have not).
Comment 2 Christoph Feck 2014-09-05 13:48:08 UTC
Yes, Qt5 version. Funny that QCommandLineParser:process() calls exit(), might be a Qt bug.
Comment 3 Christoph Feck 2014-09-05 13:52:16 UTC
From qcommandlineparser.cpp:

"When invoking one of these options, or when an error happens (for instance an unknown option was passed), the current process will then stop, using the exit() function."

Nice way of error handling.
Comment 4 Christoph Feck 2014-09-05 13:56:05 UTC
Probably should use QCP::parse() instead of QCP::process() instead. It seems the behavior is intended.
Comment 5 Christoph Feck 2014-09-05 14:00:43 UTC
The other issue here is that a global QtDBus object is created before QCP is used.
Comment 6 Maxi Schimmel 2014-09-05 14:14:55 UTC
Yes, is the qt5 version. I'm using it for testing and every day use (I'm Rambo :))
Comment 7 Albert Astals Cid 2014-09-06 16:04:48 UTC

*** This bug has been marked as a duplicate of bug 338264 ***