Bug 626952 - [abrt] gnochm-0.9.11-5.fc13: pango_fc_fontset_get_font_at: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnochm-0.9.11-5.fc13: pango_fc_fontset_get_font_at: Process /usr/bin/p...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnochm
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:50ff8d3753062f0bfbe24d3eafd...
: 617076 620027 649359 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-24 18:14 UTC by Jérôme Benoit
Modified: 2011-06-28 14:03 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 14:03:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (38.64 KB, text/plain)
2010-08-24 18:14 UTC, Jérôme Benoit
no flags Details

Description Jérôme Benoit 2010-08-24 18:14:50 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gnochm '/home/fraggle/Bureau/Documentation en vrac/O\'Reilly - SQL in a Nutshell 2nd Edition.chm'
comment: clicking on a submenu
component: gnochm
crash_function: pango_fc_fontset_get_font_at
executable: /usr/bin/python
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: gnochm-0.9.11-5.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282673534
uid: 500

How to reproduce
-----
1. Reading a .chm file
2.
3.

Comment 1 Jérôme Benoit 2010-08-24 18:14:53 UTC
Created an attachment (id=440717)
File: backtrace

Comment 2 isiscreation 2010-08-24 23:18:25 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Just pressing an embedded link on the page
2.
3.

Comment 3 rossrobert24 2010-09-01 01:55:29 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Just opened the file, read a bit and it crashed.
2.
3.


Comment
-----
Yea, I noticed that tables titles were superimposed over the first couple of lines of the table... like the title was running down the table instead of across to top

Comment 4 Ganapathi Kamath 2010-09-13 22:25:56 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. opened a chm file
2. clicked around
3. crashed on a click

Comment 5 Tore Anderson 2010-09-15 18:41:56 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
Not exactly sure when or how this happened - just noticed the crash lying there unreported in ABRT's queue today.

Comment 6 datahal42 2010-10-08 01:50:54 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.open chm file
2.version fedora 13 64 bit
3.

Comment 7 Stjepan Gros 2010-10-11 20:42:37 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
Nothing specific. I was reading CHM file and clicked on the next chapter when GNOCHM crashed.

Comment 8 Marc 2010-10-26 19:35:38 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Run gnochm with any chm file 
2. Change a few pages (press next, click links)
3. Within a few seconds a segfault crash will occur


Comment
-----
Seems to be looking for pango, but I have this installed (including devel version).

Comment 9 isiscreation 2010-11-07 15:15:44 UTC
Package: gnochm-0.9.11-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Clicking on the "Next" link for three consective times
2. Crash
3.

Comment 10 Karel Klíč 2010-11-08 18:06:59 UTC
*** Bug 620027 has been marked as a duplicate of this bug. ***

Comment 11 Karel Klíč 2010-11-08 18:07:04 UTC
*** Bug 617076 has been marked as a duplicate of this bug. ***

Comment 12 Karel Klíč 2010-11-08 18:07:09 UTC
*** Bug 649359 has been marked as a duplicate of this bug. ***

Comment 13 datahal42 2010-11-17 03:38:07 UTC
hi ,gnochm always has problem to open some chm file , therefore im use chmsee. 

This soft (chmsee) should be default in gnome and fedora

Comment 14 Bug Zapper 2011-06-01 10:34:00 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 15 Bug Zapper 2011-06-28 14:03:22 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.