kmail crashed with SIGSEGV when importing from evolution and editing profile

[AdamReid]

Binary package hint: kdepim

The crash occurred when I was importing my .evolution folder structure using kmails import messages function. I had started the import and things seemed to be running nicely for about 5 minutes. I then realized I wasn't receiving any mail from my IMAP account, so I started to investigate the settings I had. When I clicked the edit button in the Profiles settings list the crash occurred.

I had a lot of messages in evolution, probably several thousand. When the crash occurred I got a messages saying something like "could not open file 706, too many open files"

Kubuntu Intrepid Beta + updates

kmail:
  Installed: 4:4.1.2-0ubuntu1
  Candidate: 4:4.1.2-0ubuntu1
  Version table:
 *** 4:4.1.2-0ubuntu1 0
        500 http://ca.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Disassembly: 0xb8027430:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kmail
NonfreeKernelModules: nvidia
Package: kmail 4:4.1.2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/kmail -caption KMail
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/username/bin
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdepim
Stacktrace: #0 0xb8027430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: kmail crashed with SIGSEGV
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Jonathan Thomas (echidnaman)]

Hi,
Could you see if this is still a problem with KDE 4.2? The automated bug report wasn't able to get a good crash log, so if this is still a problem we'd appreciate it if you could help us get one manually. (I can give further instructions if you are still having this crash)

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!