Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 613428 - [abrt] crash in evolution-2.30.2-1.fc13: cfs_try_release_memory: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] crash in evolution-2.30.2-1.fc13: cfs_try_release_memory: Process /usr...
Status: CLOSED DUPLICATE of bug 629351
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-11 09:56 EDT by flashl
Modified: 2010-11-09 08:16 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 08:16:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (35.06 KB, text/plain)
2010-07-11 09:56 EDT, flashl
no flags Details

  None (edit)
Description flashl 2010-07-11 09:56:43 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
comment: Moved focus from evolution opened in different window when it crashes.
component: evolution
crash_function: cfs_try_release_memory
executable: /usr/bin/evolution
global_uuid: d7182039c447f0f5c06f3c69ae78c408947be9f7
package: evolution-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 flashl 2010-07-11 09:56:45 EDT
Created attachment 431000 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 08:16:30 EST

*** This bug has been marked as a duplicate of bug 629351 ***
Comment 3 Karel Klíč 2010-11-09 08:16:30 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 #629351.

Sorry for the inconvenience.

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