In gutsy, kontact now crashes on startup (SIGSEGV)

Okay, so I found a pattern, and a TERRIBLE UGLY HORRIBLE workaround.

Here are the steps to replicate this problem:

1) Make sure basket is installed. If basket is installed and normally started up with kontact, I would guess that it would crash if you tried to start kontact now.

2) Start basket

3) Start kontact

4) Kill basket

5) Click the Baskets icon inside of kontact.

6) Crash and burn.

My work-around is to simply start basket before kontact, and leave it running. Normally Basket was started and run by kontact, and I really miss that functionality, but this is better than nothing for now.

Did we forget to move Basket over with the rest of the last round of updates or something?

BTW, kontact says that it is Version 1.2.4 (enterprise 0.20070508.662491)

And baskets is Version 1.0.2

I can confirm the crash after installing basket. Without basket, kontact starts up fine. The workaround presented in the description works. I am using latest gutsy on AMD64.

I can confirm this on i386 after installing basket kontact crashes.

I can confirm this bug, and confirm also the workaround of starting basket first.
I'm on kubuntu gutsy installed from tribe3 on i386

Tried to run kontact from console and get the following errors:

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.

the newest subversion build of basket, like 30 minutes ago, fixes this issue. no more crashes!!!

I had the same problem :-(

Removing basket or starting it first does not help in my case. Still both Kontact and Kmail are crashing.... I use Kmail a lot so this is very BIG problem for me to not have access to mail. Hope the problem will be fixed soon.

If Eric is right, maybe we should update our Basket package?

SergeyS: Sorry man, I never had kmail crashing, only kontact. If I ran kmail separately it worked fine. Perhaps you're having a separate issue?

Thank you for taking the time to report this bug. I confirm this bug and changing Importance to Low since there is an existing workaround - launch basket first and/or disable basket from kontact.
I'll also be adding two duplicates to this bug.

I would strongly disagree with a low priority here, as the workaround seriously limits the integration that is the very purpose of Kontact. Also, since there has been a fix mentioned, I think getting that fix into our packages should be a bit of a priority. That's just my $0.02 though.

I fully agree with Michael.

that workaround didn't work for me, so its not really a workaround if it doesn't work for everybody. plus when i went into kontact to select components, basket wasn't there to enable or disable. I stress again, that is not a valid workaround as it did not work for me.

Changing the Importance to Medium. It seems that the workaround doesn't work for everyone and seems to have affected more users that I previously thought.
Thanks.

The workaround works for me but it limits usage. Even after successfully using the workaround, kontact does not list basket so that it can be disabled.

And basket is an extremely useful application for it to be uninstalled...

I'm not sure if it's related, but I do not have basket installed, but Kontact does not want to start either. I can start kmail separately.

Steps I took before the crash:
- Click summary view: Kontact crashed
- Remove every component from summary view
- Go to summary view (no crash)
- Add components back to summary view, close Kontact
- Start Kontact: crash...

So, Kontact does not want to start anymore and I'm in the same situation as in the original bug description. Could this be related, or am I describing a completely different bug?

I think we should assign this to Jonathan Riddell because according to bug policies confirmed or triaged bugs should be assigned to someone and Jonathan is the package maintainer

Are we sure yet, this is related to basket?
I removed "kontact_specialdatesplugin" from ~/.kde/share/config/kontact_summaryrc and kontact no longer crashes.

@Alvin
No we are not sure yet, because removing the plugin from file didn't change anything for me

all I know is, kontact crashed, i updated basket, and no more crashing.

A temporarily solution is to open
/home/your_username/.kde/share/config/kontactrc

and adding the following section, if not already there, and disabling basket with the second line
[Plugins]
kontact_akregatorEnabled=true
kontact_basketpluginEnabled=false

This prevents kontact to load basket at startup. However, baskets could then not open from within kontact but you can use basket as standalone application. A little bit annoying but works for now.

Frank

On Saturday 25 Aug 2007 10:04:23 pm Eric Wheeler wrote:
> all I know is, kontact crashed, i updated basket, and no more crashing.

What do you mean "updated basket"? I do not see any available update! Anyway,
i tried reinstalling basket but that did not help. So the only thing that
works is to start basket before kontact.
--
Cheers!
kitts

On Saturday 25 Aug 2007 10:06:40 pm Frank wrote:
> A temporarily solution is to open
> /home/your_username/.kde/share/config/kontactrc
>
> and adding the following section, if not already there, and disabling
> basket with the second line [Plugins]
> kontact_akregatorEnabled=true
> kontact_basketpluginEnabled=false
>
> This prevents kontact to load basket at startup. However, baskets could
> then not open from within kontact but you can use basket as standalone
> application. A little bit annoying but works for now.

Thanks! This works for me for now.. i hope the real issue is fixed soon
though. :-)
--
Cheers!
kitts

