Bug 1301728 - [abrt] claws-mail: mailstream_close(): claws-mail killed by SIGSEGV
Summary: [abrt] claws-mail: mailstream_close(): claws-mail killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:e14ae8758564bdb17de429c6e74...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-25 20:36 UTC by Levan
Modified: 2016-12-20 18:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 18:12:16 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (67.44 KB, text/plain)
2016-01-25 20:36 UTC, Levan
no flags Details
File: cgroup (200 bytes, text/plain)
2016-01-25 20:36 UTC, Levan
no flags Details
File: core_backtrace (42.42 KB, text/plain)
2016-01-25 20:36 UTC, Levan
no flags Details
File: dso_list (23.01 KB, text/plain)
2016-01-25 20:36 UTC, Levan
no flags Details
File: environ (1.50 KB, text/plain)
2016-01-25 20:36 UTC, Levan
no flags Details
File: exploitable (82 bytes, text/plain)
2016-01-25 20:36 UTC, Levan
no flags Details
File: limits (1.29 KB, text/plain)
2016-01-25 20:37 UTC, Levan
no flags Details
File: maps (111.76 KB, text/plain)
2016-01-25 20:37 UTC, Levan
no flags Details
File: mountinfo (3.30 KB, text/plain)
2016-01-25 20:37 UTC, Levan
no flags Details
File: namespaces (85 bytes, text/plain)
2016-01-25 20:37 UTC, Levan
no flags Details
File: open_fds (1.60 KB, text/plain)
2016-01-25 20:37 UTC, Levan
no flags Details
File: proc_pid_status (1.02 KB, text/plain)
2016-01-25 20:37 UTC, Levan
no flags Details
File: var_log_messages (311 bytes, text/plain)
2016-01-25 20:37 UTC, Levan
no flags Details

Description Levan 2016-01-25 20:36:42 UTC
Description of problem:
internet conncetion was lost durning imap sync

Version-Release number of selected component:
claws-mail-3.13.1-4.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        claws-mail
crash_function: mailstream_close
executable:     /usr/bin/claws-mail
global_pid:     1133
kernel:         4.3.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 mailstream_close at mailstream.c:300
 #1 mailimap_logout at mailimap.c:776
 #2 disconnect_run at imap-thread.c:697
 #3 thread_run at etpan-thread-manager.c:340

Potential duplicate: bug 1161990

Comment 1 Levan 2016-01-25 20:36:50 UTC
Created attachment 1118186 [details]
File: backtrace

Comment 2 Levan 2016-01-25 20:36:51 UTC
Created attachment 1118188 [details]
File: cgroup

Comment 3 Levan 2016-01-25 20:36:54 UTC
Created attachment 1118189 [details]
File: core_backtrace

Comment 4 Levan 2016-01-25 20:36:56 UTC
Created attachment 1118190 [details]
File: dso_list

Comment 5 Levan 2016-01-25 20:36:57 UTC
Created attachment 1118191 [details]
File: environ

Comment 6 Levan 2016-01-25 20:36:59 UTC
Created attachment 1118192 [details]
File: exploitable

Comment 7 Levan 2016-01-25 20:37:01 UTC
Created attachment 1118193 [details]
File: limits

Comment 8 Levan 2016-01-25 20:37:03 UTC
Created attachment 1118194 [details]
File: maps

Comment 9 Levan 2016-01-25 20:37:05 UTC
Created attachment 1118195 [details]
File: mountinfo

Comment 10 Levan 2016-01-25 20:37:07 UTC
Created attachment 1118196 [details]
File: namespaces

Comment 11 Levan 2016-01-25 20:37:08 UTC
Created attachment 1118197 [details]
File: open_fds

Comment 12 Levan 2016-01-25 20:37:10 UTC
Created attachment 1118198 [details]
File: proc_pid_status

Comment 13 Levan 2016-01-25 20:37:12 UTC
Created attachment 1118199 [details]
File: var_log_messages

Comment 14 Michael Schwendt 2016-01-29 19:02:33 UTC
> internet conncetion was lost durning imap sync

Interrupting an IMAP session in Claws Mail is not 100% safe. There have been a couple of fixes last year, but it still can result in spontaneous crashes.

I think this one crashes inside libetpan, and if I remember correctly, there has been confusion about what is the culprit.

Hmmm ... while writing this and a mail to claws mail devel list, a brief search turnt up this: http://lists.claws-mail.org/pipermail/users/2015-March/012457.html

Comment 15 Fedora End Of Life 2016-11-24 15:11:39 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.

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 2016-12-20 18:12:16 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.