Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 614737 - [abrt] crash in gnochm-0.9.11-5.fc13: memcpy: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
[abrt] crash in gnochm-0.9.11-5.fc13: memcpy: Process /usr/bin/python was kil...
Status: CLOSED DUPLICATE of bug 612959
Product: Fedora
Classification: Fedora
Component: gnochm (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Haïkel Guémar
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-15 02:33 EDT by Vinh-Quang Luu
Modified: 2010-11-09 11:06 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 11:06:27 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 (67.15 KB, text/plain)
2010-07-15 02:33 EDT, Vinh-Quang Luu
no flags Details

  None (edit)
Description Vinh-Quang Luu 2010-07-15 02:33:27 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gnochm /home/glory/Desktop/English2008.chm
component: gnochm
crash_function: memcpy
executable: /usr/bin/python
global_uuid: 7d9ab1505d1491a3554b8befc958ca1f12d98946
package: gnochm-0.9.11-5.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Vinh-Quang Luu 2010-07-15 02:33:31 EDT
Created attachment 431979 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 11:06:27 EST

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

Sorry for the inconvenience.

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