Application that crashed: konqueror Version of the application: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) "release 146" KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) "release 146" Qt Version: 4.5.2 Operating System: Linux 2.6.25.20-0.4-default x86_64 What I was doing when the application crashed: When loading http://radsport-news.com the page is not completely loading. The header and the right side is missing. This happens everytime. Following any link there to any articel has konqueror crashing, every time. This did not happen before, with any kde4 release including betas and RC1 and RC2, but started right after upgrading to KDE4 RC3 from the repositories for OpenSUSE 11.0. Other websites, such as kde bugzilla load fine. -- Backtrace: Application: Konqueror (kdeinit4), signal: Segmentation fault [Current thread is 0 (LWP 12734)] Thread 2 (Thread 0x4107e950 (LWP 12756)): #0 0x00007f8633acc05d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f8633d3cec7 in QWaitCondition::wait () from /usr/lib64/libQtCore.so.4 #2 0x00007f8633d32b1a in ?? () from /usr/lib64/libQtCore.so.4 #3 0x00007f8633d3bf35 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f8633ac8040 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f863062208d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f86342e9700 (LWP 12734)): [KCrash Handler] #5 0x00007f8632cedbe0 in KIO::SimpleJob::url () from /usr/lib64/libkio.so.5 #6 0x00007f8633439937 in KParts::BrowserRun::slotBrowserMimetype () from /usr/lib64/libkparts.so.4 #7 0x00007f863343adfd in KParts::BrowserRun::qt_metacall () from /usr/lib64/libkparts.so.4 #8 0x00007f8633e3b2f2 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #9 0x00007f8632cee1b7 in KIO::TransferJob::mimetype () from /usr/lib64/libkio.so.5 #10 0x00007f8632cf3c41 in KIO::TransferJob::qt_metacall () from /usr/lib64/libkio.so.5 #11 0x00007f8633e3b2f2 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #12 0x00007f8632db2a55 in KIO::SlaveInterface::mimeType () from /usr/lib64/libkio.so.5 #13 0x00007f8632db6060 in KIO::SlaveInterface::dispatch () from /usr/lib64/libkio.so.5 #14 0x00007f8632db30c2 in KIO::SlaveInterface::dispatch () from /usr/lib64/libkio.so.5 #15 0x00007f8632da5c13 in KIO::Slave::gotInput () from /usr/lib64/libkio.so.5 #16 0x00007f8632da7e78 in KIO::Slave::qt_metacall () from /usr/lib64/libkio.so.5 #17 0x00007f8633e3b2f2 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #18 0x00007f8632cc19f1 in ?? () from /usr/lib64/libkio.so.5 #19 0x00007f8632cc1e4a in KIO::Connection::qt_metacall () from /usr/lib64/libkio.so.5 #20 0x00007f8633e364d8 in QObject::event () from /usr/lib64/libQtCore.so.4 #21 0x00007f86311bfa9d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4 #22 0x00007f86311c7d1a in QApplication::notify () from /usr/lib64/libQtGui.so.4 #23 0x00007f86322ac91b in KApplication::notify () from /usr/lib64/libkdeui.so.5 #24 0x00007f8633e264fc in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4 #25 0x00007f8633e2718a in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/libQtCore.so.4 #26 0x00007f8633e4fd53 in ?? () from /usr/lib64/libQtCore.so.4 #27 0x00007f862fca193a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f862fca5040 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f862fca51dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f8633e4f9df in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4 #31 0x00007f863125741f in ?? () from /usr/lib64/libQtGui.so.4 #32 0x00007f8633e24d72 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #33 0x00007f8633e25144 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #34 0x00007f8633e27454 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #35 0x00007f86279cfee9 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so #36 0x00000000004073dd in _start () Reported using DrKonqi
Thanks for the bug report! This is a regression in KDE 4.3 RC 3. I think I've identified the commit that was responsible, so I hope it can be fixed before 4.3.0 is released. *** This bug has been marked as a duplicate of bug 201315 ***