Bug 558330 - [abrt] crash in gnochm-0.9.11-4.fc12
Summary: [abrt] crash in gnochm-0.9.11-4.fc12
Alias: None
Product: Fedora
Classification: Fedora
Component: gnochm
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:453984e834801880acee9055689...
: 585974 589182 590937 594468 595214 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-01-24 22:11 UTC by Terry Wallwork
Modified: 2010-12-03 23:52 UTC (History)
21 users (show)

Clone Of:
Last Closed: 2010-12-03 23:52:00 UTC

Attachments (Terms of Use)
File: backtrace (28.12 KB, text/plain)
2010-01-24 22:11 UTC, Terry Wallwork
no flags Details
File: cmdline (258 bytes, text/plain)
2010-01-24 22:11 UTC, Terry Wallwork
no flags Details

Description Terry Wallwork 2010-01-24 22:11:00 UTC
abrt 1.0.3 detected a crash.

Comment: Tried to switch pages and it crashed.
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gnochm '/home/terry/Documents/Books/Python /home/terry/Documents/B /h /home/ / / / /home/te /home/terry/ /h /ho /home/ /home/te /home/te /home/terry/Docu /h /home/ / / / /home/te /home/terry/ /h /ho /home/ /home/te /home/te /home/te'
component: gnochm
executable: /usr/bin/python
package: gnochm-0.9.11-4.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Terry Wallwork 2010-01-24 22:11:02 UTC
Created attachment 386503 [details]
File: backtrace

Comment 2 Terry Wallwork 2010-01-24 22:11:05 UTC
Created attachment 386504 [details]
File: cmdline

Comment 3 Sync 2010-04-20 15:16:32 UTC

When I tried  to view the chm file via the gnochm tool, the tool suddenly broken down. 
And I tried again ,the situation was the same as before.

Please check the  bug report  information. Thanks

Comment 4 Karel Klíč 2010-05-24 15:07:08 UTC
*** Bug 585974 has been marked as a duplicate of this bug. ***

Comment 5 Karel Klíč 2010-05-24 15:07:12 UTC
*** Bug 589182 has been marked as a duplicate of this bug. ***

Comment 6 Karel Klíč 2010-05-24 15:07:17 UTC
*** Bug 590937 has been marked as a duplicate of this bug. ***

Comment 7 Karel Klíč 2010-05-24 15:07:21 UTC
*** Bug 594468 has been marked as a duplicate of this bug. ***

Comment 8 Karel Klíč 2010-05-24 15:07:25 UTC
*** Bug 595214 has been marked as a duplicate of this bug. ***

Comment 9 Bug Zapper 2010-11-04 00:00: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: 

Comment 10 Bug Zapper 2010-12-03 23:52:00 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.