Bug 192188 - Akonadi has no useful documenatation
Summary: Akonadi has no useful documenatation
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-10 01:39 UTC by Joe Christy
Modified: 2017-01-07 22:44 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 Joe Christy 2009-05-10 01:39:18 UTC
Version:           akonadi-1.1.1-6.fc10.x86_64 (using KDE 4.2.2)
OS:                Linux
Installed from:    Fedora RPMs

I'm trying to report a bug concerning kpilot's inability to sync my calendar from my Palm, but I can't find enough information about akonadi to determine if the bug is in kpilot or akonadi [cf. bug 192187].

For example, I cannot discover the name or location of the backing MySQL db, an account/password with which to access it, or a schema for the database to find how the Calendar is stored or what is actually in mine.
Comment 1 Joe Christy 2009-05-13 19:58:22 UTC
At least the answer to the question of where the config files and db are located in a user's home dir is found in the FAQ on the akonadi techbase entry: http://techbase.kde.org/Projects/PIM/Akonadi#Akonadi_FAQ.

It would be _extremely_ useful if there were a link there from the Akonadi project page: http://pim.kde.org/akonadi/
which is what comes up at the top in google (at least for me).
Comment 2 Denis Kurz 2016-09-24 20:35:44 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 3 Denis Kurz 2017-01-07 22:44:13 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.