Bug 1011643 - [abrt] claws-mail-3.9.2-3.fc18: matcherlist_match: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Summary: [abrt] claws-mail-3.9.2-3.fc18: matcherlist_match: Process /usr/bin/claws-mai...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:07cf0c5842626ade9f935f0a90a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 17:21 UTC by Tim Flink
Modified: 2014-02-05 22:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:25:03 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (74.62 KB, text/plain)
2013-09-24 17:21 UTC, Tim Flink
no flags Details
File: cgroup (129 bytes, text/plain)
2013-09-24 17:21 UTC, Tim Flink
no flags Details
File: core_backtrace (15.60 KB, text/plain)
2013-09-24 17:21 UTC, Tim Flink
no flags Details
File: dso_list (15.41 KB, text/plain)
2013-09-24 17:21 UTC, Tim Flink
no flags Details
File: environ (1.67 KB, text/plain)
2013-09-24 17:22 UTC, Tim Flink
no flags Details
File: exploitable (82 bytes, text/plain)
2013-09-24 17:22 UTC, Tim Flink
no flags Details
File: limits (1.29 KB, text/plain)
2013-09-24 17:22 UTC, Tim Flink
no flags Details
File: maps (90.48 KB, text/plain)
2013-09-24 17:22 UTC, Tim Flink
no flags Details
File: open_fds (1.38 KB, text/plain)
2013-09-24 17:22 UTC, Tim Flink
no flags Details
File: proc_pid_status (943 bytes, text/plain)
2013-09-24 17:22 UTC, Tim Flink
no flags Details
File: var_log_messages (733 bytes, text/plain)
2013-09-24 17:22 UTC, Tim Flink
no flags Details

Description Tim Flink 2013-09-24 17:21:45 UTC
Description of problem:
I had just sent a gpg signed mail and claws crashed. it appears that the mail was sent, though

Version-Release number of selected component:
claws-mail-3.9.2-3.fc18

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        claws-mail
crash_function: matcherlist_match
executable:     /usr/bin/claws-mail
kernel:         3.10.11-100.fc18.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 matcherlist_match at matcher.c:1809
 #1 folder_item_search_msgs_local at folder.c:4805
 #2 search_msgs at imap.c:2272
 #3 folder_item_search_msgs at folder.c:4748
 #4 search_filter_folder at advsearch.c:472
 #6 search_impl at advsearch.c:515
 #7 advsearch_search_msgs_in_folders at advsearch.c:124
 #8 quicksearch_run_on_folder at quicksearch.c:172
 #9 summary_show at summaryview.c:1373
 #10 folderview_selected at folderview.c:2221

Comment 1 Tim Flink 2013-09-24 17:21:49 UTC
Created attachment 802362 [details]
File: backtrace

Comment 2 Tim Flink 2013-09-24 17:21:52 UTC
Created attachment 802363 [details]
File: cgroup

Comment 3 Tim Flink 2013-09-24 17:21:55 UTC
Created attachment 802364 [details]
File: core_backtrace

Comment 4 Tim Flink 2013-09-24 17:21:57 UTC
Created attachment 802365 [details]
File: dso_list

Comment 5 Tim Flink 2013-09-24 17:22:00 UTC
Created attachment 802366 [details]
File: environ

Comment 6 Tim Flink 2013-09-24 17:22:02 UTC
Created attachment 802367 [details]
File: exploitable

Comment 7 Tim Flink 2013-09-24 17:22:05 UTC
Created attachment 802368 [details]
File: limits

Comment 8 Tim Flink 2013-09-24 17:22:08 UTC
Created attachment 802369 [details]
File: maps

Comment 9 Tim Flink 2013-09-24 17:22:10 UTC
Created attachment 802370 [details]
File: open_fds

Comment 10 Tim Flink 2013-09-24 17:22:12 UTC
Created attachment 802371 [details]
File: proc_pid_status

Comment 11 Tim Flink 2013-09-24 17:22:15 UTC
Created attachment 802372 [details]
File: var_log_messages

Comment 12 Michael Schwendt 2013-09-24 18:58:23 UTC
> I had just sent a gpg signed mail and claws crashed.
> it appears that the mail was sent, though

The stacktrace is related to using "Quicksearch" and an IMAP folder.

> #0  matcherlist_match (matchers=matchers@entry=0xb097fe0, 
> info=info@entry=0x847d360) at matcher.c:1809
>        matcher = <optimized out>
>        l = 0x21

The address of the l pointer here looks broken.

Comment 13 Fedora End Of Life 2013-12-21 14:37:09 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 14 Fedora End Of Life 2014-02-05 22:25:03 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.