Bug 60655 - Get a SIGSEGV crash (signal 11) every time I close a konqueror window
Summary: Get a SIGSEGV crash (signal 11) every time I close a konqueror window
Status: RESOLVED DUPLICATE of bug 53603
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-02 22:44 UTC by John Harlow
Modified: 2003-07-02 23:30 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Harlow 2003-07-02 22:44:22 UTC
Version:           3.1 (using KDE KDE 3.1)
Installed from:    Unlisted Binary Package
OS:          Linux

My KDE bits are installed from the ASP rpms. They are 3.1.0. My system in RH 7.3 w/2.4.21 kernel. Anytime I close any Konqueror window, I get a SIGSEGV. This is totally reproducible.

Here is the backtrace:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 4957)]

0x420aa549 in wait4 () from /lib/i686/libc.so.6
#0  0x420aa549 in wait4 () from /lib/i686/libc.so.6
#1  0x42125f10 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x40d7f673 in waitpid () from /lib/i686/libpthread.so.0
#3  0x4057f6ff in KCrash::defaultCrashHandler ()
   from /usr/lib/libkdecore-gcc2.96.so.4
#4  <signal handler called>
#5  0x40ab4aca in QGDict::unlink_ascii ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#6  0x40ab4f05 in QGDict::take_ascii ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#7  0x40385806 in KActionCollection::_take ()
   from /usr/lib/libkdeui-gcc2.96.so.4
#8  0x4038591f in KActionCollection::take ()
   from /usr/lib/libkdeui-gcc2.96.so.4
#9  0x4037971f in KAction::~KAction () from /usr/lib/libkdeui-gcc2.96.so.4
#10 0x4089708a in QObject::~QObject ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#11 0x403851e8 in KActionCollection::~KActionCollection ()
   from /usr/lib/libkdeui-gcc2.96.so.4
#12 0x408c08da in QWidget::~QWidget ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#13 0x40957f40 in QMainWindow::~QMainWindow ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#14 0x403bfe05 in KMainWindow::~KMainWindow ()
   from /usr/lib/libkdeui-gcc2.96.so.4
#15 0x40051573 in KParts::MainWindow::~MainWindow ()
   from /usr/lib/libkparts-gcc2.96.so.2
#16 0x41065dd4 in KonqMainWindow::~KonqMainWindow ()
   from /usr/lib/konqueror-gcc2.96.so
#17 0x40897480 in QObject::event () from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#18 0x408c5711 in QWidget::event () from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#19 0x4095976f in QMainWindow::event ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#20 0x40845163 in QApplication::internalNotify ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#21 0x40844f4a in QApplication::notify ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#22 0x4051a59d in KApplication::notify () from /usr/lib/libkdecore-gcc2.96.so.4
#23 0x40845eed in QApplication::sendPostedEvents ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#24 0x40856004 in QEventLoop::enterLoop ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#25 0x40855eb5 in QEventLoop::exec ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#26 0x408452e0 in QApplication::exec ()
   from /usr/lib/qt3-gcc2.96/lib/libqt-mt.so.3
#27 0x41063579 in main () from /usr/lib/konqueror-gcc2.96.so
#28 0x0804cc74 in strcpy ()
#29 0x0804d9ac in strcpy ()
#30 0x0804dda8 in strcpy ()
#31 0x0804ed55 in strcpy ()
#32 0x42015b07 in __libc_start_main () from /lib/i686/libc.so.6
Comment 1 Maksim Orlovich 2003-07-02 23:30:00 UTC
Fixed already. As a workaround you can hide the bookmarks toolbar; or  
alternatively make sure you don't have two bookmarks to one URL.  
(Upgrading to 3.1.1+ may be easier, though). 
 
Thanks a lot for taking your time to report this. It's because other people like 
you have reported this bug before that it has been fixed.  
 

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