claws-mail crashed with SIGSEGV in IA__gtk_ctree_is_viewable()

[Graham C]

Binary package hint: claws-mail

looks similar to #202214, but occurred with claws-mail 3.3.1-1ubuntu2

ProblemType: Crash
Architecture: i386
Date: Sun Mar 23 17:46:58 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/claws-mail
NonfreeKernelModules: fglrx
Package: claws-mail 3.3.1-1ubuntu2
PackageArchitecture: i386
ProcCmdline: claws-mail
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: claws-mail
StacktraceTop:
 IA__gtk_ctree_is_viewable (ctree=0x835a178, node=0x854de90)
 IA__gtk_ctree_node_moveto (ctree=0x835a178, node=0x854de90,
 ?? ()
 ?? ()
 ?? ()
Title: claws-mail crashed with SIGSEGV in IA__gtk_ctree_is_viewable()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv plugdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__gtk_ctree_is_viewable (ctree=0x835a178, node=0x854de90)
IA__gtk_ctree_node_moveto (ctree=0x835a178, node=0x854de90, column=-1, row_align=0.5,
folderview_selected (ctree=0x835a178, row=0x854de90, column=-1, folderview=0x83e6d48)
_gtk_marshal_VOID__POINTER_INT (closure=0x84d0058, return_value=0x0, n_param_values=3,
IA__g_closure_invoke (closure=0x84d0058, return_value=0x0, n_param_values=3,

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