Today kontact will not launch, although kmail and korganizer launch perfectly well stand-alone. I'm assuming that yesterdays updates have upset something - possibly the selinux-policy changes? audit.log is showing a lot of denials and failures. Attempting to launch kontact from a terminal gives
WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 1) suspended. QDir::exists: Empty or null file name QDir::exists: Empty or null file name *** KMail got signal 11 (Crashing) [anne@david ~]$ KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kontact path = <unknown> pid = 19533
'locate QDir' merely returns to the prompt.
Anyone else seeing this? .
Anne
Anne Wilson wrote:
Hello.
Today kontact will not launch, although kmail and korganizer launch perfectly
WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 1) suspended. QDir::exists: Empty or null file name QDir::exists: Empty or null file name *** KMail got signal 11 (Crashing) [anne@david ~]$ KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kontact path = <unknown> pid = 19533
Anyone else seeing this?
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
regards Olaf
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
-- Rex
Rex Dieter wrote:
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
Basket could be selected as a component of kontact since basket version 0.6.0. See for more under http://basket.kde.org/, "What's New in 0.6.0?" -> Kontact Integration.
It costs me an long hour to find out basket as causer for the crash of kontact and it was a real nightmare.
regards Olaf
On Friday 16 February 2007, Olaf Mueller wrote:
Rex Dieter wrote:
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
Basket could be selected as a component of kontact since basket version 0.6.0. See for more under http://basket.kde.org/, "What's New in 0.6.0?" -> Kontact Integration.
It costs me an long hour to find out basket as causer for the crash of kontact and it was a real nightmare.
I tried your suggestion, but it made no difference. i still get
QDir::exists: Empty or null file name QDir::exists: Empty or null file name *** KMail got signal 11 (Crashing)
Anne
On 2/16/07, Olaf Mueller wrote:
Basket could be selected as a component of kontact since basket version 0.6.0. See for more under http://basket.kde.org/, "What's New in 0.6.0?" -> Kontact Integration.
I'm curious about whether fedora's basket can be integrated in kontact. I have seen that though I have been using basket for some months now.
Chitlesh
Chitlesh GOORAH wrote:
On 2/16/07, Olaf Mueller wrote:
Basket could be selected as a component of kontact since basket version 0.6.0. See for more under http://basket.kde.org/, "What's New in 0.6.0?" -> Kontact Integration.
I'm curious about whether fedora's basket can be integrated in kontact. I have seen that though I have been using basket for some months now.
Now, after the broken basket update (1.0-1.fc6), there's a new update for basket (1.0-2.fc6). And it seems to me this version couldn't be integrated any more in kontact.
regards Olaf
On 2/17/07, Olaf Mueller wrote:
Now, after the broken basket update (1.0-1.fc6), there's a new update for basket (1.0-2.fc6). And it seems to me this version couldn't be integrated any more in kontact.
chitlesh(~)[0]$rpm -q basket basket-1.0-2.fc6
Chitlesh
On Friday 16 February 2007 15:53, Olaf Mueller wrote:
Rex Dieter wrote:
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
Basket could be selected as a component of kontact since basket version 0.6.0. See for more under http://basket.kde.org/, "What's New in 0.6.0?" -> Kontact Integration.
It costs me an long hour to find out basket as causer for the crash of kontact and it was a real nightmare.
New info from the kde-pim list:
Matthew T. Gibbs wrote
I also had this problem, but I was able to work around by editing the file ~/.kde/share/config/kontactrc to include the line
kontact_basketpluginEnabled=false
under [Plugins].
HTH. At least it means that anyone previously using basket would not need to uninstall, while waiting for a fix.
Anne
HEllo there, fedora ships : - basket - basket-kontact
Right now if you install only basket, kontact will not crash.
But if you install basket-kontact, kontact will crash. I've filed a bug concerning this and it is an easy-fix https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231621
regards, Chitlesh
On Friday 16 February 2007, Rex Dieter wrote:
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
Rex, Olaf's 'basket' fix didn't cure it for me. How can I help troubleshoot it?
Anne
Anne Wilson wrote:
On Friday 16 February 2007, Rex Dieter wrote:
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
Rex, Olaf's 'basket' fix didn't cure it for me. How can I help troubleshoot it?
Basket is the causer of this error, see for more on the kdepim developers list. If this doesn't work for you, and 'rpm -e basket' doesn't work for you too, then nobody can help you without more information. Then your problem seems to me more complex.
regards Olaf
On Saturday 17 February 2007, Olaf Mueller wrote:
Anne Wilson wrote:
On Friday 16 February 2007, Rex Dieter wrote:
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
Rex, Olaf's 'basket' fix didn't cure it for me. How can I help troubleshoot it?
Basket is the causer of this error, see for more on the kdepim developers list. If this doesn't work for you, and 'rpm -e basket' doesn't work for you too, then nobody can help you without more information. Then your problem seems to me more complex.
Before this came up I didn't even know that basket was installed. I renamed it, so I'll try to put it back to what it was and then try an 'rpm -e' on it.
Whatever the problem is, it definitely came from that update run.
Anne
On Saturday 17 February 2007, Olaf Mueller wrote:
Anne Wilson wrote:
On Friday 16 February 2007, Rex Dieter wrote:
Olaf Mueller wrote:
Yes, and the problem was caused by a new update of basket: Feb 15 01:19:34 Updated: basket.i386 1.0-1.fc6 (/var/log/yum.log)
Delete or rename ~/.kde/share/apps/basket and ~/.kde/share/config/basketrc, that should solve the problem.
I'm curious, how does basket interact with kontact?
Rex, Olaf's 'basket' fix didn't cure it for me. How can I help troubleshoot it?
Basket is the causer of this error, see for more on the kdepim developers list. If this doesn't work for you, and 'rpm -e basket' doesn't work for you too, then nobody can help you without more information. Then your problem seems to me more complex.
To my surprise I found that the basket directory and rc file had been re-created! I've removed them altogether now, instead of renaming them, and Kontact opened without problems.
Thanks for the help
Anne
-
Anne Wilson -
Chitlesh GOORAH -
Olaf Mueller -
Rex Dieter