Bug 489475 - broken .desktop file for NetworkManager-vpnc: missing trailing semicolon in MimeType entry
broken .desktop file for NetworkManager-vpnc: missing trailing semicolon in M...
Product: Fedora
Classification: Fedora
Component: NetworkManager-vpnc (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-03-10 06:06 EDT by Till Maas
Modified: 2010-06-10 15:15 EDT (History)
2 users (show)

See Also:
Fixed In Version: NetworkManager-vpnc-0.8.0-1.git20100411.fc12
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-10 15:15:02 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 Till Maas 2009-03-10 06:06:33 EDT
Description of problem:
The MimeType entry in .desktop files can contain multiple values and every
value must have a trailing semicolon:

| Some keys can have multiple values. In such a case, the value of the key is 
| specified as a plural: for example, string(s). The multiple values should be 
| separated by a semicolon, and the value of the key should have a semicolon as 
| trailing character. Semicolons in these values need to be escaped using \;. 

But /usr/share/applications/nm-vpnc.desktop uses this entry:

Version-Release number of selected component (if applicable):
Comment 1 Bug Zapper 2009-06-09 08:04:29 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 2 Dan Williams 2009-11-06 01:46:28 EST

commit 2e1bdcbe90b5a85e439e5d2cd353f87b4b841644
Author: Dan Williams <dcbw@redhat.com>
Date:   Thu Nov 5 22:45:08 2009 -0800

    trivial: make .desktop file pass validation (rh #489475)

Comment 3 Fedora Update System 2010-04-24 03:49:49 EDT
NetworkManager-vpnc-0.8.0-1.git20100411.fc12 has been submitted as an update for Fedora 12.
Comment 4 Fedora Update System 2010-04-26 22:11:35 EDT
NetworkManager-vpnc-0.8.0-1.git20100411.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update NetworkManager-vpnc'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-vpnc-0.8.0-1.git20100411.fc12
Comment 5 Bug Zapper 2010-04-27 09:09:04 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 6 Fedora Update System 2010-06-10 15:14:57 EDT
NetworkManager-vpnc-0.8.0-1.git20100411.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

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