Bug 154991 - after editing contact clicking on another contact crashes Kontact or Kaddressbook
Summary: after editing contact clicking on another contact crashes Kontact or Kaddress...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-02 21:46 UTC by Laryssa
Modified: 2009-08-05 16:34 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 Laryssa 2008-01-02 21:46:43 UTC
Version:           Kontact - Version 1.2.4 (enterprise 20070904.708012), Kaddressbook - Version 3.5.6, KDE - 3.5.8 release 22.3 (using KDE KDE 3.5.8)
Installed from:    SuSE RPMs
OS:                Linux

I open Kontact, go to Contacts. I edit a few of them (click on them in the list, and have the editor on the bottom of the screen, I edit their categories). 

After a few of these, I click on another to edit it, and it crashes Kontact completely. It happens every time, after about four contacts edited.
Comment 1 Pino Toscano 2008-01-02 21:59:26 UTC
Can you please provide a backtrace as explained in the page: http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports
?
Comment 2 Laryssa 2008-01-03 00:26:31 UTC
I meant to, but it took considerably longer time to recreate the error...

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1241748992 (LWP 5500)]
[KCrash handler]
#9  0xb6cd10e5 in QListView::ensureItemVisible ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb544a926 in KAddressBookTableView::setSelected ()
   from /opt/kde3/lib/kde3/libkaddrbk_tableview.so
#11 0xb55245d0 in KAddressBookView::updateView ()
   from /opt/kde3/lib/libkaddressbook.so.0
#12 0xb5524757 in KAddressBookView::qt_invoke ()
   from /opt/kde3/lib/libkaddressbook.so.0
#13 0xb544a713 in KAddressBookTableView::qt_invoke ()
   from /opt/kde3/lib/kde3/libkaddrbk_tableview.so
#14 0xb6beda11 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb6bee6ed in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb5551629 in KAB::SearchManager::contactsUpdated ()
   from /opt/kde3/lib/libkaddressbook.so.0
#17 0xb5551946 in KAB::SearchManager::search ()
   from /opt/kde3/lib/libkaddressbook.so.0
#18 0xb5552152 in KAB::SearchManager::reload ()
   from /opt/kde3/lib/libkaddressbook.so.0
#19 0xb551c1b7 in KABCore::addressBookChanged ()
   from /opt/kde3/lib/libkaddressbook.so.0
#20 0xb552120e in KABCore::qt_invoke () from /opt/kde3/lib/libkaddressbook.so.0
#21 0xb6bedaad in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb6bee6ed in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb6f2a869 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb6c112cf in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb6b8e557 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb6b8f321 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb724a6f2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#28 0xb6b83763 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb6b3d4f0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb6ba5380 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0xb6ba5216 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb6b8e10f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x0805a759 in main ()
Comment 3 Christophe Marin 2008-06-26 18:54:45 UTC

*** This bug has been marked as a duplicate of 151942 ***
Comment 4 Tobias Koenig 2009-08-05 16:34:33 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.