Bug 356518 - Akonadi wrong storage (Sqlite) configuration via UI in 4:15.08.2-ubuntu1
Summary: Akonadi wrong storage (Sqlite) configuration via UI in 4:15.08.2-ubuntu1
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: server (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-11 16:40 UTC by zx_master
Modified: 2016-01-03 17:27 UTC (History)
1 user (show)

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 zx_master 2015-12-11 16:40:13 UTC
I'm not able to switch to Sqlite data source via Akonadi configuration UI.
It does not save my settings and shows me always MySQL source when I close and reopen configuration UI.

It makes some changes in akonadiserverrc BUT it does not help - it can not start with Sqlite dataseource.

Looks like it also write wrong information in  ~/.config/akonadi/akonadiserverrc
After  I submit new settings via UI it changes file content like this:
[Debug]
Tracer=null
[%General]
Driver=QSQLITE3
[QMYSQL]
..................
[QPSQL]
.............
[SQLITE]
Name=akonadi

BUT IN ORDER TO GET IT WORK I have to alter this configuration by
removig:
[SQLITE]
Name=akonadi

And replace it with:
[QSQLITE3]
Name=/home/mylogin/.local/share/akonadi/akonadi.db

PLUS after several config updates via UI I've found multiple records in akonadiserverrc:
[%General]
Driver=QSQLITE3
[%General]
Driver=QSQLITE3


Reproducible: Always

Steps to Reproduce:
I'm use russian locale but hope that this is not related.
1. Open Akonadi server configuration
2. Switch to SQLite source
3. Close Configuration window
4. Open it again

Actual Results:  
Configuration shows me MySql as source for Akonadi

Expected Results:  
It must show me SQLite related configuration
Comment 1 Daniel Vrátil 2016-01-03 17:27:35 UTC
The UI has been removed in 15.12. We don't support switching the backends once they are set up and the UI was broken allowing this and generating invalid config files (as you found out).