Bug 297135

Summary:	kcm_akonadi must specify host for local PostgreSQL
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Dmitry <dmitry.ashkadov>
Component:	Account Wizard	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	adam, corentin.chary, vkrause
Priority:	NOR
Version:	GIT (master)
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	kcm_akonadi: host field is empty akonadiserverrc: host setting is empty

Description Dmitry 2012-03-30 19:36:53 UTC

*** Sorry, for my bad English

Hello!

I have tried to use postgres instead of mysql. I made next:

1. I chose PostgreSQL from list
2. Check (set) "Use internal postgreSQL server"
3. Start akonadi server

But akonadi failed. PostgreSQL successfully was started, but Akonadi coudln't connect to it. Why?
Because "Host" settings was empty in akonadiserverrc.
Solution is next: kcm_akonadi must set path to socket and put it as host settings (like its behaviour in case of using local mysql server).
please see attached images.

KDE: 4.8.1

Thank you.

Comment 1 Dmitry 2012-03-30 19:37:55 UTC

Created attachment 70023 [details]
kcm_akonadi: host field is empty

Comment 2 Dmitry 2012-03-30 19:38:39 UTC

Created attachment 70024 [details]
akonadiserverrc: host setting is empty

Comment 3 Corentin Chary 2012-09-11 21:05:46 UTC

I can confirm this bug. Host should ever be set by kcm_akonadi, or should implicitly be set to the socket directory when "StartServer" is true.

The problem is that kcm_akonadi sets an empty Host, and thus the default is no more used in http://quickgit.kde.org/index.php?p=akonadi.git&a=blob&h=058ae9b24c0cf32fb93288de20c68c004eb8f7e0&hb=3a637b8d6f12ad282cac6b0822757856ed42262d&f=server%2Fsrc%2Fstorage%2Fdbconfigpostgresql.cpp

Comment 4 Corentin Chary 2012-09-11 21:08:23 UTC

CCing akonadi people working on that part of the tree in akonadi.

Comment 5 Myriam Schweingruber 2012-09-12 08:09:44 UTC

Setting status to confirmed.

Comment 6 Denis Kurz 2016-09-24 20:45:09 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 7 Denis Kurz 2017-01-07 22:11:35 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.