Bug 249683

Summary:	Apparently, disabling the wrong module renders Kontact unresponsive. Requires killing.
Product:	[Applications] kontact	Reporter:	Borden <borden_c>
Component:	summary	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	quazgar
Priority:	NOR
Version:	4.4.5
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	kontactrc, with the [Plugin] section added in

Description Borden 2010-09-01 01:03:33 UTC

Version:           4.4.5 (using KDE 4.4.5) 
OS:                Linux

Today I closed Kontact with the Summary view open.  When I try to reopen Kontact, the Tip of the Day popup appears but it is completely unresponsive.  Clicking anywhere in Kontact or TotD does nothing.  When I go to close the TotD window, after a few seconds, KDE reports that TotD is not responding (no kidding) and recommends that I terminate the application Kontact, which gives me my computer back but keeps me safely out of Kontact.  The whole system does not hang and rebooting does not fix the problem.

This did not happen earlier today (or earlier period) when Kontact went directly into KMail, KOrganiser or Akregator or any other module, which is why I'm reporting it against Summary.  I am still able to access the individual components of Kontact (which generate their own TotD) without problem.

Reproducible: Always

Steps to Reproduce:
1. Close Kontact with the Summary view open (presuming that it'll reopen Kontact at the Summary view).  Make sure that TotD is enabled.
2. Open Kontact.
3. Let the insanity begin.

Comment 1 Borden 2010-09-01 01:04:26 UTC

Sorry, I should add that I'm using a fully-updated version of Debian Squeeze.

Comment 2 Kai Uwe Broulik 2010-09-02 15:08:56 UTC

Those tip of the day features should be banned altogether, they are just annoying, ok, sometimes there are a few good tips inside but that doesn‘t justify annoying the user all the time, especially at first launch. This is Windows 95 aera, not 2010.

Comment 3 Borden 2010-09-07 05:43:32 UTC

I personally have nothing against them although the point is that a freakin' popup shouldn't bring Kontact to its knees!

Comment 4 Borden 2010-09-11 02:18:40 UTC

My initial assessment was incorrect.  The problem is not with the Tip of the Day.  Through a cumbersome, undocumented process, I eventually figured out that adding

[TipOfDay]
RunOnStart=false

to my ~/.kde/share/config/kontactrc file could disable TotD but I was still left with an unresponsive Kontact which required force closing.  I noticed when I started Kontact through bash that it spat out this line:

<unknown program name>(4313)/ main: Unknown resource type:  "notes" 

now leading me to believe that having disabled the KNotes module earlier has krashed Kontact because it can't find this module and, in a reasonable manner, now hangs instead of employing some intelligent exception handling.

Since Kontact is *totally* unresponsive and clicking on anything does *nothing* can someone suggest how to re-enable the KNotes module through rc files?  If I can do this, then I can appropriately report a bug in how Kontact does not handle module disabling correctly.

Comment 5 Christophe Marin 2010-09-20 00:09:00 UTC

(In reply to comment #4)

> can someone suggest how to re-enable the KNotes module through rc files?  

edit .kde/share/config/kontactrc and look in the [Plugins] section

make sure you have kontact_knotespluginEnabled=true 

save and start kontact

Comment 6 Borden 2010-09-25 22:34:20 UTC

Created attachment 51991 [details]
kontactrc, with the [Plugin] section added in

Comment 7 Borden 2010-09-25 22:39:17 UTC

Thank you but, unfortunately, that fix didn't work.  I'm attaching my kontactrc file and here's the output when I try to run kontact from bash:

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kontact(8125) KMKernel::recoverDeadLetters: Unable to open autosave file "1273281827.2894.eTuRq" 
kontact(8125) KMKernel::recoverDeadLetters: Unable to open autosave file "1274422111.5984.OJ2XJ" 
kontact(8125)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kontact(8125)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kontact(8125)/kdeui (kdelibs): No such XML file "/home/me/.kde/share/apps/kontact/local-kmail.rc" 
kontact(8125)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kontact(8125)/kdeui (kdelibs): No such XML file "/home/me/.kde/share/apps/kontact/local-calendar.rc" 
kontact(8125)/kdeui (kdelibs): No such XML file "/home/me/.kde/share/apps/kontact/local-todo.rc" 
<unknown program name>(8149)/ main: Unknown resource type:  "notes" 
kontact(8125)/kdeui (kdelibs): No such XML file "/home/me/.kde/share/apps/kontact/local-.rc" 
kontact(8125)/kdeui (kdelibs): No such XML file "/home/me/.kde/share/apps/kontact/default-.rc"

Comment 8 quazgar 2011-02-20 20:02:41 UTC

Possibly a duplicate of bug #226292?

Comment 9 Borden 2011-03-13 18:04:30 UTC

I'm not sure.  I tried reproducing the bug on a fresh install of Debian Wheezy and couldn't.  Perhaps the problem has been fixed?  Anyway, close for now and if it gives me any trouble in the future I'll report.

Thanks :)