I recently upgraded to kde 3.3 and have since been unable to start kontact. Although I can start the individual components with no problem starting kontact itself results in a very quick crash. I am running Slackware 10.0, 2.4.26 and upgraded to 3.3 via swaret. I tried downloading and installing kde-pim 3.3.1 from source and still get the same result.
$ kontact --version gives me Qy 3.3.3, KDE 3.3.1 and kontact 1.0.1
Starting kontact from a console gives me:
$ kontact (core): Loading Plugin: Mail
kontact (core): LIBNAMEPART: libkmailpart
kontact (core): Loading Plugin: Feeds
kontact (core): LIBNAMEPART: libakregatorpart
kontact (core): Loading Plugin: Contacts
kontact (core): LIBNAMEPART: libkaddressbookpart
KCrash: Application 'kontact' crashing...
and the backtrace is:
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 2711)]
[KCrash handler]
#5 0x00000000 in ?? ()
#6 0x0805b756 in Kontact::MainWindow::loadPlugins ()
#7 0x08059e1b in Kontact::MainWindow::initObject ()
#8 0x0805e716 in Kontact::MainWindow::qt_invoke ()
#9 0x40f0d18c in QObject::activate_signal ()
from /usr/lib/qt/lib/libqt-mt.so.3
#10 0x4122ebca in QSignal::signal () from /usr/lib/qt/lib/libqt-mt.so.3
#11 0x40f2736d in QSignal::activate () from /usr/lib/qt/lib/libqt-mt.so.3
#12 0x40f2eb53 in QSingleShotTimer::event () from /usr/lib/qt/lib/libqt-mt.so.3
#13 0x40eb084f in QApplication::internalNotify ()
from /usr/lib/qt/lib/libqt-mt.so.3
#14 0x40eafe4e in QApplication::notify () from /usr/lib/qt/lib/libqt-mt.so.3
#15 0x40a43873 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4
#16 0x40ea0085 in QEventLoop::activateTimers ()
from /usr/lib/qt/lib/libqt-mt.so.3
#17 0x40e5a97b in QEventLoop:
rocessEvents ()
from /usr/lib/qt/lib/libqt-mt.so.3
#18 0x40ec2ba8 in QEventLoop::enterLoop () from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x40ec2a58 in QEventLoop::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#20 0x40eb0aa1 in QApplication::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#21 0x080593c5 in main ()
none of which means too much to me. I have googled and tried bugs.kde.org but I've not really come across anything to point me in the right direction. I would be grateful for any pointers.
regards,
