Bug 58538

Summary: kaddressbook crashes on start
Product: kab3 Reporter: Jan Spitalnik <spitalnik>
Component: generalAssignee: Tobias Koenig <tokoe>
Status: RESOLVED UNMAINTAINED    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jan Spitalnik 2003-05-15 20:27:52 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc-3.2 debian unstable
OS:          Linux

hi,
kaddressbook crashes on every start, also imho it causes associated crash in kmail (when you have automatic completion of email addresses in composer on). crash output with --enable-debug:

[New Thread 16384 (LWP 26772)]
0x4d040b89 in wait4 () from /lib/libc.so.6
#0  0x4d040b89 in wait4 () from /lib/libc.so.6
#1  0x4d0b4020 in sys_sigabbrev () from /lib/libc.so.6
#2  0x4ce7a061 in waitpid () from /lib/libpthread.so.0
#3  0x4c65e55f in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#4  0x4cfcd9d8 in sigaction () from /lib/libc.so.6
#5  0x4b9b1d02 in KABC::AddressBook::load() () from /usr/lib/libkabc.so.1
#6  0x4b9cb29d in KABC::StdAddressBook::init(bool) ()
   from /usr/lib/libkabc.so.1
#7  0x4b9cae93 in KABC::StdAddressBook::StdAddressBook() ()
   from /usr/lib/libkabc.so.1
#8  0x4b9cad00 in KABC::StdAddressBook::self() () from /usr/lib/libkabc.so.1
#9  0x4b8c37c4 in KABCore (this=0x80ff530, client=0xfffffe00, 
    parent=0x80ec188, name=0x0) at ../../kaddressbook/kabcore.cpp:77
#10 0x4b8f12c7 in KAddressBookMain (this=0x80ec188)
    at ../../kaddressbook/kaddressbookmain.cpp:39
#11 0x0804a187 in KAddressBookApp::newInstance() (this=0xbfffe600)
    at ../../kaddressbook/main.cpp:71
#12 0x4c6768c1 in KUniqueApplication::newInstanceNoFork() ()
   from /usr/lib/libkdecore.so.4
#13 0x4c676f11 in KUniqueApplication::qt_invoke(int, QUObject*) ()
   from /usr/lib/libkdecore.so.4
#14 0x4c9c8072 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/libqt-mt.so.3
#15 0x4cc31d52 in QSignal::signal(QVariant const&) ()
   from /usr/lib/libqt-mt.so.3
#16 0x4c9de599 in QSignal::activate() () from /usr/lib/libqt-mt.so.3
#17 0x4c9e46e7 in QSingleShotTimer::event(QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#18 0x4c973d82 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#19 0x4c9735e8 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#20 0x4c5f2768 in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdecore.so.4
#21 0x4c951fab in QEventLoop::activateTimers() () from /usr/lib/libqt-mt.so.3
#22 0x4c932cf1 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/libqt-mt.so.3
#23 0x4c9853ff in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#24 0x4c9852bc in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#25 0x4c973f7c in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#26 0x0804a341 in main (argc=2, argv=0xbfffe754)
    at ../../kaddressbook/main.cpp:118
Comment 1 Tobias Koenig 2003-05-16 18:52:45 UTC
Hi Jan, 
 
I can't reproduce it here with fresh checkout from CVS HEAD. 
We had a lot of changes in the libraries over the last weeks, so maybe 
there is a version conflict. Could you update your sources please and 
tell me if it still crash? 
 
Ciao, 
Tobias 
Comment 2 Jan Spitalnik 2003-05-17 21:29:44 UTC
Subject: Re:  kaddressbook crashes on start

Dne p
Comment 3 Tobias Koenig 2003-05-18 14:01:00 UTC
Subject: Re:  kaddressbook crashes on start

On Sat, May 17, 2003 at 07:29:45PM -0000, Jan Spitalnik wrote:
> hi tobias,
Hi Jan,

> i did complete fresh compile of kdelibs,qt-copy and kdebase and it no longer 
> crashes. so it was something rotten in kdelibs i suppose. could you please 
> close the bug report?
Yepp, done with this email.

Ciao,
Tobias
Comment 4 Tobias Koenig 2009-08-05 15:52:35 UTC
The development of the old KAddressBook will be discontinued for KDE 4.4.
Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.