Application that crashed: konqueror Version of the application: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 125" KDE Version: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 125" Qt Version: 4.5.1 Operating System: Linux 2.6.27.21-0.1-default x86_64 Distribution: "openSUSE 11.1 (x86_64)" What I was doing when the application crashed: I was reviewing my Monster.com profile, made no changes on the Edit Profile page, and clicked Back to return to the main page when Konqueror crashed. I had just changed my site password, and closed the tab where I had previously logged in. FWIW, when I closed the tab, I got a message about entered data going away; I clicked Cancel to approve that choice. -- Backtrace: Application: Konqueror (kdeinit), signal: Segmentation fault [KCrash Handler] #5 0x00007fdb01c913fb in QString::operator==(QString const&) const () from /usr/lib64/libQtCore.so.4 #6 0x00007fdaecc86add in KHTMLPart::restoreState (this=0x283eb10, stream=<value optimized out>) at /usr/include/QtCore/qstring.h:400 #7 0x00007fdaf589cbd0 in KonqView::restoreHistory (this=0x3217400) at /usr/src/debug/kdebase-4.2.85/apps/konqueror/src/konqview.cpp:871 #8 0x00007fdaf58e9a6a in KonqMainWindow::slotGoHistoryDelayed (this=0x767fd0) at /usr/src/debug/kdebase-4.2.85/apps/konqueror/src/konqmainwindow.cpp:2821 #9 0x00007fdaf58f34a5 in KonqMainWindow::qt_metacall (this=0x767fd0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff0a246e50) at /usr/src/debug/kdebase-4.2.85/build/apps/konqueror/src/konqmainwindow.moc:438 #10 0x00007fdb01d4ec22 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #11 0x00007fdb01d53f9f in ?? () from /usr/lib64/libQtCore.so.4 #12 0x00007fdb01d48f43 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #13 0x00007fdaff09b78d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #14 0x00007fdaff0a3a2a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007fdb001b037b in KApplication::notify (this=0x7fff0a247b20, receiver=0x1b79de0, event=0x7fff0a247550) at /usr/src/debug/kdelibs-4.2.85/kdeui/kernel/kapplication.cpp:307 #16 0x00007fdb01d3915c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #17 0x00007fdb01d665c0 in ?? () from /usr/lib64/libQtCore.so.4 #18 0x00007fdb01d6293d in ?? () from /usr/lib64/libQtCore.so.4 #19 0x00007fdafdb7b0fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #20 0x00007fdafdb7e8cd in ?? () from /usr/lib64/libglib-2.0.so.0 #21 0x00007fdafdb7ea8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #22 0x00007fdb01d6289f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #23 0x00007fdaff132b0f in ?? () from /usr/lib64/libQtGui.so.4 #24 0x00007fdb01d379f2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #25 0x00007fdb01d37dbd in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #26 0x00007fdb01d3a0a4 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #27 0x00007fdaf591e749 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-4.2.85/apps/konqueror/src/konqmain.cpp:257 #28 0x00000000004071fe in launch (argc=4, _name=0x670658 "konqueror", args=<value optimized out>, cwd=0x6706ba "/home/mikemc/Documents", envc=93, envs=0x6714de "", reset_env=true, tty=0x0, avoid_loops=false, startup_id_str=0x6714e7 "linux-k0ig;1242838323;398247;12377_TIME16888164") at /usr/src/debug/kdelibs-4.2.85/kinit/kinit.cpp:667 #29 0x0000000000407a28 in handle_launcher_request (sock=39, who=<value optimized out>) at /usr/src/debug/kdelibs-4.2.85/kinit/kinit.cpp:1159 #30 0x0000000000407fb5 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.2.85/kinit/kinit.cpp:1343 #31 0x0000000000408af2 in main (argc=2, argv=0x7fff0a249118, envp=0x7fff0a249130) at /usr/src/debug/kdelibs-4.2.85/kinit/kinit.cpp:1779 This bug may be a duplicate of or related to bug 186993
This may be related to bug 186993. Thanks
*** This bug has been marked as a duplicate of bug 173870 ***