Bug 372776 - Crash when opening link in new window
Summary: Crash when opening link in new window
Status: RESOLVED DUPLICATE of bug 379771
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-22 07:25 UTC by Antonio Rojas
Modified: 2017-06-02 19:06 UTC (History)
0 users

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 Antonio Rojas 2016-11-22 07:25:10 UTC
Using 16.12 beta. When opening a link in a new window, instead of opening directly I get a dialog asking how to open the HTML file. If I cancel the dialog, konqueror crashes

(gdb) bt
#0  0x00007ffff7b041a8 in QExplicitlySharedDataPointer<KService>::~QExplicitlySharedDataPointer (this=<optimized out>, __in_chrg=<optimized out>)
    at /usr/include/qt/QtCore/qshareddata.h:165
#1  KonqRun::foundMimeType (this=0x1e86960, _type=...) at /build/konqueror/src/konqueror-16.11.80/src/konqrun.cpp:106
#2  0x00007ffff6409722 in KRun::mimeTypeDetermined(QString const&) () from /usr/lib/libKF5KIOWidgets.so.5
#3  0x00007ffff69b98be in KParts::BrowserRun::slotBrowserMimetype(KIO::Job*, QString const&) () from /usr/lib/libKF5Parts.so.5
#4  0x00007ffff22719ce in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#5  0x00007ffff608f507 in KIO::TransferJob::mimetype(KIO::Job*, QString const&) () from /usr/lib/libKF5KIOCore.so.5
#6  0x00007ffff608f5ef in KIO::TransferJob::slotMimetype(QString const&) () from /usr/lib/libKF5KIOCore.so.5
#7  0x00007ffff6091a6d in ?? () from /usr/lib/libKF5KIOCore.so.5
#8  0x00007ffff2271659 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#9  0x00007ffff605caa5 in KIO::SlaveInterface::mimeType(QString const&) () from /usr/lib/libKF5KIOCore.so.5
#10 0x00007ffff605e04b in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5
#11 0x00007ffff605cbb7 in KIO::SlaveInterface::dispatch() () from /usr/lib/libKF5KIOCore.so.5
#12 0x00007ffff6061f21 in KIO::Slave::gotInput() () from /usr/lib/libKF5KIOCore.so.5
#13 0x00007ffff60fe325 in ?? () from /usr/lib/libKF5KIOCore.so.5
#14 0x00007ffff2271659 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#15 0x00007ffff5ff4b90 in ?? () from /usr/lib/libKF5KIOCore.so.5
#16 0x00007ffff22724b9 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#17 0x00007ffff33b1e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#18 0x00007ffff33b9581 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#19 0x00007ffff2245de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#20 0x00007ffff224856d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#21 0x00007ffff229a303 in ?? () from /usr/lib/libQt5Core.so.5
#22 0x00007fffeb304587 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007fffeb3047f0 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007fffeb30489c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007ffff229a70f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#26 0x00007ffff224423a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#27 0x00007ffff224c73c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#28 0x00007ffff7b884bd in kdemain (argc=<optimized out>, argv=<optimized out>) at /build/konqueror/src/konqueror-16.11.80/src/konqmain.cpp:232
#29 0x00007ffff7740291 in __libc_start_main () from /usr/lib/libc.so.6
#30 0x000000000040068a in _start ()
Comment 1 Christoph Feck 2017-06-02 19:06:31 UTC
Bug 379771 has a better backtrace.

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