Bug 674731 - xmobar desktop file should not appear in Gnome menu
Summary: xmobar desktop file should not appear in Gnome menu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xmobar
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Boeckel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 04:14 UTC by Jens Petersen
Modified: 2011-06-24 03:26 UTC (History)
2 users (show)

Fixed In Version: ghc-libmpd-0.5.0-8.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-02 18:15:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jens Petersen 2011-02-03 04:14:33 UTC
Description of problem:
I think xmobar doesn't need to be listed in the desktop menu.
So the desktop file should be marked as "hidden".

Steps to Reproduce:
1. start gnome desktop
2. yum install xmobar
3. check Accessories menu
  
Actual results:
"XMobar status bar" listed

Expected results:
xmobar not to be listed, since it is not an application.

Comment 1 Jens Petersen 2011-02-03 04:18:23 UTC
Can be fixed by the following change to xmobar.desktop:


diff --git a/xmobar.desktop b/xmobar.desktop
index 510f1ba..6064406 100644
--- a/xmobar.desktop
+++ b/xmobar.desktop
@@ -7,3 +7,4 @@ Terminal=false
 Name=XMobar status bar
 GenericName=Status bar
 Comment=Text-based status bar inspired by Ion3
+NoDisplay=true

Comment 2 Jens Petersen 2011-03-12 12:57:46 UTC
Should be fixed in xmobar-0.12-5.fc16.

Comment 3 Fedora Update System 2011-06-04 08:08:17 UTC
ghc-libmpd-0.5.0-8.fc14,xmobar-0.13-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/ghc-libmpd-0.5.0-8.fc14,xmobar-0.13-2.fc14

Comment 4 Fedora Update System 2011-06-24 03:26:28 UTC
ghc-libmpd-0.5.0-8.fc14, xmobar-0.13-2.fc14 has been pushed to the Fedora 14 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.