Bug 615539 - [abrt] crash in Mayavi-3.3.0-1.fc13: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in Mayavi-3.3.0-1.fc13: Process /usr/bin/python was killed by si...
Status: CLOSED DUPLICATE of bug 623636
Alias: None
Product: Fedora
Classification: Fedora
Component: Mayavi   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Rakesh Pandit
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:3d7855393e722513c800550a4e5...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-17 00:43 UTC by Phil V
Modified: 2010-08-14 10:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-14 10:21:51 UTC
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 (105.23 KB, text/plain)
2010-07-17 00:43 UTC, Phil V
no flags Details

Description Phil V 2010-07-17 00:43:37 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/mayavi2
comment: segmentation fault 100% guaranteed.
component: Mayavi
executable: /usr/bin/python
global_uuid: 3d7855393e722513c800550a4e572a44ce7f08d4
package: Mayavi-3.3.0-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1. /usr/bin/python /usr/bin/mayavi2

$ /usr/bin/python /usr/bin/mayavi2
Warning: Unable to import the wx backend for pyface due to traceback: Traceback (most recent call last):
	  File "/usr/lib/python2.6/site-packages/enthought/pyface/toolkit.py", line 40, in _init_toolkit
	    __import__(be + 'init')
	ImportError: No module named wx.init

Segmentation fault (core dumped)

Comment 1 Phil V 2010-07-17 00:43:39 UTC
Created attachment 432525 [details]
File: backtrace

Comment 2 Chen Lei 2010-08-14 10:21:51 UTC

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

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