Konqueror crash with back button

Bug #289853 reported by Kieran Hogg
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE Base
Fix Released
Unknown
kde4libs (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: kdebase

I can crash konqueror every time by doing the following:

1. Login to facebook.com
2. Click on the first photo of a photo album (probably works with any)
3. When the page is loaded, press back
4. Konqueror crashes

Below is the stacktrace, I'll wait for someone to confirm this before moving it upstream.

Application: Konqueror (konqueror), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb60dc8d0 (LWP 16950)]
[New Thread 0xb1b23b90 (LWP 17626)]
[KCrash handler]
#6 0xb74492ab in QString::operator== () from /usr/lib/libQtCore.so.4
#7 0xb41d6980 in KHTMLPart::restoreState (this=0xa872190, stream=@0xbfbd681c)
    at /usr/include/qt4/QtCore/qstring.h:372
#8 0xb4202a7e in KHTMLPartBrowserExtension::restoreState (this=0xca56e58,
    stream=@0xbfbd681c)
    at /build/buildd/kde4libs-4.1.2/khtml/khtml_ext.cpp:104
#9 0xb7ffe216 in KonqView::restoreHistory (this=0xcae1650)
    at /build/buildd/kdebase-4.1.2/apps/konqueror/src/konqview.cpp:859
#10 0xb8055240 in KonqMainWindow::slotGoHistoryDelayed (this=0x98b58f0)
    at /build/buildd/kdebase-4.1.2/apps/konqueror/src/konqmainwindow.cpp:2820
#11 0xb805fc97 in KonqMainWindow::qt_metacall (this=0x98b58f0,
    _c=QMetaObject::InvokeMetaMethod, _id=104, _a=0xbfbd69c8)
    at /build/buildd/kdebase-4.1.2/obj-i486-linux-gnu/apps/konqueror/src/konqmainwindow.moc:434
#12 0xb750ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb750d7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb7512db7 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb7512edc in ?? () from /usr/lib/libQtCore.so.4
#16 0xb750753f in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb69fb8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0xb6a0376e in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb79c772d in KApplication::notify (this=0xbfbd72a4, receiver=0xd69b748,
    event=0xbfbd6e5c)
    at /build/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311
#20 0xb74f7e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0xb7525d81 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb7522520 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb646e6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb6471da3 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb6471f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb7522478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb6a95ee5 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb74f652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb74f66ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb74f8da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb69fb767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0xb808b95d in kdemain (argc=2, argv=0xbfbd75c4)
    at /build/buildd/kdebase-4.1.2/apps/konqueror/src/konqmain.cpp:227
#33 0x080485b2 in main (argc=)
    at /build/buildd/kdebase-4.1.2/obj-i486-linux-gnu/apps/konqueror/src/konqueror_dummy.cpp:3
#0 0xb80d7430 in __kernel_vsyscall ()

Revision history for this message
Kieran Hogg (xerosis) wrote :
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Was already reported upstream.

Changed in kdebase:
importance: Undecided → Low
status: New → Triaged
Changed in kdebase:
status: Unknown → Confirmed
Revision history for this message
Harald Sitter (apachelogger) wrote : Re: Konqeuror crash with back button

The crash happens in KHTML, sourcepackage => kde4libs

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Should be fixed in KDE 4.2.1.

Changed in kde4libs:
status: Triaged → Fix Released
Changed in kdebase:
status: Confirmed → Invalid
Changed in kdebase:
status: Invalid → Confirmed
Changed in kdebase:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.