Bug 218281 - Crash on opening okular
Summary: Crash on opening okular
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-11 15:07 UTC by Andreas Neustifter
Modified: 2010-07-11 17:35 UTC (History)
1 user (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 Andreas Neustifter 2009-12-11 15:07:40 UTC
Application that crashed: okular
Version of the application: 0.9.80
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
double click on nautilus after telling it to always use okular crashed

 -- Backtrace:
Application: Okular (okular), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fd132a84820 in KServiceType::serviceOffersOffset() const () from /usr/lib/libkdecore.so.5
#6  0x00007fd132a6b6f2 in KMimeTypeTrader::query(QString const&, QString const&, QString const&) const () from /usr/lib/libkdecore.so.5
#7  0x00007fd1237fbc24 in Okular::Document::openDocument (this=0x16e1ed0, docFile=..., url=<value optimized out>, _mime=<value optimized out>)
    at /home/astifter/Development/kdegraphics/okular/core/document.cpp:1598
#8  0x00007fd123ab2d7c in Okular::Part::openFile (this=0x16c18d0) at /home/astifter/Development/kdegraphics/okular/part.cpp:924
#9  0x00007fd13408e0c7 in KParts::ReadOnlyPart::openUrl(KUrl const&) () from /usr/lib/libkparts.so.4
#10 0x00007fd123aa6eaa in Okular::Part::openUrl (this=0x16c18d0, _url=<value optimized out>) at /home/astifter/Development/kdegraphics/okular/part.cpp:1043
#11 0x0000000000409b0a in Shell::openUrl (this=0x1670320, url=...) at /home/astifter/Development/kdegraphics/okular/shell/shell.cpp:130
#12 0x000000000040a42c in Shell::qt_metacall (this=0x1670320, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fffa7fa2ea0) at /home/astifter/Development/kdegraphics/build/okular/shell/shell.moc:88
#13 0x00007fd1323ebddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#14 0x00007fd1323f0e1f in ?? () from /usr/lib/libQtCore.so.4
#15 0x00007fd1323e5d83 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x00007fd13187eefc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x00007fd1318861ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x00007fd133242ab6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x00007fd1323d6c2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x00007fd132401862 in ?? () from /usr/lib/libQtCore.so.4
#21 0x00007fd1323ff25d in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007fd12e239bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x00007fd12e23d598 in ?? () from /lib/libglib-2.0.so.0
#24 0x00007fd12e23d6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0x00007fd1323ff1a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0x00007fd1319134be in ?? () from /usr/lib/libQtGui.so.4
#27 0x00007fd1323d5532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x00007fd1323d5904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x00007fd1323d7ab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#30 0x000000000040899c in main (argc=<value optimized out>, argv=<value optimized out>) at /home/astifter/Development/kdegraphics/okular/shell/main.cpp:81

This bug may be a duplicate of or related to bug 214747

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-11 16:23:14 UTC
- Does running "kbuildsycoca4 --noincremental" prior to launching Okular fixes the issue ? Thanks
Comment 2 Andreas Neustifter 2009-12-11 16:31:42 UTC
(In reply to comment #1)
> - Does running "kbuildsycoca4 --noincremental" prior to launching Okular fixes
> the issue ? Thanks

No, sorry:
> astifter@astifter:/tmp$ okular empirical-fortran.pdf 
> KCrash: Application 'okular' crashing...
> sock_file=/home/astifter/.kde/socket-astifter/kdeinit4__0
> 
> [1]+  Stopped                 okular empirical-fortran.pdf
> astifter@astifter:/tmp$ kbuildsycoca4 --noincremental
> kbuildsycoca4 running...
> [1]+  Exit 253                okular empirical-fortran.pdf
> astifter@astifter:/tmp$ okular empirical-fortran.pdf 
> KCrash: Application 'okular' crashing...
> sock_file=/home/astifter/.kde/socket-astifter/kdeinit4__0
> 
> [1]+  Stopped                 okular empirical-fortran.pdf
> astifter@astifter:/tmp$ 
> [1]+  Exit 253                okular empirical-fortran.pdf
> astifter@astifter:/tmp$
Comment 3 Albert Astals Cid 2009-12-11 21:38:38 UTC
same backtrace?
Comment 4 Albert Astals Cid 2010-07-11 17:35:42 UTC
No asnwer from the reporter in 6 months, thus closing the bug, if you still have the problem please reopen the bug.