Bug 229070 - Wrong 'Exec' and 'MimeType' in kchmviewer.desktop
Wrong 'Exec' and 'MimeType' in kchmviewer.desktop
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: kchmviewer (Show other bugs)
6
All Linux
medium Severity low
: ---
: ---
Assigned To: Patrice Dumas
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-16 14:50 EST by Andrew Zabolotny
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 2.7-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-17 04:54:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Zabolotny 2007-02-16 14:50:39 EST
Description of problem:

The .desktop file provided with kchmviewer is slightly incorrect.

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

2.6-2.fc6

How reproducible:

Always

Steps to Reproduce:
1. Install kchmviewer
2. Open a folder with .chm files
3. Double-click on a chm file
  
Actual results:

It will tell you it doesn't know how to open the file

Expected results:

The file should be opened with kchmviewer

Additional info:

Actually the .desktop file contains two bugs:

1. "Exec=kchmviewer %U" must be "Exec=kchmviewer %f" as kchmviewer doesn't
understand URLs on command line, so it doesn't know how to open
"file:///some/where/something.chm" (and neither can open several files at once,
so %f not %F).

2. "MimeType=application/x-chm" should be "MimeType=application/chm". This is
the MIME type that Gnome assigns to chm files.
Comment 1 Patrice Dumas 2007-02-17 04:54:01 EST
In fact application/chm is required for kde mimetypes handling, and
application/x-chm for the freedesktop mimetype handling. So I added both
and corrected the %U. Thanks for the report, should be fixed in 
2.7-2 (in FC-6 and devel).

Note You need to log in before you can comment on or make changes to this bug.