Bug#449118: kmail: several errors, segfault and crashes
Am Samstag 03 November 2007 schrieb Kevin Krammer:
> On Saturday 03 November 2007, Hans wrote:
> > 1. The folder "trash" can not be deleted. It seems, the mails are
> > deleted, but they are NOT. The size of the file ~/Mail/trash should be
> > set to zero with an empty trash, but it is NOT. The mails are staying in
> > this folder. Besides this, this is also a security problem, as mails will
> > never be securely deleted (and other persons might take a look at it)
>
> Is the trash folder of type "mbox"?
> If yes, compact it (in German "Ordner komprimieren")
Hi Kevin,
the folders are in "maildir" format.
>
> > 2. The content of the "sent-mail" folder can not be deleted. The same
> > behavior as desribed above, with one exception:
>
> Do you mean it can't be deleted as in the mails are still visible in KMail
> or that they are still on disk?
>
The LAST Mail is still visible. I can see, that it tries to delete the mail
(there is a line through the text) , but it will not be deleted. The mails
stay in the file ~/Mail/sent-mail, too.
> > When trying to push the LAST(!) Mail into the trash, kmail crashes with
> > segfault.
>
> This is definitely a bug.
> Does this also happen if you do "Move all messages to trash" from the
> folder's context menu?
>
Yes, it does.
> > 3. The content of folder "drafts" are no more shown, although it is still
> > existing in ~/Mail/drafts.
>
> Hmm.
> While KMail is not running, remove the .drafts.index file from the mail
> directory and then restart KMail. Does this help?
>
No, I tried this, too. Also forcing to rebuild a new index will not help.
To force it, I deleted some lines in the "trash" file. Kmail remarks it, and
built a new index, but no success. All mails appeared again, but could not
deleted as described above.
> > 4. Please check: I suppose, the access-rights are not set correctly by
> > default ( I never changed them manually). ~/Mail/outbox, ~/Mail/sentmail
> > and ~/Mail/trash got 0600, but ~/Mail/drafts got 0644.
>
> I think 0600 is the correct one, though I also have one with 0644. My guess
> is that this folder has been created at a time where there has probably
> been a bug in kdelibs or somewhere else which resulted in those access
> flags.
>
> Cheers,
> Kevin
I hope, this will help. IMO there is definately a bug, which might be
responsible for all described behaviours.
Regards
Hans-J. Ullrich
Reply to: