Description of problem: I did not do anything special. No plugin loading/unloading. Claws just crashed. Version-Release number of selected component: claws-mail-3.9.0-1.fc17 Additional info: backtrace_rating: 4 cmdline: /usr/bin/claws-mail crash_function: mailstream_cancel_cancelled executable: /usr/bin/claws-mail kernel: 3.7.9-104.fc17.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 mailstream_cancel_cancelled at mailstream_cancel.c:169 #1 mailstream_low_ssl_read at mailstream_ssl.c:719 #2 mailstream_low_read at mailstream_low.c:202 #3 mailstream_read at mailstream.c:246 #4 mailimap_literal_parse_progress at mailimap_parser.c:5630 #5 mailimap_string_parse_progress at mailimap_parser.c:10123 #6 mailimap_nstring_parse_progress at mailimap_parser.c:7999 #7 mailimap_msg_att_body_section_parse_progress at mailimap_parser.c:7719 #8 mailimap_msg_att_static_parse_progress at mailimap_parser.c:7906 #9 mailimap_msg_att_item_parse_progress at mailimap_parser.c:7084
Created attachment 706152 [details] File: backtrace
Created attachment 706153 [details] File: build_ids
Created attachment 706154 [details] File: cgroup
Created attachment 706155 [details] File: core_backtrace
Created attachment 706156 [details] File: dso_list
Created attachment 706157 [details] File: environ
Created attachment 706158 [details] File: limits
Created attachment 706159 [details] File: maps
Created attachment 706160 [details] File: open_fds
Created attachment 706161 [details] File: proc_pid_status
Created attachment 706162 [details] File: smolt_data
Created attachment 706163 [details] File: var_log_messages
> imap.gmail.com > #0 mailstream_cancel_cancelled (cancel=0x0) at mailstream_cancel.c:169 > cancelled = <optimized out> > ms_internal = <error reading variable ms_internal > (Cannot access memory at address 0x10)> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^ Something caused libetpan to crash, ... but with Google Mail via IMAP again, which is still a construction area.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.