claws-mail crashed with SIGSEGV in folder_item_get_msginfo_by_msgid()

[Miia Sample]

Binary package hint: claws-mail

I was flagging my mails read and the program started to get sluggish. I marked one as spam, and noted the others hadn't yet been flagged as read. At this point the program became unresponsive and eventually crashed.

ProblemType: Crash
Architecture: amd64
Date: Fri Jun 13 14:45:28 2008
DistroRelease: Ubuntu 8.04.1
ExecutablePath: /usr/bin/claws-mail
Package: claws-mail 3.3.1-1ubuntu3
PackageArchitecture: amd64
ProcCmdline: claws-mail
Signal: 11
SourcePackage: claws-mail
StacktraceTop:
 folder_item_get_msginfo_by_msgid ()
 ?? ()
 procmsg_msg_has_flagged_parent ()
 ?? ()
 procmsg_msginfo_unset_flags ()
Title: claws-mail crashed with SIGSEGV in folder_item_get_msginfo_by_msgid()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev vboxusers video

[Miia Sample (myrtti)]

The mailbox was IMAPS, I've got bogofilter installed...

[Apport retracing service (apport)]

StacktraceTop:procmsg_msg_has_flagged_parent_real (info=0x1394920, perm_flags=4,
procmsg_msg_has_flagged_parent (info=0x1394920, perm_flags=4) at procmsg.c:2037
update_folder_msg_counts (item=0xef1230, msginfo=0x3fba10141a1a1014, old_flags=2)
procmsg_msginfo_unset_flags (msginfo=0x1394920, perm_flags=3, tmp_flags=4294967295)
summary_mark_row_as_read (summaryview=0xc01c70, row=0x7fec90fe1d40)

[Dimitrios Symeonidis (azimout)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[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!