Bug 691864

Summary: [abrt] claws-mail-3.7.8-6.fc14: mailing_list_create_submenu: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Richard Ruhland <bugzilla.redhat>
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: 14CC: andreas.bierfert, bugs.michael, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1e7564c9f1e91b4d0c46bb6ba057824b6d3a0fe2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:06:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Richard Ruhland 2011-03-29 17:45:11 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 34674 bytes
cmdline: claws-mail
component: claws-mail
Attached file: coredump, 54738944 bytes
crash_function: mailing_list_create_submenu
executable: /usr/bin/claws-mail
kernel: 2.6.35.11-83.fc14.i686.PAE
package: claws-mail-3.7.8-6.fc14
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301420532
uid: 500

How to reproduce
-----
1. delete old mail from local Imap owner
2.
3.

Comment 1 Richard Ruhland 2011-03-29 17:45:14 UTC
Created attachment 488508 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-04-06 18:20:22 UTC
> How to reproduce
> -----
> 1. delete old mail from local Imap owner

Reproducibly? Can you reproduce it? Or did it happen just once? What "local Imap owner"? Perhaps there's a message you can reproduce this with?

Here's a polite request with regard to bug reports in general: Whenever you're asked to enter a "How to reproduce" recipe, please mention whether you are able to reproduce the problem. The availability of a test-case can be important. Please don't be too brief.

The backtrace says:

> #0  0x081465bb in mailing_list_create_submenu (mainwin=0x8583278,
> msginfo=0x859e290) at mainwindow.c:3373

The source code:

  3372          /* Mailing list post */
  3373          if (!strcmp2 (msginfo->extradata->list_post, "NO")) {
  3374                  g_free(msginfo->extradata->list_post);
  3375                  msginfo->extradata->list_post = g_strdup (_("No posting allowed"));
  3376          }

Now, strcmp2() is NULL-ptr safe. So, line 3373 can only crash if something bad has happened to the list_post pointer or the memory area it points to. Skimming over portions of the source code related to this list_post value, no obvious mistake is found. Could be that the crash is just a side-effect.

Comment 3 Fedora End Of Life 2012-08-16 12:06:07 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping