Bug 529559

Summary: scidavis segmentation fault on startup when Python as a scripting language is used
Product: [Fedora] Fedora Reporter: Jacek Pawlyta <cunio>
Component: scidavisAssignee: Chen Lei <supercyper1>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 12CC: cunio, eric.tanguy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: scidavis-0.2.4-1.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-14 13:36:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jacek Pawlyta 2009-10-18 17:00:51 UTC
Description of problem:


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

scidavis-0.2.3-7.fc11.x86_64
python-2.6-9.fc11.x86_64

How reproducible:
Always

Steps to Reproduce:
1. start SciDAVis on a fresh user account
2. change scripting language to from muParser to Python in SciDAVis preferences 
3. close SciDAVis
4. run SciDAVis
  
Actual results:
Segmentation fault

Expected results:
running SciDaVis

to "FIX" this one has to manually change:
ScriptingLang=Python
to
ScriptingLang=muParser
in ~/.config/.config/SciDAVis/SciDAVis.conf

Additional info:
part of ltrace scidavis output:

strcmp("Python", "muParser")                                                                                    = -1                                                      
strcmp("Python", "Python")                                                                                      = 0                                                       
_Znwm(64, 0x72d872, 0x11cec01, 0xffffffff, 0x142fea0)                                                           = 0x1210c80                                               
_ZN7QObjectC2EPS_PKc(0x1210c80, 0, 0x72d86b, 0x1210c70, 64)                                                     = 0x145c110                                               
Py_IsInitialized(0x146bd40, 0x7fffceb50130, 0x72d801, 0x145c136, 0xffffffbf)                                    = 0                                                       
Py_Initialize(0x146bd40, 0x7fffceb50130, 0x72d801, 0x145c136, 0xffffffbf)                                       = 25                                                      
Py_IsInitialized(0x159a3ea, 0x11104f6, 0xa69a10, 0x382d46, 0xfffffffffeeefb10)                                  = 1                                                       
Py_InitModule4_64(0x733acc, 0xa6ac60, 0, 0, 1013)                                                               = 0x1599c58                                               
PyModule_GetDict(0x1599c58, 0x733ad5, 0, 0x145c410, 0xffffffffff8cc534)                                         = 0x15d7980                                               
PyImport_ImportModule(0x72d96a, 0x7f06c3418420, 0, 0x145c410, 0xffffffffff8cc534)                               = 0x1599cc8                                               
PyModule_GetDict(0x1599cc8, 1, 35, 0x145c410, 0xfffffffffeb780dc)                                               = 0x15e03f0                                               
PyDict_GetItemString(0x15e03f0, 0x72d96e, 35, 0x145c410, 0xfffffffffeb780dc)                                    = 0x149a120                                               
PyCObject_AsVoidPtr(0x149a120, 0x159a65a, 35, 0x145c410, 0x159a4aa)                                             = 0x7f06b9e04080                                          
--- SIGSEGV (Segmentation fault) ---                                                                                                                                      
+++ killed by SIGSEGV +++

Comment 1 Jacek Pawlyta 2009-10-18 17:09:32 UTC
correction:
the "FIX": manually change:
ScriptingLang=Python
to
ScriptingLang=muParser
in ~/.config/SciDAVis/SciDAVis.conf

Comment 2 Eric Tanguy 2009-10-18 20:28:37 UTC
Thanks but i think the best is to report it upstream http://sourceforge.net/projects/scidavis/forums/forum/708156

Comment 3 Eric Tanguy 2009-11-25 16:44:07 UTC
Could this bug be closed ?-

Comment 4 Fedora Update System 2010-03-14 07:30:32 UTC
scidavis-0.2.4-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/scidavis-0.2.4-1.fc12

Comment 5 Fedora Update System 2010-03-14 07:30:42 UTC
scidavis-0.2.4-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/scidavis-0.2.4-1.fc11

Comment 6 Fedora Update System 2010-03-14 07:30:51 UTC
scidavis-0.2.4-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/scidavis-0.2.4-1.fc13

Comment 7 Fedora Update System 2010-03-14 13:35:50 UTC
scidavis-0.2.4-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2010-03-16 00:34:53 UTC
scidavis-0.2.4-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2010-03-16 00:35:39 UTC
scidavis-0.2.4-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.