| Summary: | Kmail startup crash, after upgrade to KDE 4.8 | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Sascha <sascha_o> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | strace kmail --nofork session | ||
|
Description
Sascha
2012-01-27 13:01:48 UTC
Created attachment 68237 [details]
strace kmail --nofork session
--- SIGABRT (Aborted) @ 0 (0) ---
rt_sigaction(SIGALRM, {SIG_DFL, [ALRM], SA_RESTORER|SA_RESTART, 0x7f90bc52a420}, {SIG_DFL, [], 0}, 8) = 0
alarm(3) = 0
write(2, "*** KMail got signal 6 (Exiting)"..., 33*** KMail got signal 6 (Exiting)
) = 33
write(2, "*** Dead letters dumped.\n", 25*** Dead letters dumped.
) = 25
sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1 \0\0\0\307\10\0\0\230\0\0\0\1\1o\0\r\0\0\0/AgentMa"..., 168}, {"\27\0\0\0akonadi_pop3_resource_0\0\0\0\0\0", 32}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 200
getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=16*1024}) = 0
close(3) = 0
close(4) = 0
close(5) = 0
[...]
close(1021) = -1 EBADF (Bad file descriptor)
close(1022) = -1 EBADF (Bad file descriptor)
close(1023) = -1 EBADF (Bad file descriptor)
write(2, "KCrash: Application 'kmail' cras"..., 40KCrash: Application 'kmail' crashing...
) = 40
write(2, "KCrash: Attempting to start /usr"..., 71KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
) = 71
apparently, all file descriptors have been consumed. I increased the limit to 16384, and then the crash would look similar, with the last line reading
close(16384) = -1 EBADF (Bad file descriptor)
May be related, the trace is full of messages like
recvmsg(3, 0x7ffffd5c88b0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)
maybe that's the reason it's running out of descriptors?
Of course, it's very annoying not being able to start my main mailer :-(
*** This bug has been marked as a duplicate of bug 280630 *** |