Bug 872520

Summary: [abrt] claws-mail-3.8.1-1.fc17: g_realloc: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Tomas 'Sheldon' Radej <tradej>
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: andreas.bierfert, bugs.michael
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6a6ad8eb9e253d6ff640a479f2b0e29e35d3068b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 18:31:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: smolt_data
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: build_ids
none
File: var_log_messages
none
File: open_fds
none
File: proc_pid_status none

Description Tomas 'Sheldon' Radej 2012-11-02 10:12:29 UTC
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

Comment 1 Tomas 'Sheldon' Radej 2012-11-02 10:12:32 UTC
Created attachment 637019 [details]
File: core_backtrace

Comment 2 Tomas 'Sheldon' Radej 2012-11-02 10:12:34 UTC
Created attachment 637020 [details]
File: environ

Comment 3 Tomas 'Sheldon' Radej 2012-11-02 10:12:36 UTC
Created attachment 637021 [details]
File: limits

Comment 4 Tomas 'Sheldon' Radej 2012-11-02 10:12:38 UTC
Created attachment 637022 [details]
File: backtrace

Comment 5 Tomas 'Sheldon' Radej 2012-11-02 10:12:40 UTC
Created attachment 637023 [details]
File: smolt_data

Comment 6 Tomas 'Sheldon' Radej 2012-11-02 10:12:42 UTC
Created attachment 637024 [details]
File: cgroup

Comment 7 Tomas 'Sheldon' Radej 2012-11-02 10:12:45 UTC
Created attachment 637025 [details]
File: maps

Comment 8 Tomas 'Sheldon' Radej 2012-11-02 10:12:47 UTC
Created attachment 637026 [details]
File: dso_list

Comment 9 Tomas 'Sheldon' Radej 2012-11-02 10:12:50 UTC
Created attachment 637027 [details]
File: build_ids

Comment 10 Tomas 'Sheldon' Radej 2012-11-02 10:12:52 UTC
Created attachment 637028 [details]
File: var_log_messages

Comment 11 Tomas 'Sheldon' Radej 2012-11-02 10:12:54 UTC
Created attachment 637029 [details]
File: open_fds

Comment 12 Tomas 'Sheldon' Radej 2012-11-02 10:12:57 UTC
Created attachment 637030 [details]
File: proc_pid_status

Comment 13 Michael Schwendt 2012-11-02 12:01:16 UTC
> 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.

Comment 14 Tomas 'Sheldon' Radej 2012-11-07 14:01:10 UTC
(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.

Comment 15 Fedora End Of Life 2013-07-03 19:41:56 UTC
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.

Comment 16 Fedora End Of Life 2013-07-31 18:31:37 UTC
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.