Bug 1000152 - Python get segmentation fault, core dumped running Brainworkshop
Python get segmentation fault, core dumped running Brainworkshop
Product: Fedora
Classification: Fedora
Component: python (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Bohuslav "Slavek" Kabrda
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-08-22 16:07 EDT by Peter H. Jones
Modified: 2013-08-23 02:25 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-23 02:25:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Standard output (89 bytes, text/plain)
2013-08-22 16:07 EDT, Peter H. Jones
no flags Details
Standard error (36.79 KB, text/plain)
2013-08-22 16:08 EDT, Peter H. Jones
no flags Details

  None (edit)
Description Peter H. Jones 2013-08-22 16:07:31 EDT
Created attachment 789342 [details]
Standard output

Description of problem:
python -v brainworkshop.pyw 2>two 1>one 

gives Segmentation fault (core dumped)

Version-Release number of selected component (if applicable):

How reproducible:
Almost every time.

Steps to Reproduce:
1. Download from
2. unzip downloaded file brainworkshop-4.8.4.zip
3. python -v brainworkshop.pyw 2>two 1>one 
4. Use ESC to exit from screen with image of brain displayed.

Actual results:
Segmentation fault (core dumped)

Expected results:
Normal running.

Additional info:
The software dates from 2010 and may be obsolete or no longer be
supported. I have emailed the author/maintainer to see if this is the
case. However, faulty python code that doesn't seem to link to other modules (in C or C++) should not cause a dump.

I also note the Segmentation Fault message does not appear in the starndard error file.
Comment 1 Peter H. Jones 2013-08-22 16:08:50 EDT
Created attachment 789343 [details]
Standard error
Comment 2 Bohuslav "Slavek" Kabrda 2013-08-23 02:25:23 EDT
I don't see how this could be Python's error. The message

AL lib: (EE) alc_cleanup: 1 device not closed

is caused by not cleaning up audio handles properly. This may be result of wrong ctypes usage in pyglet/media/drivers/openal/lib_* (in the sense that there is no deallocation/deinitialization code.
I can't help you here, sorry. I'm closing as cantfix - if you still think that the error is in Python after communication with upstream, feel free to reopen this bug.

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