Bug 124677 - Kopete crashes when k3b is starting
Summary: Kopete crashes when k3b is starting
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 3.5
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
: 119023 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-04-01 00:12 UTC by Javier Martínez Ortiz
Modified: 2009-08-05 16:29 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Javier Martínez Ortiz 2006-04-01 00:12:31 UTC
Version:           0.11.1 (using KDE KDE 3.5.1)
Installed from:    Slackware Packages
OS:                Linux

I have running Kopete on the systray, and I try to start k3b. k3b splash screen freezes while scan for CD drives and Kopete send a signal 11 (crash, I think).
I have a IBM ThinkPad A21m (Pentium III 800 Mhz, 256 MB RAM), with Slackware Linux (current updated) and KDE 3.5.1.

Here is the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/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)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3347)]
(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)
[KCrash handler]
#6  0x40234001 in KABC::VCardParser::parseVCards ()
   from /opt/kde/lib/libkabc.so.1
#7  0x4021fd7a in KABC::VCardTool::parseVCards ()
   from /opt/kde/lib/libkabc.so.1
#8  0x401f755b in KABC::VCardConverter::parseVCards ()
   from /opt/kde/lib/libkabc.so.1
#9  0x40201685 in KABC::VCardFormatPlugin::loadAll ()
   from /opt/kde/lib/libkabc.so.1
#10 0x422644b0 in KABC::ResourceFile::load ()
   from /opt/kde/lib/libkabc_file.so.1
#11 0x401c89af in KABC::AddressBook::load () from /opt/kde/lib/libkabc.so.1
#12 0x401f1493 in KABC::StdAddressBook::init () from /opt/kde/lib/libkabc.so.1
#13 0x401f1829 in KABC::StdAddressBook::StdAddressBook ()
   from /opt/kde/lib/libkabc.so.1
#14 0x401f188b in KABC::StdAddressBook::self () from /opt/kde/lib/libkabc.so.1
#15 0x40130be5 in Kopete::KABCPersistence::addressBook ()
   from /opt/kde/lib/libkopete.so.1
#16 0x0806e254 in QGList::count ()
#17 0x0806edd8 in QGList::count ()
#18 0x4144c4e4 in QObject::activate_signal ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x4178adcd in QSignal::signal () from /usr/lib/qt/lib/libqt-mt.so.3
#20 0x41466f41 in QSignal::activate () from /usr/lib/qt/lib/libqt-mt.so.3
#21 0x4146ea43 in QSingleShotTimer::event ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#22 0x413e7f2f in QApplication::internalNotify ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#23 0x413e80cc in QApplication::notify () from /usr/lib/qt/lib/libqt-mt.so.3
#24 0x40f768c5 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4
#25 0x413db48c in QEventLoop::activateTimers ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#26 0x41394281 in QEventLoop::processEvents ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#27 0x413fe691 in QEventLoop::enterLoop () from /usr/lib/qt/lib/libqt-mt.so.3
#28 0x413fe5e6 in QEventLoop::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#29 0x413e708f in QApplication::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#30 0x0806d9f3 in ?? ()
#31 0xbffff820 in ?? ()
#32 0xbffff800 in ?? ()
#33 0xbffff800 in ?? ()
#34 0x00000000 in ?? ()

I hope this will be useful.
Comment 1 Tobias Koenig 2006-05-09 14:03:46 UTC
Hi,

could you provide your addressbook (per private mail to tokoe@kde.org) for further
testing, please?

Ciao,
Tobias
Comment 2 Andreas Kling 2006-07-31 13:35:11 UTC
*** Bug 119023 has been marked as a duplicate of this bug. ***
Comment 3 Andreas Kling 2006-07-31 13:35:20 UTC
*** Bug 130492 has been marked as a duplicate of this bug. ***
Comment 4 Chris Kerr 2007-06-02 10:37:02 UTC
I'm sorry - I don't see the connection between this bug and bugs #119023 and #130492 - they are obviously duplicates of each other, but this seems to be a completely different problem (kopete + k3b versus kmail + kabc). If they are in fact caused by the same underlying bug, can someone please explain how?
Comment 5 Tobias Koenig 2008-09-04 12:53:27 UTC
No reply from author
Comment 6 Tobias Koenig 2009-08-05 16:29:24 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.