Bug 105609 - Konqueror crashes with Signal 11 (SIGSEGV) when program is closed normally.
Summary: Konqueror crashes with Signal 11 (SIGSEGV) when program is closed normally.
Status: RESOLVED DUPLICATE of bug 109498
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.3.2
Platform: Mandrake RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-13 15:14 UTC by Eddie Faulkner
Modified: 2005-08-10 15:42 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 Eddie Faulkner 2005-05-13 15:14:53 UTC
Version:           3.3.2 (using KDE KDE 3.3.2)
Installed from:    Mandrake RPMs
Compiler:          GCC 3.4.3 
OS:                Linux

Whilst working in Konqueror, no matter what i have been doing, browsing web, file management, anything, closure of the program using the X in the corner, or using File/Quit from top toolbar causes Konqueror to crash. I have a generated Backtrace from it, which I hope will assist with fixing this bug.

BACKTRACE >>>
[KCrash handler]
#6  0xb6c9e058 in pthread_mutex_lock () from /lib/libpthread.so.0
#7  0xb6d600af in _XUnregisterFilter () from /usr/X11R6/lib/libX11.so.6
#8  0xb6d49270 in XrmEnumerateDatabase () from /usr/X11R6/lib/libX11.so.6
#9  0xb6d3111a in XKeysymToString () from /usr/X11R6/lib/libX11.so.6
#10 0xb78f46f0 in KKeyServer::Sym::toString () from /usr/lib/libkdecore.so.4
#11 0xb78f4f0f in KKeyServer::Sym::toStringInternal ()
   from /usr/lib/libkdecore.so.4
#12 0xb78f4fc2 in KKey::toStringInternal () from /usr/lib/libkdecore.so.4
#13 0xb78f5076 in KKeySequence::toStringInternal ()
   from /usr/lib/libkdecore.so.4
#14 0xb78f5b59 in KShortcut::toStringInternal () from /usr/lib/libkdecore.so.4
#15 0xb7929405 in KAccelBase::removeConnection ()
   from /usr/lib/libkdecore.so.4
#16 0xb79295e4 in KAccelBase::slotRemoveAction ()
   from /usr/lib/libkdecore.so.4
#17 0xb7929696 in KAccelActions::remove () from /usr/lib/libkdecore.so.4
#18 0xb79296c7 in KAccelBase::remove () from /usr/lib/libkdecore.so.4
#19 0xb792976d in KAccelPrivate::removeAction () from /usr/lib/libkdecore.so.4
#20 0xb785323e in KAccel::remove () from /usr/lib/libkdecore.so.4
#21 0xb7bfa90f in KAction::removeKAccel () from /usr/lib/libkdeui.so.4
#22 0xb7c05106 in KActionCollection::unplugShortcuts ()
   from /usr/lib/libkdeui.so.4
#23 0xb7c051cc in KActionCollection::prepareXMLUnplug ()
   from /usr/lib/libkdeui.so.4
#24 0xb7c0522a in KXMLGUIClient::prepareXMLUnplug ()
   from /usr/lib/libkdeui.so.4
#25 0xb7c2fc9f in KXMLGUIFactory::removeClient () from /usr/lib/libkdeui.so.4
#26 0xb7fc59d7 in KParts::MainWindow::createGUI ()
   from /usr/lib/libkparts.so.2
#27 0xb690e424 in ?? () from /usr/lib/libkdeinit_konqueror.so
#28 0x0819c2a8 in ?? ()
#29 0x082b1ab8 in ?? ()
#30 0xbfffd63c in ?? ()
#31 0xb7fb105e in KParts::PartManager::staticMetaObject ()
   from /usr/lib/libkparts.so.2
#32 0xb690f111 in ?? () from /usr/lib/libkdeinit_konqueror.so
#33 0x0819c2a8 in ?? ()
#34 0x082b1ab8 in ?? ()
#35 0x00000001 in ?? ()
#36 0xb694a8d4 in ?? () from /usr/lib/libkdeinit_konqueror.so
#37 0xbfffd7b0 in ?? ()
#38 0xbfffd7b0 in ?? ()
#39 0xbfffd7f8 in ?? ()
#40 0xb690f37c in ?? () from /usr/lib/libkdeinit_konqueror.so
#41 0x081a0ed8 in ?? ()
#42 0x082b1ab8 in ?? ()
#43 0x00000000 in ?? ()
#44 0xb7617cd9 in typeinfo name for QChildEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#45 0xbfffd7c0 in ?? ()
#46 0x082b301c in ?? ()
#47 0x01000344 in ?? ()
#48 0x081a0ed8 in ?? ()
#49 0x0830e7f0 in ?? ()
#50 0x0827cf50 in ?? ()
#51 0x00000344 in ?? ()
#52 0xb694a8d4 in ?? () from /usr/lib/libkdeinit_konqueror.so
#53 0xb76ec550 in vtable for QGArray () from /usr/lib/qt3/lib/libqt-mt.so.3
#54 0x00000000 in ?? ()
#55 0xbfffd7f8 in ?? ()
#56 0xb693bc07 in kdemain () from /usr/lib/libkdeinit_konqueror.so

I hope this can be rectified, as the continual shutdown of Konqueror without warning is driving me nuts.
Comment 1 Tommi Tervo 2005-05-13 15:58:33 UTC

*** This bug has been marked as a duplicate of 103855 ***
Comment 2 Eddie Faulkner 2005-05-13 16:28:40 UTC
As far as I can see,  the 2 generated backtraces signify different things occurring. I cannot work out how this is a duplicate of bug 103855 because of the nature of the crash.  I would appreciate this being looked at again.
Comment 3 Tommi Tervo 2005-05-13 16:38:49 UTC
That's known kaffeine crash, is this dupe better?

*** This bug has been marked as a duplicate of 102981 ***
Comment 4 Eddie Faulkner 2005-05-13 18:53:44 UTC
Yes - It looks to be a lot closer to the one I reported. I dont understand though how Konqueror crashes, if this is a Kaffeine problem, when I havent used Kaffeine?  Its wierd, still, you guys are the developers. I'll let you sort it!!!
Comment 5 Eddie Faulkner 2005-05-14 15:43:21 UTC
There may not be any need to sort it. I have found a resolution which allows Konqueror to work normally with the kaffeine plugin. Its a bit of work, but does allow normal usage of Konqueror.  Resolution consists of the complete removal of all installed components of Kaffeine 0.6, and the addition of src compiled versions of xine-lib 1.0.1, xine-ui 0.99.3, and then kaffeine 0.4.3 - this resolution has produced successful results on my system with Konqueror quitting normally and no production of the KCrashHandler.  If anyone has comments on this resolution, please say whether it works for you or not.  
Comment 6 Tommi Tervo 2005-08-10 15:42:21 UTC

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