Bug 597743 - [abrt] crash in claws-mail-3.7.6-1.fc13: in invoke_hook_cb at log.c:76
Summary: [abrt] crash in claws-mail-3.7.6-1.fc13: in invoke_hook_cb at log.c:76
Status: CLOSED DUPLICATE of bug 598132
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:695bc9b7a46bcdceddfcfdf56f5...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-30 10:39 UTC by Jaroslaw Gorny
Modified: 2010-11-12 15:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-12 15:00:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (22.27 KB, text/plain)
2010-05-30 10:39 UTC, Jaroslaw Gorny 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Jaroslaw Gorny 2010-05-30 10:39:18 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: claws-mail
comment: Standard claw-mail configuration with one account configured (IMAP). I have automatic checking of new mail enabled (however I'm not sure if the crash happened during fetching new e-mails or it 'just happened').
component: claws-mail
crash_function: raise
executable: /usr/bin/claws-mail
global_uuid: 695bc9b7a46bcdceddfcfdf56f530c06bb9f3908
kernel: 2.6.33.4-95.fc13.i686
package: claws-mail-3.7.6-1.fc13
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Run claws-mail
2. Wait until it crash
Comment 1 Jaroslaw Gorny 2010-05-30 10:39:21 UTC 
Created attachment 418005 [details]
File: backtrace
Comment 2 Michael Schwendt 2010-11-12 15:00:27 UTC 

*** This bug has been marked as a duplicate of bug 598132 ***
Note You need to log in before you can comment on or make changes to this bug.