Bug 455205 - gnochm package does not install menuitem sized icon for .chm files
gnochm package does not install menuitem sized icon for .chm files
Product: Fedora
Classification: Fedora
Component: gnochm (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Patrice Dumas
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-13 21:06 EDT by Mukund Sivaraman
Modified: 2009-07-14 12:07 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 12:07:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mukund Sivaraman 2008-07-13 21:06:40 EDT
Description of problem:
gnochm package in F9 does not install a menuitem sized icon for .chm files. So
in places such as my GNOME recent documents menu, I instead see a big 48x48 icon
which is incorrect.

Version-Release number of selected component (if applicable):

How reproducible:
All the time

Steps to Reproduce:
1. Install the gnochm package
2. In the GNOME desktop, open some file using the Nautilus file manager. This
will make it show up in the recent documents list.
3. Go to the recent documents list (Places->Recent Documents). You should see
the menuitem for the .chm file have a huge 48x48 icon.
Actual results:
48x48 icon is shown for the .chm file type.

Expected results:
A menuitem sized icon should be showed for the .chm file type.
Comment 1 Mukund Sivaraman 2008-07-13 21:08:35 EDT
Also, it would be nice if the package maintainer could request a
Tango-compatible icon for it too, and submit it upstream to the gnochm
maintainer. The current icon stands out (ugly) when an icon set following Tango
guidelines is used.
Comment 2 Mukund Sivaraman 2008-07-13 21:10:04 EDT
Step 2 in comment #0 should read "In the GNOME desktop, open a .chm file..."
Comment 3 Patrice Dumas 2008-08-12 11:01:46 EDT
All those requests look fairly reasonable. I don't have to time
to handle them, currently, though. 

If you have time and will to do it yourself, you can put me 
in CC when you contact the relevant people if you want to.
Comment 4 Bug Zapper 2009-06-09 22:04:53 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9'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 9 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 5 Bug Zapper 2009-07-14 12:07:57 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.