Bug 557250 - [abrt] crash in pymol-1.2-9.20091006svn3866.fc12
Summary: [abrt] crash in pymol-1.2-9.20091006svn3866.fc12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pymol
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Fenn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6a9faebd
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-20 20:26 UTC by Jan Teichmann
Modified: 2013-11-13 09:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:04:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (581 bytes, text/plain)
2010-01-20 20:26 UTC, Jan Teichmann
no flags Details
2PTC PDB file (170.95 KB, text/plain)
2010-01-25 10:37 UTC, Jan Teichmann
no flags Details

Description Jan Teichmann 2010-01-20 20:26:03 UTC
abrt 1.0.3 detected a crash.

backtrace
-----
Summary: TB6a9faebd <string>:1:<module>:ValueError: invalid literal for int() with base 10: '184A'

Traceback (most recent call last):
  File "<string>", line 1, in <module>
ValueError: invalid literal for int() with base 10: '184A'

Local variables in innermost frame:
chain: E
color: 5388
resv: 184
rank: 1195
resi: 184A
resn: GLY
formal_charge: 0
alt: 
numeric_type: 0
index: 1196
label: 
state: 0
type: ATOM
text_type: 
ID: 1196
cartoon: 0
elec_radius: 0.0
b: 24.7199993134
name: N
vdw: 1.54999995232
ss: 
elem: N
q: 1.0
flags: 134217728
partial_charge: 0.0
segi: 
model: 2PTC

cmdline: /usr/bin/python /usr/lib64/python2.6/site-packages/pymol/__init__.py
component: pymol
executable: /usr/lib64/python2.6/site-packages/pymol/__init__.py
kernel: 2.6.31.9-174.fc12.x86_64
package: pymol-1.2-9.20091006svn3866.fc12
uuid: 6a9faebd

Comment 1 Jan Teichmann 2010-01-20 20:26:08 UTC
Created attachment 385776 [details]
File: backtrace

Comment 2 Tim Fenn 2010-01-25 01:31:45 UTC
Can you provide more information?  Which PDB file(s) were open?  What were you doing at the time to cause the crash?

Comment 3 Jan Teichmann 2010-01-25 10:37:20 UTC
Created attachment 386587 [details]
2PTC PDB file

Comment 4 Jan Teichmann 2010-01-25 10:38:48 UTC
I'm not sure what exactly I've done, but I think it was just loading the 2PTC PDB file I've attached now.

Comment 5 Bug Zapper 2010-11-04 00:23:47 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-04 00:04:40 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


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