Bug 173507 - Konqueror SIGSEGV When "Back" Button Pressed
Summary: Konqueror SIGSEGV When "Back" Button Pressed
Status: RESOLVED DUPLICATE of bug 158794
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.1.2
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-25 13:08 UTC by Trebor Rude
Modified: 2008-10-25 18:29 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 Trebor Rude 2008-10-25 13:08:14 UTC
Version:            (using KDE 4.1.2)
Compiler:          x86_64-pc-linux-gnu-g++ 4.3.2 
OS:                Linux
Installed from:    Gentoo Packages

Started Konqueror (I don't have a default home page), entered "gg:rv710 linux" in the address text field. On the google page that came up, I selected the link to http://blogs.zdnet.com/hardware/?p=2603. After reading the story, I pressed the "back" button, and Konqueror crashed with a SIGSEGV. I restarted Konqueror, asked it to restore the session, pressed "back" again, and Konqueror crashed a second time. Here's the backtrace from the first crash:

Application: Konqueror (konqueror), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0x7f77adbf2750 (LWP 5012)]
[KCrash handler]
#5  0x00007f77aa63c86f in QString::operator== ()
   from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007f779fc9a6b5 in KHTMLPart::restoreState ()
   from /usr/kde/4.1/lib64/libkhtml.so.5
#7  0x00007f77ad785bd7 in KonqView::restoreHistory ()
   from /usr/kde/4.1/lib64/libkdeinit4_konqueror.so
#8  0x00007f77ad7c5066 in KonqMainWindow::slotGoHistoryDelayed ()
   from /usr/kde/4.1/lib64/libkdeinit4_konqueror.so
#9  0x00007f77ad7d035d in KonqMainWindow::qt_metacall ()
   from /usr/kde/4.1/lib64/libkdeinit4_konqueror.so
#10 0x00007f77aa6ea577 in QMetaObject::activate ()
   from /usr/lib64/qt4/libQtCore.so.4
#11 0x00007f77aa6f04b9 in QSingleShotTimer::timerEvent ()
   from /usr/lib64/qt4/libQtCore.so.4
#12 0x00007f77aa6e58b2 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007f77a95c9255 in QApplicationPrivate::notify_helper ()
   from /usr/lib64/qt4/libQtGui.so.4
#14 0x00007f77a95d03a2 in QApplication::notify ()
   from /usr/lib64/qt4/libQtGui.so.4
#15 0x00007f77ac88f774 in KApplication::notify ()
   from /usr/kde/4.1/lib64/libkdeui.so.5
#16 0x00007f77aa6d8667 in QCoreApplication::notifyInternal ()
   from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007f77aa6fff43 in QTimerInfoList::activateTimers ()
   from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007f77aa6fc95a in timerSourceDispatch ()
   from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007f77a5ddac06 in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#20 0x00007f77a5ddddf5 in g_main_context_iterate ()
   from /usr/lib/libglib-2.0.so.0
#21 0x00007f77a5dde007 in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#22 0x00007f77aa6fc8d9 in QEventDispatcherGlib::processEvents ()
   from /usr/lib64/qt4/libQtCore.so.4
#23 0x00007f77a964af96 in QGuiEventDispatcherGlib::processEvents ()
   from /usr/lib64/qt4/libQtGui.so.4
#24 0x00007f77aa6d7304 in QEventLoop::processEvents ()
   from /usr/lib64/qt4/libQtCore.so.4
#25 0x00007f77aa6d7482 in QEventLoop::exec ()
   from /usr/lib64/qt4/libQtCore.so.4
#26 0x00007f77aa6d941f in QCoreApplication::exec ()
   from /usr/lib64/qt4/libQtCore.so.4
#27 0x00007f77ad7f05c0 in kdemain ()
   from /usr/kde/4.1/lib64/libkdeinit4_konqueror.so
#28 0x00007f77a6d96486 in __libc_start_main () from /lib64/libc.so.6
#29 0x0000000000400999 in _start ()
#0  0x00007f77a6e17ca1 in nanosleep () from /lib64/libc.so.6

I do have flash enabled via kmplayer's npp support, using /usr/lib64/nsbrowser/plugins/npwrapper.libflashplayer.so which was generated by the Gentoo package net-www/nspluginwrapper-1.1.2
Comment 1 Frank Reininghaus 2008-10-25 18:29:42 UTC
Thanks for the bug report. This looks like a problem that has been reported a couple of times already.

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