Bug 955323

Summary: [abrt] pymol-1.5.0.2-7.20120218svn3982.fc19: CShaderPrg_Enable: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jeff Bastian <jbastian>
Component: pymolAssignee: Tim Fenn <tim.fenn>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: tim.fenn
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:71a87b0c33618abb25795ac418aaba7067f2fa56
Fixed In Version: pymol-1.6.0-2.20130620svn4032.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-12 03:04:57 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:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jeff Bastian 2013-04-22 18:49:44 UTC 
Description of problem:
Tried running the demos in pymol

Version-Release number of selected component:
pymol-1.5.0.2-7.20120218svn3982.fc19

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/lib64/python2.7/site-packages/pymol/__init__.py
crash_function: CShaderPrg_Enable
executable:     /usr/bin/python2.7
kernel:         3.9.0-0.rc7.git1.2.fc20.x86_64
runlevel:       N 5
uid:            1000
ureports_counter: 1
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 CShaderPrg_Enable at layer0/ShaderMgr.c:670
 #1 CShaderPrg_Enable_SphereShader at layer0/ShaderMgr.c:1017
 #2 RepSphereRender at layer2/RepSphere.c:2036
 #3 CoordSetRender at layer2/CoordSet.c:1430
 #4 ObjectMoleculeRender at layer2/ObjectMolecule.c:12496
 #5 SceneRenderAll at layer1/Scene.c:8574
 #6 DoRendering at layer1/Scene.c:8925
 #7 SceneRender at layer1/Scene.c:9984
 #8 OrthoDoDraw at layer1/Ortho.c:1606
 #9 ExecutiveDrawNow at layer3/Executive.c:12109
Comment 1 Jeff Bastian 2013-04-22 18:49:47 UTC 
Created attachment 738627 [details]
File: backtrace
Comment 2 Jeff Bastian 2013-04-22 18:49:49 UTC 
Created attachment 738628 [details]
File: cgroup
Comment 3 Jeff Bastian 2013-04-22 18:49:50 UTC 
Created attachment 738629 [details]
File: core_backtrace
Comment 4 Jeff Bastian 2013-04-22 18:49:52 UTC 
Created attachment 738630 [details]
File: dso_list
Comment 5 Jeff Bastian 2013-04-22 18:49:54 UTC 
Created attachment 738631 [details]
File: environ
Comment 6 Jeff Bastian 2013-04-22 18:49:56 UTC 
Created attachment 738632 [details]
File: limits
Comment 7 Jeff Bastian 2013-04-22 18:49:58 UTC 
Created attachment 738633 [details]
File: maps
Comment 8 Jeff Bastian 2013-04-22 18:50:00 UTC 
Created attachment 738634 [details]
File: open_fds
Comment 9 Jeff Bastian 2013-04-22 18:50:02 UTC 
Created attachment 738635 [details]
File: proc_pid_status
Comment 10 Jeff Bastian 2013-04-22 18:50:07 UTC 
Created attachment 738636 [details]
File: var_log_messages
Comment 11 Jeff Bastian 2013-04-22 18:55:05 UTC 
I was following the instructions to run pymol and OpenArena to test the graphics performance with aggressive power saving enabled for the Fedora 19 Power Management Test Day:

https://fedoraproject.org/wiki/QA:Testcase_Power_Management_video_powersave_stability
https://fedoraproject.org/wiki/Test_Day:2013-04-17_Power_Management#Video_cards


My system is a Lenovo T60 laptop with Intel 945GM graphics.  If it matters, I also have these package versions:

xorg-x11-drv-intel-2.21.6-1.fc19.x86_64
mesa-dri-drivers-9.1-6.fc19.x86_64
mesa-dri-filesystem-9.1-6.fc19.x86_64
mesa-libEGL-9.1-6.fc19.x86_64
mesa-libEGL-devel-9.1-6.fc19.x86_64
mesa-libgbm-9.1-6.fc19.x86_64
mesa-libGL-9.1-6.fc19.x86_64
mesa-libglapi-9.1-6.fc19.x86_64
mesa-libGL-devel-9.1-6.fc19.x86_64
mesa-libGLU-9.0.0-2.fc19.x86_64
mesa-libxatracker-9.1-6.fc19.x86_64
Comment 12 Tim Fenn 2013-04-26 07:14:59 UTC 
I'll pass this along to upstream.  A new version is on the way soon, so hopefully some of this will be addressed there?
Comment 13 Fedora Update System 2013-07-02 08:20:44 UTC 
pymol-1.6.0-1.20130620svn4032.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/pymol-1.6.0-1.20130620svn4032.fc19
Comment 14 Fedora Update System 2013-07-02 08:21:08 UTC 
pymol-1.6.0-2.20130620svn4032.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/pymol-1.6.0-2.20130620svn4032.el6
Comment 15 Fedora Update System 2013-07-02 08:21:27 UTC 
pymol-1.6.0-1.20130620svn4032.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/pymol-1.6.0-1.20130620svn4032.fc18
Comment 16 Fedora Update System 2013-07-03 01:41:12 UTC 
Package pymol-1.6.0-1.20130620svn4032.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pymol-1.6.0-1.20130620svn4032.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12176/pymol-1.6.0-1.20130620svn4032.fc18
then log in and leave karma (feedback).
Comment 17 Fedora Update System 2013-07-12 03:04:57 UTC 
pymol-1.6.0-1.20130620svn4032.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 18 Fedora Update System 2013-07-12 03:07:03 UTC 
pymol-1.6.0-1.20130620svn4032.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 19 Fedora Update System 2013-07-22 21:47:59 UTC 
pymol-1.6.0-2.20130620svn4032.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.