Bug 588768 - [abrt] crash in evolution-2.30.1-2.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] crash in evolution-2.30.1-2.fc13: raise: Process /usr/bin/evolution wa...
Status: CLOSED DUPLICATE of bug 610912
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
abrt_hash:530f8aaacff84b236bfa16195eb...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-04 09:30 EDT by drewskiwooskie
Modified: 2010-11-08 12:26 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-08 12:26:04 EST
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 (36.79 KB, text/plain)
2010-05-04 09:30 EDT, drewskiwooskie
no flags Details

  None (edit)
Description drewskiwooskie 2010-05-04 09:30:08 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: as stated, i just entered in information into the to/cc and the subject, when I tried to click or tab into the Body when creating a new email. I unchecked sync with pidgin and it has not crashed since
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 530f8aaacff84b236bfa16195ebc719f4880320a
kernel: 2.6.33.3-72.fc13.x86_64
package: evolution-2.30.1-2.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.enter in addresses manually in to, cc when creating a new email
2.type in subject
3.try to tab or click in body
Comment 1 drewskiwooskie 2010-05-04 09:30:10 EDT
Created attachment 411295 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 12:26:04 EST

*** This bug has been marked as a duplicate of bug 610912 ***
Comment 3 Karel Klíč 2010-11-08 12:26:04 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #610912.

Sorry for the inconvenience.

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