Red Hat Bugzilla – Bug 567088
does not show installed "xterm"
Last modified: 2010-06-25 03:16:19 EDT
Description of problem:
xterm package is installed, /usr/share/applications/fedora-xterm.desktop exists but I do not see an entry in either Lancelot nor kde-application launcher. Searching in text search field does not work either.
Sorry to file it here, seems more of a generic KDE problem or perhaps xterm one but I was not sure where else to file it.
Version-Release number of selected component (if applicable):
Up to date F12
It isn't supposed to show up. The relevant desktop file (in xterm package)
contains "NoDisplay=true" which according to  means it shouldn't be
displayed. If anything this is a bug in gnome (for showing it when it shouldn't) or xterm (for using NoDisplay=true). Both kde and gnome have
better alternatives. In the case of kde, konsole.
 - http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html
thanks for the info - so it is a bug in xterm. I know that kde and gnome have alternatives but obviously have installed xterm for a reason. kde and gnome also have alternatives to vim and emacs and yet both are configured to display.
The upstream xterm sources don't contain a setting for NoDisplay,
and the fdo url cited doesn't give a default value for that.
Presumably it defaults to NoDisplay=YES, since I don't recall
Red Hat patching the desktop files. (I can change it, subject
to the usual problem with fdo ongoing incompatibilities with
I have a Fedora12 for checking - it's as reported.
I recall that Red Hat delivered a desktop file, which was one
of the ones that I noticed before adding desktop files to xterm
in patch #226 (2007/6/17). Mandriva uses these files, and so
does SuSE. (The latter changes the icon - not everyone likes
the ones I made). So it looks like a Red Hat-specific bug.
It's Fedora-specific and it's an intentional decision to hide it, see bug 231000. But it is arguably a violation of our packaging guidelines. All GUI apps are supposed to have menu entries.
*** This bug has been marked as a duplicate of bug 607018 ***