kitts: way up above i stated that i installed the subversion build and it fixed it.

Did someone mention that this is a Gutsy exclusive problem? I am currently here at FrosCon in Germany and according to the KDE developers I talked to Kontact works fine with all other distros. I suggest to raise the importance of this bug higher than medium. Kontact is the main application I run 24h/24h, and these workarounds are poor fixes that I consider not acceptable for a PIM package. The main purpose of a PIM application IS the integration of it's various compounds.

On Sunday 26 Aug 2007 6:28:46 pm Myriam Schweingruber wrote:
> Did someone mention that this is a Gutsy exclusive problem? I am
> currently here at FrosCon in Germany and according to the KDE developers
> I talked to Kontact works fine with all other distros. I suggest to
> raise the importance of this bug higher than medium. Kontact is the main
> application I run 24h/24h, and these workarounds are poor fixes that I
> consider not acceptable for a PIM package. The main purpose of a PIM
> application IS the integration of it's various compounds.

The problem started ever since the switch to the enterprise version of
kde-pim. However, as eric mentions, basket-svn fixes the issue. I have not
tried this however.
--
Cheers!
kitts

I have to put the followig plugins on false in ~/.kde/share/config/kontactrc

kontact_korganizerpluginEnabled=true
kontact_specialdatespluginEnabled=true
kontact_todopluginEnabled=true

I can not go to the Summary without a crash if one of the above plugins are enabled.

With today's basket update 1.0.2-2build1 it is fixed.

But folk please read #135394 and #135410, respectively and please help me to confirm or solve this

Best wishes

Frank

The update basket-1.0.2-2build1 fixed it for me.

I can confirm. Kontact starts properly after installing the updated Basket package.

@Frank:
If you write "bug $ID" without the quotes and $ID replaced with the number of the bug launchpad
will create links automatically.
So it would haven been easier if you had written: bug 135394 and bug 135410.

I would also like to confirm that it works. However, IF Basket's a disabled component of Kontact, Kontact randomly crashes for me. There's really multiple situations triggering the crash, including fetching emails. But since I got Basket up, I'm not complaining.

On Wednesday 29 August 2007 13:56:19 Stefan Fleiter wrote:
> @Frank:
> If you write "bug $ID" without the quotes and $ID replaced with the number
> of the bug launchpad will create links automatically.
> So it would haven been easier if you had written: bug 135394 and bug
> 135410.
@Stefan
Thank you, I forgot always

Just confirming this bug - I was getting a crash on startup with kontact. My install came from the Tribe 3 cd and has been continuously added to and updated. I reviewed the installed packages and noticed that kdepim was not installed. After I installed that today, kontact would start and run. However I am still getting intermittent crashes. Backtrace follows - hope this helps...

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1243265344 (LWP 6329)]
[New Thread -1287353456 (LWP 6492)]
[New Thread -1278960752 (LWP 6491)]
[New Thread -1270568048 (LWP 6490)]
[New Thread -1262175344 (LWP 6489)]
0xffffe410 in ?? ()
#0 0xffffe410 in ?? ()
#1 0xbffbc7b8 in ?? ()
#2 0xb5fcbff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#3 0xbffbc7a4 in ?? ()
#4 0xb5f18eb6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#5 0xb5f18cc7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#6 0xb6d61ad9 in KCrash::startDrKonqi (argv=0xbffbe9bc, argc=17)
    at /build/buildd/kdelibs-3.5.7/./kdecore/kcrash.cpp:312
#7 0xb6d784de in KCrash::defaultCrashHandler (sig=11)
    at /build/buildd/kdelibs-3.5.7/./kdecore/kcrash.cpp:229
#8 0xffffe420 in ?? ()
#9 0x0000000b in ?? ()
#10 0xb5013901 in KMail::PopAccount::slotData (this=0x8457640, job=0x8ca36c0,
    data=@0x86b69c8)
    at /build/buildd/kdepim-3.5.7enterprise20070828/./kmail/popaccount.cpp:890
