Bug 262992

Summary:	Launching Kontact/Kmail causes error message: no read/write permission for inbox folder
Product:	[Frameworks and Libraries] Akonadi	Reporter:	gene kodadek <gkodadek>
Component:	Migration	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	dc, null, tokoe, winter
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:	4.9.0
Sentry Crash Report:

Description gene kodadek 2011-01-12 22:44:50 UTC

Version:           2.0.89 (using KDE 4.5.95) 
OS:                Linux

I just upgraded to KDE 4.6 RC2, including KDEPIM Beta3. When I attempt to launch Kmail in KDEPIM beta 3 (either individually or by launching Kontact), I get the following error message:

Kmail encountered a fatal error and will terminate now.
The error was:
You do not have read/write permission to your inbox folder.

Simultaneously I get a separate error message box that says:

Folder /home/gene/.kde/share/apps/kmail/mail/inbox does not seem to be a valid email folder

For one thing, the specified inbox folder has the proper permissions; read/writable by me. Secondly, what would a vaild email folder look like? It's the same email directory I've been using with the previous version of Kmail.

Reproducible: Always

Steps to Reproduce:
1) Upgrade previous KDEPIM with existing Kmail account to KDEPIM 4.6 Beta 3.
2) Attempt to launch Kmail or Kontact


Actual Results:  
Error messages as described above

Expected Results:  
Kmail launches and displays my emails

Comment 1 Tobias Koenig 2011-06-04 12:17:16 UTC

Hej Gene,

the migrator has been improved a lot lately. Can you try to reproduce with a current version, please?

Ciao,
Tobias

Comment 2 Christophe Marin 2011-08-28 23:28:03 UTC

*** Bug 280115 has been marked as a duplicate of this bug. ***

Comment 3 Christophe Marin 2011-08-28 23:29:17 UTC

reopen due to bug 280115

Comment 4 dc 2011-08-29 09:31:34 UTC

On Sun, 28 Aug 2011 23:29:17 +0000 - Christophe Giboudeaux
<cgiboudeaux@gmx.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=262992
> 
> 
> Christophe Giboudeaux <cgiboudeaux@gmx.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEEDSINFO                   |UNCONFIRMED
>           Component|general                     |Migration
>             Version|2.0.89                      |4.7
>          Resolution|WAITINGFORINFO              |
>             Product|kmail2                      |Akonadi

What do you mean by "Resolution|WAITINGFORINFO" and "Status|NEEDSINFO" ?

It doesn't work at all !!!

 Kmail is dead and pop configuration can't be accessed anymore. I had
 to use an editor to stop akonadi to retrieve my mails from the
 server... and store them in a way which makes them unaccessible from
 other mailers ! A regular user would be very very upset.

 I'm not the only one with this critical bug, but we've all been forced
 to use another mailer since kmail is unusable. I'm not yieling but
 "just" a bit disapointed by the lack of action on this very serious
 problem.

Daniel

Comment 5 Rigo Wenning 2011-09-04 17:13:07 UTC

I found the following:
http://forum.kde.org/viewtopic.php?f=20&t=90197
**************** FIXED **************

The problem was Akonadi. It was looking for a non-existent mailbox.

SOLUTION:
Use text entry box on the start menu to type akonadi
Select Akonadi Console 
Select Kmail Folders, configure natively

The application was looking for current in /home/jim/.kde4/share/apps/kmail/mail/ but they only exist at the next level ie 
/home/jim/.kde4/share/apps/kmail/mail/Web stuff. 
Changed to point to a random sub-folder and now fully functional.

That's why kmail always crashed with "KMail encountered a fatal error and will terminate now. The error was: Failed to fetch the resource collection."

Comment 6 Unknown 2012-06-25 13:56:58 UTC

This bug is now fixed. Look at release KDE 4.9 and https://bugs.kde.org/show_bug.cgi?id=124111