Bug 202573 - Crash after selecting link to .tex doc when choose application dialog displayed
Summary: Crash after selecting link to .tex doc when choose application dialog displayed
Status: RESOLVED DUPLICATE of bug 201564
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-05 07:01 UTC by David Rankin
Modified: 2009-12-12 23:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Rankin 2009-08-05 07:01:46 UTC
Application that crashed: okular
Version of the application: 0.9
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3))
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH x86_64

What I was doing when the application crashed:
Ocular crashed after selecting a link to a .tex document within the pdf being viewed. After selecting the link, the normal kde "choose application" dialog opened so I could choose the application to open the link with. After choosing firefox, the entire app crashed.

 -- Backtrace:
Application: Okular (okular), signal: Segmentation fault
[Current thread is 0 (LWP 5833)]

Thread 2 (Thread 0x7f0211518910 (LWP 5875)):
#0  0x00007f0222ea205d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f02245682b2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#2  0x00007f022455e412 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007f0224567285 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007f0222e9d57a in start_thread () from /lib/libpthread.so.0
#5  0x00007f02233c316d in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0225f3d750 (LWP 5833)):
[KCrash Handler]
#5  0x00007f0225719434 in KIO::Connection::suspended () from /usr/lib/libkio.so.5
#6  0x00007f022580e01e in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#7  0x00007f022580ae13 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#8  0x00007f02257fdc3d in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#9  0x00007f02257ffd5c in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#10 0x00007f0224661e0c in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0x00007f022571b487 in KIO::ConnectionPrivate::dequeue () from /usr/lib/libkio.so.5
#12 0x00007f022571b5ad in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#13 0x00007f022465c129 in QObject::event () from /usr/lib/libQtCore.so.4
#14 0x00007f0223af8e2c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#15 0x00007f0223b000fe in QApplication::notify () from /usr/lib/libQtGui.so.4
#16 0x00007f022525b036 in KApplication::notify () from /usr/lib/libkdeui.so.5
#17 0x00007f022464cd0c in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#18 0x00007f022464d8ea in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#19 0x00007f0224675563 in ?? () from /usr/lib/libQtCore.so.4
#20 0x00007f0220142dbe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00007f0220146568 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#22 0x00007f0220146690 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x00007f02246751d6 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#24 0x00007f0223b8bdde in ?? () from /usr/lib/libQtGui.so.4
#25 0x00007f022464b612 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#26 0x00007f022464b9e4 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#27 0x00007f022464db99 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#28 0x00000000004087cc in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-08-05 15:15:38 UTC
The backtrace at bug 201564 looks related. It could be the same bug.
Can you reproduce the crash at will using the steps you described ? Thanks!
Comment 2 Dario Andres 2009-12-12 23:10:16 UTC
Merging with bug 201564. Thanks

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