#11 0xb5018aba in KMail::PopAccount::qt_invoke (this=0x8457640, _id=8,
    _o=0xbffbef00) at ./popaccount.moc:125
#12 0xb66f3893 in QObject::activate_signal (this=0x8ca36c0, clist=0x8ca35a0,
    o=0xbffbef00) at kernel/qobject.cpp:2356
#13 0xb732a03d in KIO::TransferJob::data (this=0x8ca36c0, t0=0x8ca36c0,
    t1=@0xbffbf200) at ./jobclasses.moc:993
#14 0xb732a0b8 in KIO::TransferJob::slotData (this=0x8ca36c0,
    _data=@0xbffbf200) at /build/buildd/kdelibs-3.5.7/./kio/kio/job.cpp:933
#15 0xb7372779 in KIO::TransferJob::qt_invoke (this=0x8ca36c0, _id=18,
    _o=0xbffbeff4) at ./jobclasses.moc:1072
#16 0xb66f3893 in QObject::activate_signal (this=0x8ca2e18, clist=0x8c3a9f0,
    o=0xbffbeff4) at kernel/qobject.cpp:2356
#17 0xb732811e in KIO::SlaveInterface::data (this=0x8ca2e18, t0=@0xbffbf200)
    at ./slaveinterface.moc:194
#18 0xb738bd73 in KIO::SlaveInterface::dispatch (this=0x8ca2e18, _cmd=100,
    rawdata=@0xbffbf200)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/slaveinterface.cpp:234
#19 0xb737dcda in KIO::SlaveInterface::dispatch (this=0x8ca2e18)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/slaveinterface.cpp:173
#20 0xb733973c in KIO::Slave::gotInput (this=0x8ca2e18)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/slave.cpp:300
#21 0xb7375dd0 in KIO::Slave::qt_invoke (this=0x8ca2e18, _id=4, _o=0xbffbf328)
    at ./slave.moc:113
#22 0xb66f3893 in QObject::activate_signal (this=0x8cbf2c8, clist=0x8ca3060,
    o=0xbffbf328) at kernel/qobject.cpp:2356
#23 0xb66f41aa in QObject::activate_signal (this=0x8cbf2c8, signal=2,
    param=51) at kernel/qobject.cpp:2449
#24 0xb6a8067f in QSocketNotifier::activated (this=0x8cbf2c8, t0=51)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#25 0xb671646e in QSocketNotifier::event (this=0x8...

Thanks for report. This bug should be fixed with latest update of kdepim (3.5.7enterprise20070904-0ubuntu1). Please try new version and feel free to open new bug (or re-open) if you experience any problem with latest version.

After the update, the korganizerplugin can be enabled in the summary view. Previously, I was unable to do this without a crash. However, enabling specialdatesplugin and todoplugin still causes crashes for me.
Every plugin works separately, but going to the summary view crashes contact, so if that's the default view when starting, Kontact crashes on startup.

I've disabled all plugins except for kmail and kaddressbook. I don't have basket installed and I'm getting crashes immediately.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/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)
(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 -1243314496 (LWP 10697)]
(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)
0xffffe410 in ?? ()
#0 0xffffe410 in ?? ()
#1 0xbfe22a98 in ?? ()
#2 0xb5fbfff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#3 0xbfe22a84 in ?? ()
#4 0xb5f0ce70 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#5 0xb5f0cca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#6 0xb6d55ad9 in KCrash::startDrKonqi () from /usr/lib/libkdecore.so.4
#7 0xb6d6c4de in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4
#8 0xffffe420 in ?? ()
#9 0x0000000b in ?? ()
#10 0...

I confirm this bug too.
I've just upgraded from Feisty to Gutsy today, and after that kontact crashes on startup.
I don't think the problem is in Basket since it wasn't installed, and the problem remains after install it.
I could only open kontact after edit ~/.kde/share/config/kontactrc so that it didn't start in the summary view.
Now, i'm able to start kontact, but it crashes when i try to change to summary view, if specialdatesplugin or todoplugin are enabled, but not always...
Problems with summary view?
I've got the latest version of kdepim (3.5.7enterprise20070904-0ubuntu2).

i've been running gutsy for awhile now, and after the latest upgrades for kdepim and basket and kmail etc.. kontact works great for me.

Apparently the problem with the summary view was Bug #140500. The release of today (3.5.7enterprise20070907-0ubuntu3 ?) fixed my problem.