Bug 592746 - [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: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8d4c3934e937127142a15d64496...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-16 16:42 UTC by Aleksandar Kanchev
Modified: 2010-12-03 14:39 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 14:39:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (86.10 KB, text/plain)
2010-05-16 16:42 UTC, Aleksandar Kanchev
no flags Details

Description Aleksandar Kanchev 2010-05-16 16:42:10 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gnochm /home/kanchev/download/firefox/Microsoft.Press.The.Security.Development.Lifecycle.Jun.2006.chm
component: gnochm
crash_function: pango_fc_fontset_get_font_at
executable: /usr/bin/python
global_uuid: 8d4c3934e937127142a15d6449621223e3f0a32d
kernel: 2.6.32.11-99.fc12.x86_64
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. read the "Microsoft Security Development Lifecycle 2006"
2. increase text size since it's "normal size" is way too small
3. switch between chapters

Comment 1 Aleksandar Kanchev 2010-05-16 16:42:13 UTC
Created attachment 414379 [details]
File: backtrace

Comment 2 filipe.custodio 2010-05-18 00:22:22 UTC
Package: gnochm-0.9.11-4.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1.Unable to reproduce
2.
3.


Comment
-----
Crashed twice (in different ways) while using the file MoTV.Complete.vol-024.2010-01-02.chm. Unable to reproduce.

Comment 3 Jean Figueiredo 2010-06-07 16:11:26 UTC
Package: gnochm-0.9.11-4.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. search 
2.
3.

Comment 4 Bug Zapper 2010-11-03 14:46:57 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 5 Bug Zapper 2010-12-03 14:39:22 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.