Bug 262399 - Kontact freezes when Akonadi is not running and trying to restore from systray
Summary: Kontact freezes when Akonadi is not running and trying to restore from systray
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korgac
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-07 12:49 UTC by Thomas Richard
Modified: 2017-01-07 22:15 UTC (History)
0 users

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 Thomas Richard 2011-01-07 12:49:50 UTC
Version:           unspecified (using KDE 4.5.90) 
OS:                Linux

When Akonadi is not running for some reason, Kontact freezes for some time when i try to restore it from systray. It does that when trying to spawn korgac. 
From the console (of kontact) i get:
kontact(13921)/korganizer KPIM::ReminderClient::ReminderClient: ReminderClient::ReminderClient()

It stays there for about 30 seconds and then continues. It then works normally. 

The korgac process seems to be running but it shows an empty icon in the systray. When i kill the process and restart it, this is what i get from my console:
korgac(14086)/libakonadi Akonadi::SessionPrivate::init: ""
korgac(14086)/libakonadi Akonadi::SessionPrivate::reconnect: Akonadi Client Session: connection config file 'akonadi/akonadiconnectionrc' can not be found in "/home/thomas/.config" nor in any of ("/etc/xdg", "/etc")
korgac(14086)/libakonadi Akonadi::SessionPrivate::reconnect: connectToServer "/home/thomas/.local/share/akonadi/akonadiserver.socket"
korgac(14086)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Connection refused" 
unnamed app(14085): Communication problem with  "korgac" , it probably crashed.

It didn't actually crash and probably just hangs.


Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 21:04:37 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korgac (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:15:30 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.