Bug 179421 - Segmentation fault after clicking 'back' button
Summary: Segmentation fault after clicking 'back' button
Status: RESOLVED DUPLICATE of bug 158794
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.1.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-02 22:40 UTC by Lars Gjesse Kjellberg
Modified: 2009-01-03 00:14 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 Lars Gjesse Kjellberg 2009-01-02 22:40:39 UTC
Version:           4.1.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Sorry - I can't remember which site I had visited. But fortunately I had loaded debugging symbols, so I hope the backtrace might be useful:

Program: Konqueror (konqueror), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb609c8d0 (LWP 6093)]
[New Thread 0xac316b90 (LWP 7116)]
[KCrash handler]
#6  0xb74092ab in QString::operator== () from /usr/lib/libQtCore.so.4
#7  0xb4141cd0 in KHTMLPart::restoreState (this=0xb4d2480, stream=@0xbfa95dd8)
    at /usr/include/qt4/QtCore/qstring.h:372
#8  0xb416c9fe in KHTMLPartBrowserExtension::restoreState (this=0xaef9420, 
    stream=@0xbfa95dd8)
    at /build/buildd/kde4libs-4.1.3/khtml/khtml_ext.cpp:104
#9  0xb4141c7f in KHTMLPart::restoreState (this=0xc6fe0c0, stream=@0xbfa95efc)
    at /build/buildd/kde4libs-4.1.3/khtml/khtml_part.cpp:5683
#10 0xb416c9fe in KHTMLPartBrowserExtension::restoreState (this=0xb781b28, 
    stream=@0xbfa95efc)
    at /build/buildd/kde4libs-4.1.3/khtml/khtml_ext.cpp:104
#11 0xb7fc0156 in KonqView::restoreHistory (this=0xc4c3190)
    at /build/buildd/kdebase-4.1.3/apps/konqueror/src/konqview.cpp:859
#12 0xb8016ce0 in KonqMainWindow::slotGoHistoryDelayed (this=0xa14ef88)
    at /build/buildd/kdebase-4.1.3/apps/konqueror/src/konqmainwindow.cpp:2809
#13 0xb80201c7 in KonqMainWindow::qt_metacall (this=0xa14ef88, 
    _c=QMetaObject::InvokeMetaMethod, _id=104, _a=0xbfa960a8)
    at /build/buildd/kdebase-4.1.3/obj-i486-linux-gnu/apps/konqueror/src/konqmainwindow.moc:434
#14 0xb74cca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb74cd7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb74d2db7 in ?? () from /usr/lib/libQtCore.so.4
#17 0xb74d2edc in ?? () from /usr/lib/libQtCore.so.4
#18 0xb74c753f in QObject::event () from /usr/lib/libQtCore.so.4
#19 0xb69bb8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#20 0xb69c372e in QApplication::notify () from /usr/lib/libQtGui.so.4
#21 0xb7987b2d in KApplication::notify (this=0xbfa96984, receiver=0xc830670, 
    event=0xbfa9653c)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#22 0xb74b7e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#23 0xb74e5d81 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb74e2520 in ?? () from /usr/lib/libQtCore.so.4
#25 0xb642e6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb6431da3 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb6431f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb74e2478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#29 0xb6a55ea5 in ?? () from /usr/lib/libQtGui.so.4
#30 0xb74b652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#31 0xb74b66ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#32 0xb74b8da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#33 0xb69bb767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#34 0xb804d2ed in kdemain (argc=2, argv=0xbfa96ca4)
    at /build/buildd/kdebase-4.1.3/apps/konqueror/src/konqmain.cpp:227
#35 0x080485b2 in main (argc=)
    at /build/buildd/kdebase-4.1.3/obj-i486-linux-gnu/apps/konqueror/src/konqueror_dummy.cpp:3
#0  0xb8095430 in __kernel_vsyscall ()
Comment 1 Dario Andres 2009-01-03 00:14:45 UTC

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