Bug 139517 - Crashes on startup and / or configuration
Summary: Crashes on startup and / or configuration
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 143865 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-01-02 20:20 UTC by Markus Knorn
Modified: 2007-08-18 14:15 UTC (History)
1 user (show)

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 Markus Knorn 2007-01-02 20:20:14 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
OS:                Linux

Kontact crashes when configuration is changed. On restart Kontact keeps on crashing. Deleting the .kde-folder let you start Kontact again, but is not a solution because whole KDE configuration is gone.
Comment 1 Bram Schoenmakers 2007-01-02 20:37:54 UTC
Please provide a backtrace of the crash and describe what you changed and in which component you were working.
Comment 2 Markus Knorn 2007-01-02 21:38:33 UTC
Mostly crashes of Kontact appear while configuring the email accounts. After such a crash Kontact never starts again.
Last crash appeared after changing the K-menu style. Well, I don't see a pattern.

Überprüfung der Systemkonfiguration beim Start deaktiviert.

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1241708128 (LWP 5592)]
(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)
(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]
#9  0xb6ea40bd in QString::QString () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb6678f8c in KCal::IncidenceBase::uid () from /opt/kde3/lib/libkcal.so.2
#11 0xb5672258 in KCal::ResourceKolab::incidenceUpdated ()
   from /opt/kde3/lib/libkcalkolab.so.0
#12 0xb5670693 in KCal::ResourceKolab::addIncidence ()
   from /opt/kde3/lib/libkcalkolab.so.0
#13 0xb567125a in KCal::ResourceKolab::fromKMailAddIncidence ()
   from /opt/kde3/lib/libkcalkolab.so.0
#14 0xb5678345 in Kolab::KMailConnection::fromKMailAddIncidence ()
   from /opt/kde3/lib/libkcalkolab.so.0
#15 0xb567d6f9 in Kolab::KMailConnection::process ()
   from /opt/kde3/lib/libkcalkolab.so.0
#16 0xb7063e77 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4
#17 0xb70655cb in DCOPRef::sendInternal () from /opt/kde3/lib/libDCOP.so.4
#18 0xb70657fc in DCOPClient::processPostedMessagesInternal ()
   from /opt/kde3/lib/libDCOP.so.4
#19 0xb70658cd in DCOPClient::qt_invoke () from /opt/kde3/lib/libDCOP.so.4
#20 0xb6bd33cd in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb6bd400d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb6f0f2b9 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb6bf6bdf in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb6b74647 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb6b754f9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb72321f2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#27 0xb6b69663 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb6b23bd0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb6b8b0e0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb6b8af76 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0xb6b7400f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x08058c12 in QWidget::setUpdatesEnabled ()
#33 0xbfb5c9cc in ?? ()
#34 0x00000001 in ?? ()
#35 0x00000001 in ?? ()
#36 0x00000000 in ?? ()
Comment 3 Markus Knorn 2007-01-04 18:24:34 UTC
Had my last message been sent? Didn't get the usual mail.
Comment 4 Bram Schoenmakers 2007-01-04 19:54:13 UTC
Your backtrace was received. Normally you don't receive mails from your own additions to Bugzilla.
Comment 5 Sebastian Turzański 2007-02-08 13:26:17 UTC
i confirm the problem

here is my backtrace

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240922448 (LWP 4791)]
[New Thread -1284580448 (LWP 4795)]
[New Thread -1276187744 (LWP 4794)]
[New Thread -1267795040 (LWP 4793)]
[New Thread -1259402336 (LWP 4792)]
[KCrash handler]
#6  0xffffffcc in ?? ()
#7  0xb7e19072 in Kontact::Plugin::part ()
   from /opt/kde3/lib/libkpinterfaces.so.1
#8  0x0805bee0 in Kontact::MainWindow::selectPlugin ()
#9  0x08059ad2 in Kontact::MainWindow::loadSettings ()
#10 0x0805d902 in Kontact::MainWindow::initObject ()
#11 0x0805866f in KontactApp::newInstance ()
#12 0xb728241d in KUniqueApplication::processDelayed ()
   from /opt/kde3/lib/libkdecore.so.4
#13 0xb72bc2c8 in KUniqueApplication::qt_invoke ()
   from /opt/kde3/lib/libkdecore.so.4
#14 0xb6c8467d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb6fbd3be in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb6ca0727 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb6ca7ae3 in QSingleShotTimer::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb6c25547 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb6c26311 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0xb72e0e23 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#21 0xb6c1a6e6 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb6bd4940 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb6c3c368 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb6c3c1fe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb6c250ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x08058c39 in main ()


-----------------------
but the interesting output is in konsole (when kmail was not running when i started to run kontact) :

polrus@suse:~> kontact
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
*** KMail got signal 11 (Crashing)
ERROR: Communication problem with kontact, it probably crashed.
polrus@suse:~> KCrash: Application 'kontact' crashing...


-------------------------------------------
The interesting thing is that kmail run alone(not under kontact) works OK


Comment 6 Nikolai Försterling 2007-02-19 03:49:55 UTC
same here (backtrace too)

[nf@rex ~]$ kontact
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
*** KMail got signal 11 (Crashing)
ERROR: Communication problem with kontact, it probably crashed.
[nf@rex ~]$ KCrash: Application 'kontact' crashing...

all components can be started separately, but not with Kontact... strange
Comment 7 Nikolai Försterling 2007-02-19 03:53:39 UTC
[nf@rex ~]$ rpm -q kdebase3 kdelibs3 kdepim3
kdebase3-3.5.6-33.3
kdelibs3-3.5.6-25.2
kdepim3-3.5.6-21.2
Comment 8 Nikolai Försterling 2007-02-22 15:09:36 UTC
The problem persists even after an update:
[nf@rex ~]$ rpm -q kdebase3 kdelibs3 kdepim3
kdebase3-3.5.6-42.1
kdelibs3-3.5.6-31.2
kdepim3-3.5.6-24.1

It doesn't make a difference whether i use my existing user account or create a new test account with no KDE configs.

As before, the apps can be started separately.
Comment 9 Thomas McGuire 2007-03-28 16:03:09 UTC
Sebastian, your crash is caused by basket. Please completely remove basket from your system and the crash is gone.
Comment 10 Nikolai Försterling 2007-03-31 03:23:51 UTC
wow, 
how did you trace that output back to basket??
But hey, works for me, too.
Comment 11 Sebastian Turzański 2007-03-31 10:57:56 UTC
yes , removing Basket worked - and the same question - how did You find out it was Basket?
Comment 12 Thomas McGuire 2007-03-31 18:24:56 UTC
>how did you trace that output back to basket?? 
Magic.



Ok, actually I remembered the first line of the backtrace from another bug report, which was about the basket crash.
Comment 13 Tommi Tervo 2007-04-05 09:03:14 UTC
*** Bug 143865 has been marked as a duplicate of this bug. ***
Comment 14 Remco Bloemen 2007-04-17 20:07:47 UTC
*** This bug has been confirmed by popular vote. ***
Comment 15 Markus Knorn 2007-08-08 15:01:09 UTC
For a recent time no crashes occurred. Problem seems to be solved. I am going to makr the bug as being resolved if there are no further comments till Aug 10.

Regards
Comment 16 Markus Knorn 2007-08-18 10:59:53 UTC
Well, I heard nothing new about this bug so I guess a patch just solved the problem. Kind regards
Comment 17 Nikolai Försterling 2007-08-18 14:15:52 UTC
Yes, seems ok now :-)