Version-Release number of selected component: python-2.7.3-7.2.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: /usr/bin/python /usr/lib/python2.7/site-packages/pymol/__init__.py crash_function: nv_alloc_instruction kernel: 3.3.4-5.fc17.i686 truncated backtrace: :Thread no. 1 (10 frames) : #5 nv_alloc_instruction at nv50_pc.h:351 : #6 new_instruction at nv50_pc.h:362 : #7 bld_insn_1 at nv50_tgsi_to_nc.c:535 : #8 bld_instruction at nv50_tgsi_to_nc.c:1602 : #9 nv50_tgsi_to_nc at nv50_tgsi_to_nc.c:2060 : #10 nv50_generate_code at nv50_pc.c:500 : #11 nv50_program_translate at nv50_program.c:658 : #12 nv50_program_validate at nv50_shader_state.c:134 : #13 nv50_fragprog_validate at nv50_shader_state.c:194 : #14 nv50_state_validate at nv50_state_validate.c:393
Created attachment 623925 [details] File: core_backtrace
Created attachment 623926 [details] File: environ
Created attachment 623927 [details] File: limits
Created attachment 623928 [details] File: backtrace
Created attachment 623929 [details] File: cgroup
Created attachment 623930 [details] File: maps
Created attachment 623931 [details] File: dso_list
Created attachment 623932 [details] File: open_fds
Created attachment 623933 [details] File: var_log_messages
Thanks for filing this bug report. Looking at attachment 623928 [details] I see that thread 1 has a failed assertion: nv_alloc_instruction: Assertion `pc->num_instructions < 2048' failed. deep within OpenGL rendering (and I believe, within an nVidia driver). Reassigning from "python" to "pymol" for now.
(In reply to comment #10) > deep within OpenGL rendering (and I believe, within an nVidia driver). Specifically, within a call to glDrawArrays at frame #18, so probably a driver issue actually. Reassigning from "pymol" to "mesa" in the hope that that's the appropriate component (my knowledge of the internals of our 3D stack is a little hazy, sorry).
OK, let me know if you'd like me to contact pymol upstream and have them take a look, if need be.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.