Description of problem: Going offline Version-Release number of selected component: claws-mail-3.8.1-1.fc17 Additional info: libreport version: 2.0.16 abrt_version: 2.0.16 backtrace_rating: 4 cmdline: claws-mail crash_function: g_realloc kernel: 3.6.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #3 g_realloc at gmem.c:224 : #4 g_realloc_n at gmem.c:411 : #5 miSubtractNonO1 at gdkregion-generic.c:1311 : #6 miRegionOp at gdkregion-generic.c:1021 : #7 gdk_region_subtract at gdkregion-generic.c:1492 : #9 remove_child_area at gdkwindow.c:793 : #10 recompute_visible_regions_internal at gdkwindow.c:997 : #12 recompute_visible_regions at gdkwindow.c:1119 : #13 gdk_window_hide at gdkwindow.c:7234 : #14 _g_closure_invoke_va at gclosure.c:840
Created attachment 637019 [details] File: core_backtrace
Created attachment 637020 [details] File: environ
Created attachment 637021 [details] File: limits
Created attachment 637022 [details] File: backtrace
Created attachment 637023 [details] File: smolt_data
Created attachment 637024 [details] File: cgroup
Created attachment 637025 [details] File: maps
Created attachment 637026 [details] File: dso_list
Created attachment 637027 [details] File: build_ids
Created attachment 637028 [details] File: var_log_messages
Created attachment 637029 [details] File: open_fds
Created attachment 637030 [details] File: proc_pid_status
> Description of problem: > Going offline That's a very poor description, unfortunately. :-( Assumably, you've run into bug 569478 related to interrupting/stopping network while Claws Mail is busy accessing a remote folder via IMAP. I've filed that one upstream once more.
(In reply to comment #13) > That's a very poor description, unfortunately. :-( Yeah, I'm sorry, I was quite in a hurry when I did that, so I didn't pay enough attention to it. > Assumably, you've run into bug 569478 related to interrupting/stopping > network while Claws Mail is busy accessing a remote folder via IMAP. I've > filed that one upstream once more. That sounds plausible. Thank you.
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.