Bug 603070 - [abrt] crash in gnochm-0.9.11-4.fc12: pango_fc_fontset_get_font_at: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnochm-0.9.11-4.fc12: pango_fc_fontset_get_font_at: Process /...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnochm
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e301fc0bdbd8d5b14674cf34aa2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-11 13:32 UTC by Anthony E. Greene
Modified: 2010-12-03 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 13:54:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (52.06 KB, text/plain)
2010-06-11 13:32 UTC, Anthony E. Greene
no flags Details

Description Anthony E. Greene 2010-06-11 13:32:52 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gnochm /home/agreene/Documents/ITT/DataStdzn/SSRF-20100701-v201-Draft/SSRF-20100610-v201-Draft.chm
comment: This appears to depend on the CHM. I was unable to reproduce the behavior using any CHM file that I could provide as an example.
component: gnochm
crash_function: pango_fc_fontset_get_font_at
executable: /usr/bin/python
global_uuid: e301fc0bdbd8d5b14674cf34aa2f092a7eed0b38
kernel: 2.6.31.9-174.fc12.i686.PAE
package: gnochm-0.9.11-4.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Open a CHM file that includes an index tab.
2. Click once on an index term to ensure that the list has the input focus.
3. Press a letter to move the highlight to a different index term.
4. Double-click on the highlighted term to display the topic.
5. Application crashes.

Comment 1 Anthony E. Greene 2010-06-11 13:32:54 UTC
Created attachment 423272 [details]
File: backtrace

Comment 2 Bug Zapper 2010-11-03 13:19:39 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 3 Bug Zapper 2010-12-03 13:54:48 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.