Created attachment 1150 [details] bug report
The backtrace is useless as it comes from striped binaries. Read http://www.claws-mail.org/faq/index.php/Debugging_Claws and try to provide a useful backtrace. A description of how this happened would be also appreciated.
After clicking on the button to get the new mail from the internet (removed from the server site). Mail is downloaded but unreadable because the program shutdown. gdb claws-mail Reading symbols from /usr/bin/claws-mail...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/claws-mail warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3200.4-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [New Thread 0x7fffe7be9700 (LWP 14198)] [Thread 0x7fffe7be9700 (LWP 14198) exited] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff43262aa in __strchr_sse2 () from /lib/libc.so.6 (gdb) quit A debugging session is active. Inferior 1 [process 14185] will be killed. Quit anyway? (y or n) y
downgrading severity because this only happens to you. Please attach a useful backtrace as requested in comment #1
Created attachment 1151 [details] running claws-mail in gdb
Under Archlinux, the version of claws-mail I used was 3.8.1 from pacman. The installation from archlinux AUR is wrong to (bad PKGBUILD ?? huh?). I used Installed 3.8.1cvs35 directly from claws-mail site instead: the bug disappeared.