Bug 285895 - ~/.local/share/local-mail is empty
Summary: ~/.local/share/local-mail is empty
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-06 12:34 UTC by S. Burmeister
Modified: 2017-01-07 22:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2011-11-06 12:34:40 UTC 
Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

I Kmail I have several folders within the resource "local folders". Yet ~/.local/share/local-mail, i.e. where the resource points to is completely empty.

Reproducible: Didn't try

Steps to Reproduce:
Add local folder resource and put some mails into it

Actual Results:  
~/.local/share/local-mail stays empty

Expected Results:  
all files and folders visible within kmail within "local fodlers" should be in ~/.local/share/local-mail
Comment 1 S. Burmeister 2011-11-07 10:20:37 UTC 
Found the files in ~/.local/share/.local-mail.directory/ which does make sense since these files should be in ~/.local/share/local-mail/.local-mail.directory/
Comment 2 Martin Schlander 2012-01-07 18:17:36 UTC 
The same issue is true for KJots / akonotes agent (4.7.2 on openSUSE 12.1)

In systemsettings -> Personal Information the Akonotes agent is configured to use .local/share/notes/ but in reality the notes are stored in .local/share/.notes.directory/
Comment 3 Anders Lund 2012-01-28 23:37:26 UTC 
Confirmed using kdepim 4.8.0
Comment 4 Denis Kurz 2016-09-24 20:43:54 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 5 Denis Kurz 2017-01-07 22:34:37 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.