Bug 710390

Summary: [abrt] claws-mail-3.7.9-2.fc14: folder_get_identifier: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David Kovalsky <dkovalsk>
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: andreas.bierfert, audit.art, benl, bugs.michael, tomspur
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2447
Whiteboard: abrt_hash:92230f0a0769b728fdf7f60b71954fff48acdd1d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:07:17 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 David Kovalsky 2011-06-03 10:02:36 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 28980 bytes
cmdline: claws-mail
comment: It's nothing that I haven't done thousand of times in the past. This is not reproducible. The system is clean, did a fresh boot this morning. I'm running with the latest and greatest from updates-testing on F14.
component: claws-mail
Attached file: coredump, 2337415168 bytes
crash_function: folder_get_identifier
executable: /usr/bin/claws-mail
kernel: 2.6.35.13-92.fc14.x86_64
package: claws-mail-3.7.9-2.fc14
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1307094941
uid: 10625

How to reproduce
-----
1. This is weird, I did nothing special. I was in the middle of replying to an e-mail. I switched to check something out in Firefox, then back to claws (on different desktop), entered a char, realized that I have an US keyboard, switched to a Czech one (keyboard shortcut), then entered 2 or 3 chars. 
2. Claws froze for a second and then crashed (or the process of crashing may take a while)

Comment 1 David Kovalsky 2011-06-03 10:02:40 UTC
Created attachment 502771 [details]
File: backtrace

Comment 2 David Kovalsky 2011-06-03 10:08:55 UTC
Ha - one more thing that might be related. 

If I recall the last events before the crash correctly, I did: 

- I wanted to reply to an e-mail which was in a subfolder INBOX/foo/bar
- I started typing a reply, but got interrupted. When I came back, I moved the "bar" subfolder under a different tree (like INBOX/baz/bar). Then got interrupted again, switched to FF, checked something out, back to claws and try finish the reply. Then it crashed. So perhaps moving a folder which contains the email one is replying to may crash claws (?)

I still seems odd to me, because I'm shuffling folder around on IMAP all the time and this is the first time I see this. Maybe this was the first time I had a compose window open in the middle of shuffling.

Comment 3 Michael Schwendt 2011-06-03 10:57:33 UTC
Confirmed.

Moving the folder that is currently being replied to crashes the compose window:
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2447

#0  folder_get_identifier (folder=0x17c0000017b) at folder.c:1362
        type_str = <error reading variable type_str (Cannot access memory at address 0x17c0000017b)>
#1  0x00000000004b40f9 in folder_item_get_identifier (item=0x133f220) at folder.c:1376
        id = 0x0
        folder_id = 0x0
#2  0x00000000004913ed in compose_draft (data=0x555d400, action=2) at compose.c:9447
[...]

Comment 4 Michael Schwendt 2011-06-29 21:16:37 UTC
*** Bug 717791 has been marked as a duplicate of this bug. ***

Comment 5 Fedora End Of Life 2012-08-16 12:07:20 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

Comment 6 Michael Schwendt 2014-05-22 20:51:02 UTC
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2447#c7
(2014-05-22 22:13:03 CEST)