Bug 858779 - Use a more descriptive comment for the desktop file.
Summary: Use a more descriptive comment for the desktop file.
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 18
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-09-19 16:37 UTC by Sergio
Modified: 2012-12-10 13:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-12-10 13:23:20 UTC
Type: Bug

Attachments (Terms of Use)

Description Sergio 2012-09-19 16:37:12 UTC
Description of problem: Current comment (menu tip) for fedora-yumex.desktop is 'GUI front end for Yum' and, coupled with the name 'Yum Extender', besides being redundant is clueless for a new user.

Version-Release number of selected component (if applicable): 3.0.7 and earlier.

How reproducible: always

Steps to Reproduce:
1. Browse to 'Yum Extender' on the menu (Xfce, for instance).
2. If menu tips are enabled it will pop-up.
Actual results: Displays non-informational 'GUI front end for Yum'

Expected results: Could display something straight like 'Install and remove applications'.

Additional info:

Comment 1 Tim Lauridsen 2012-09-19 16:40:22 UTC
Sounds like a good idea, I will change it

Comment 3 Fedora Update System 2012-10-03 14:49:55 UTC
yumex-3.0.9-1.fc18 has been submitted as an update for Fedora 18.

Comment 4 Fedora Update System 2012-10-03 14:50:28 UTC
yumex-3.0.9-1.fc17 has been submitted as an update for Fedora 17.

Comment 5 Fedora Update System 2012-10-03 17:05:18 UTC
Package yumex-3.0.9-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing yumex-3.0.9-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 6 Sergio 2012-12-10 13:23:20 UTC
I'm closing this as we have already 3.0.10 in stable and this was fixed.

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