From: Norberto Bensa <norberto+linux-kernel@bensa.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.6 breaks kmail (nfs related?)
Date: Mon, 17 May 2004 03:35:42 -0300 [thread overview]
Message-ID: <200405170335.42754.norberto+linux-kernel@bensa.ath.cx> (raw)
In-Reply-To: <200405131411.52336.amann@physik.tu-berlin.de>
Andreas Amann wrote:
> kmail: Error: Could not add message to folder (No space left on device?)
> kmail: WARNING: KMail encountered a fatal error and will terminate now.
> The error was:
> KMFolderMaildir::addMsg: abnormally terminating to prevent data loss.
> ...
Well, I'm getting this with kcalc after upgrading to 2.6.6-mm3:
$ kcalc
KCrash: Application 'kcalc' crashing...
strace shows lots of
...
close(1002) = -1 EBADF (Bad file descriptor)
close(1003) = -1 EBADF (Bad file descriptor)
close(1004) = -1 EBADF (Bad file descriptor)
close(1005) = -1 EBADF (Bad file descriptor)
...
Now it's late. More tests and info tomorrow (unless there's a new -mm kernel
which fixes this :-) )
Regards,
Norberto
next prev parent reply other threads:[~2004-05-17 6:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 12:11 2.6.6 breaks kmail (nfs related?) Andreas Amann
2004-05-16 4:46 ` Linus Torvalds
2004-05-16 17:59 ` Trond Myklebust
2004-05-16 18:10 ` Trond Myklebust
2004-05-16 18:19 ` Linus Torvalds
2004-05-16 18:47 ` Trond Myklebust
2004-05-16 18:50 ` Linus Torvalds
2004-05-16 19:10 ` Trond Myklebust
2004-05-17 11:31 ` Andreas Amann
2004-05-17 15:55 ` Trond Myklebust
2004-05-21 15:27 ` Andreas Amann
2004-05-21 16:40 ` Trond Myklebust
2004-05-21 23:05 ` Andreas Amann
2004-05-22 3:40 ` J. Bruce Fields
2004-05-17 21:35 ` Matthias Urlichs
2004-05-17 6:35 ` Norberto Bensa [this message]
2004-05-17 7:14 ` Andrew Morton
2004-05-17 17:35 ` Andrew Morton
2004-05-17 18:01 ` Trond Myklebust
2004-05-17 16:17 ` Frank van Maarseveen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200405170335.42754.norberto+linux-kernel@bensa.ath.cx \
--to=norberto+linux-kernel@bensa.ath.cx \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox