Bug 128259 - kmail "no subject" no text, no date etc.
Summary: kmail "no subject" no text, no date etc.
Status: RESOLVED DUPLICATE of bug 122028
Alias: None
Product: kmail
Classification: Applications
Component: index (show other bugs)
Version: 1.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Molkentin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-29 18:49 UTC by Richard Moore
Modified: 2007-07-17 15:34 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 Richard Moore 2006-05-29 18:49:24 UTC
Version:           1.2 (using KDE 3.5.1 Level "a" , SUSE 10.1)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.13-4-default

I copied my .kde folder to another computer prior to doing a new install of OpenSuSE 10.1 (overwriting OpenSuSE 10.0).

When I transferred the .kde... kmail .... mail folder back to the original computer I have all my emails but there is no content for any of them.  They all have 'no subject' no text, no date or any other details.

How can I get them back?  How do I avoid this problem in the future?  It would be really good to have a simple back-up arrangement inbuilt to kmail - like The Bat does in Windows.
Comment 1 Thiago Macieira 2006-06-04 10:51:35 UTC
The backup mechanism is going to be provided by a different application.

Try removing/moving all the *.index files.
Comment 2 Richard Moore 2006-06-08 16:27:32 UTC
This doesn't work.

Why are these folders so difficult?  I can copy folders for Thunderbird very 
easily, which means that I can reliably back-up even if it isn't easy.

Thanks for your response.

Richard

On Sunday 04 June 2006 09:51, Thiago Macieira wrote:
[bugs.kde.org quoted mail]
Comment 3 Thiago Macieira 2006-06-08 23:36:57 UTC
It isn't.

I copied my ~/.kde/share/apps/kmail from one computer to another, and then from that another to a third one two months later. All is working fine.

Your case probably indicates that the folders had a corruption in the first place.
Comment 4 Richard Moore 2006-06-09 15:29:24 UTC
They weren't corrupted when I backed them up.  Is a backup solution to be available shortly?

Richard Moore
National Development Consultant
Health and Social Care Advisory Service
11-13 Cavendish Square
LONDON W1G 0AN
 
Office:   020 7307-2898 

Mobile:  07973 234496

Home Office:  0141 416 0496

On Thu Jun  8 21:36 , Thiago Macieira <thiago@kde.org> sent:

[bugs.kde.org quoted mail]
later. All is working fine.
>
>Your case probably indicates that the folders had a corruption in the first place.




Comment 5 Richard Moore 2006-06-12 16:40:24 UTC
Sorry to keep pestering you Thiago.

At the weekend I tried to bring the copied email folder up on a different 
computer.

I realised two things which may or may not be significant.

First, the email folders were KMail 3.5.2, but when I upgraded my SuSE to 10.1 
the installed Kmail  would be 3.5.1 - I guess this wouldn't make a 
difference.

Second, when I tried to open Kmail on the new computer I got the message 
'Kontact already seems to be running' although it wasn't.  I had thismessage 
when I upgraded and encountered the problem I wrote about.

I haven't opened Kontact on the second machine - is there a file which is 
telling KDE that Kontact is open even though it isn't?  If so, can I amend 
this?

Thank you for your help.

Richard

On Thursday 08 June 2006 22:36, Thiago Macieira wrote:
[bugs.kde.org quoted mail]
Comment 6 Thiago Macieira 2006-06-13 00:02:02 UTC
> is there a file which is telling KDE that Kontact is open even though it
> isn't? 

You probably copied your .kde while it was running, so you copied the lock file too.

It's ~/.kde/share/apps/kmail/lock
Comment 7 Chris Gow 2006-10-28 23:17:50 UTC
Richard,

Has this problem been fixed/resolved? If so, can you mark this bug as WORKSFORME
Comment 8 Thomas McGuire 2007-07-17 15:34:15 UTC
Already reported, see bug 122028 and bug 122028.

*** This bug has been marked as a duplicate of 122028 ***