Bug 706612 - [abrt] claws-mail-3.7.9-2.fc14: folder_item_parent: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Summary: [abrt] claws-mail-3.7.9-2.fc14: folder_item_parent: Process /usr/bin/claws-ma...
Keywords:
Status: CLOSED DUPLICATE of bug 639314
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8886e8a3f2dc6cbf9f0402b0576...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-21 15:55 UTC by Neil Underwood
Modified: 2011-05-25 11:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-25 11:18:28 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (36.89 KB, text/plain)
2011-05-21 15:55 UTC, Neil Underwood
no flags Details

Description Neil Underwood 2011-05-21 15:55:55 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 37774 bytes
cmdline: /usr/bin/claws-mail
comment: I tried to unsubscribe from one of my Gmail IMAP folders by using the right-click context menu and Choosing Subscriptions->Unsubscribe.  I got a progress window that said "Scanning folder tree...", then Claws Mail crashed.  This was an isolated incident.  The second time it worked just fine.
component: claws-mail
Attached file: coredump, 33857536 bytes
crash_function: folder_item_parent
executable: /usr/bin/claws-mail
kernel: 2.6.35.13-91.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: 1305992923
uid: 500

How to reproduce
-----
1.  Right click on All Mail folder in Gmail Imap account
2. Select from menu Subscriptions->Unsubscribe
3.

Comment 1 Neil Underwood 2011-05-21 15:55:57 UTC
Created attachment 500195 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-05-25 11:18:28 UTC

*** This bug has been marked as a duplicate of bug 639314 ***


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