From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kdepim-4.6.0 woes
Date: Wed, 22 Jun 2011 13:56:39 +0100 [thread overview]
Message-ID: <201106221356.50300.michaelkintzios@gmail.com> (raw)
In-Reply-To: <2259486.maH7REsZTc@nazgul>
[-- Attachment #1: Type: Text/Plain, Size: 1944 bytes --]
On Wednesday 22 Jun 2011 13:16:05 you wrote:
> On Wednesday 22 June 2011 13:05:31 Mick did opine thusly:
> > Anyway, I noticed that a KDE machine which is using MySQL as a
> > backend for Akonadi is not showing any contacts in its address
> > book. All other boxen use sqlite3 instead and they do not seem to
> > have any noticeable problems.
> >
> > Could this be a MySQL issue?
> >
> > PS. All of these PCs run stable KDE.
>
> A while ago I eventually got my contacts back. I forget the actual
> cause now, but I strongly suspect it involved tinkering with mysql,
> and this may have broken in turn my calendar.
>
> I'm going to do one last test before consigning kdepim to the
> trashbin: migrate everything to a new user and start with a default
> config. If it works, I can migrate the data at my leisure.
>
> But now, stupid question incoming:
>
> How you you get akonadi to use sqlite as the backend? There's no, erm,
> gui tickbox for that.
Yes, that's right, no GUI box to tick because the KDE devs did not like to
support sqlite (some of the things they wanted to do were not straight forward
under sqlite).
The way I did it was to set it up manually in
~/.config/akonadi/akonadiserverrc. This old thread describes how I went about
it:
http://article.gmane.org/gmane.linux.gentoo.user/224044
This is what my akonadiserverrc looks like today:
================================================
[%General]
Driver=QSQLITE
SizeThreshold=4096
ExternalPayload=false
[QSQLITE]
Name=/home/michael/.local/share/akonadi/akonadi.db
Host=
User=
Password=
Options=
StartServer=false
[Debug]
Tracer=null
================================================
No MYSQL section in there at all.
However, I must issue a Health Warning here. I never had mysql on this
machine and did not have to migrate my PIM resources from mysql to sqlite. So
YMMV.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-22 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 23:40 [gentoo-user] kdepim-4.6.0 woes Alan McKinnon
2011-06-21 6:12 ` Mick
2011-06-21 19:19 ` Michael Schreckenbauer
2011-06-21 17:28 ` Alex Schuster
2011-06-21 19:16 ` Michael Schreckenbauer
2011-06-22 7:26 ` Alan McKinnon
2011-06-22 12:05 ` Mick
2011-06-22 12:16 ` Alan McKinnon
2011-06-22 12:56 ` Mick [this message]
2011-06-22 13:14 ` Dale
2011-06-22 15:32 ` Alan McKinnon
2011-06-22 14:36 ` Alan McKinnon
2011-06-22 15:23 ` Indi
2011-06-22 15:37 ` Alan McKinnon
2011-06-22 16:24 ` Indi
2011-06-22 15:44 ` Dale
2011-06-22 16:02 ` Alan McKinnon
2011-06-23 8:22 ` Joost Roeleveld
2011-06-23 10:53 ` Dale
2011-06-23 11:36 ` Joost Roeleveld
2011-06-23 20:12 ` Alan McKinnon
2011-06-23 20:03 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201106221356.50300.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox