Bug 120494

Summary:	Attempt to open Kontact results in crash indicating signal 11 (SIGSEGV) -- Kontact never opens successfully -- have rebooted and tried in Gnome as well as KDE
Product:	[Unmaintained] kmail	Reporter:	Doug Hiland <doug.hiland>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Doug Hiland 2006-01-20 06:24:55 UTC

Version:           kmail - Email client with Suse 9.3 (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

I attempt to open Kontact to view email...Contact screen shows for approx 2 seconds..then issues the following:
The application Kontact (kontact) crasehed and caused the singal 11 (SIGSEGV).
What is this?
An application mostly receives the SIGSEGV signal due to a bug in the application.  

Also following is the backtrace info.
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(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)
(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)
(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)
(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread 1105521376 (LWP 13544)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#7  0x00000011 in ?? ()
#8  0x40e1f524 in KXMLGUI::ActionList::unplug ()
   from /opt/kde3/lib/libkdeui.so.4
#9  0x40e70848 in KXMLGUI::ContainerNode::unplugClient ()
   from /opt/kde3/lib/libkdeui.so.4
#10 0x40e70bc5 in KXMLGUI::ContainerNode::unplugActions ()
   from /opt/kde3/lib/libkdeui.so.4
#11 0x40e70c4c in KXMLGUI::ContainerNode::destruct ()
   from /opt/kde3/lib/libkdeui.so.4
#12 0x40e70e5c in KXMLGUI::ContainerNode::destructChildren ()
   from /opt/kde3/lib/libkdeui.so.4
#13 0x40e70c40 in KXMLGUI::ContainerNode::destruct ()
   from /opt/kde3/lib/libkdeui.so.4
#14 0x40f1b8d8 in KXMLGUIFactory::removeClient ()
   from /opt/kde3/lib/libkdeui.so.4
#15 0x40915cb2 in KParts::MainWindow::createGUI ()
   from /opt/kde3/lib/libkparts.so.2
#16 0x0805f957 in ?? ()
#17 0x081865b8 in ?? ()
#18 0x084142e8 in ?? ()
#19 0xbfffe5d0 in ?? ()
#20 0x40008002 in do_lookup_x () from /lib/ld-linux.so.2
#21 0x0806306a in ?? ()
#22 0x081865b8 in ?? ()
#23 0x082c6928 in ?? ()
#24 0x081865b8 in ?? ()
#25 0x0840f388 in ?? ()
#26 0x0806ba5c in static_QUType_QString ()
#27 0x0000000a in ?? ()
#28 0x081e3c48 in ?? ()
#29 0x41d05a10 in ?? () from /usr/lib/libstdc++.so.5
#30 0xbfffe7a0 in ?? ()
#31 0x081feec0 in ?? ()
#32 0xbfffe698 in ?? ()
#33 0x081866a0 in ?? ()
#34 0x08195c70 in ?? ()
#35 0x419b48d4 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xbfffe6a8 in ?? ()
#37 0x41d94a31 in _int_malloc () from /lib/tls/libc.so.6
#38 0x0806343e in ?? ()
#39 0x081865b8 in ?? ()
#40 0x41e48800 in __malloc_initialize_hook () from /lib/tls/libc.so.6
#41 0x00000004 in ?? ()
#42 0x419b48d4 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0x0815c920 in ?? ()
#44 0xbfffe7b0 in ?? ()
#45 0xbfffe788 in ?? ()
#46 0x41558e7e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#47 0x41558e7e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#48 0x418ac3f2 in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#49 0x41576353 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#50 0x4157dda3 in QSingleShotTimer::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#51 0x414f5d5f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#52 0x414f7a83 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#53 0x411816b1 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#54 0x414ea50c in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#55 0x414a3286 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#56 0x4150de51 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#57 0x4150dc96 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#58 0x414f794f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#59 0x08063d75 in ?? ()
#60 0xbfffee80 in ?? ()
#61 0x00000001 in ?? ()
#62 0x00000001 in ?? ()
#63 0x00000000 in ?? ()
#64 0x00000000 in ?? ()
#65 0x00000001 in ?? ()
#66 0x08069124 in typeinfo name for QPtrList<KParts::Part> ()
#67 0x00000000 in ?? ()
#68 0x080682ca in typeinfo name for QPtrList<KParts::Part> ()
#69 0x08068749 in typeinfo name for QPtrList<KParts::Part> ()
#70 0x08c777ef in ?? ()
#71 0x413d90ba in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#72 0x4000dbce in _dl_name_match_p () from /lib/ld-linux.so.2
#73 0x41d46e80 in __libc_start_main () from /lib/tls/libc.so.6
#74 0x08058ab1 in ?? ()

Comment 1 Stephan Binner 2006-01-20 15:08:47 UTC

Does starting KMail alone work fine?

Comment 2 Doug Hiland 2006-01-20 22:06:27 UTC

No gives the same crash...this application was working fine until I
tried to "customize" the tool bar by attempting to use the spam tool
in SuSe 9.3..Since that time -- total failure.  Evolution email works
fine..no issues..

Thanks.
On 20 Jan 2006 14:08:48 -0000, Stephan Binner <binner@kde.org> wrote:
[bugs.kde.org quoted mail]


--
Doug Hiland
EMAIL:  doug.hiland@gmail.com
doug.hiland@gmail.com

Comment 3 Thiago Macieira 2006-06-17 22:21:47 UTC


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