{
	"id": "77420861-0df6-4c3c-9925-b0c53adf6dca",
	"created_at": "2026-04-06T00:08:52.874778Z",
	"updated_at": "2026-04-10T03:20:00.448327Z",
	"deleted_at": null,
	"sha1_hash": "9bb3c81cb209a6ed6a44236abb3fdb7e2f88b20c",
	"title": "Recognized desktop entry keys | Desktop Entry Specification",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 73371,
	"plain_text": "Recognized desktop entry keys | Desktop Entry Specification\r\nArchived: 2026-04-05 16:44:18 UTC\r\nKey Description Value Type REQ? Type\r\nType\r\nThis specification defines 3 types of desktop\r\nentries: Application (type 1), Link (type\r\n2) and Directory (type 3). To allow the\r\naddition of new types in the future,\r\nimplementations should ignore desktop entries\r\nwith an unknown type.\r\nstring YES  \r\nVersion\r\nVersion of the Desktop Entry Specification\r\nthat the desktop entry conforms with. Entries\r\nthat confirm with this version of the\r\nspecification should use 1.5 . Note that the\r\nversion field is not required to be present.\r\nstring NO 1-3\r\nName\r\nSpecific name of the application, for example\r\n\"Mozilla\".\r\nlocalestring YES 1-3\r\nGenericName\r\nGeneric name of the application, for example\r\n\"Web Browser\".\r\nlocalestring NO 1-3\r\nNoDisplay\r\nNoDisplay means \"this application exists, but\r\ndon't display it in the menus\". This can be\r\nuseful to e.g. associate this application with\r\nMIME types, so that it gets launched from a\r\nfile manager (or other apps), without having a\r\nmenu entry for it (there are tons of good\r\nreasons for this, including e.g. the netscape -\r\nremote , or kfmclient openURL kind of\r\nstuff).\r\nboolean NO 1-3\r\nComment\r\nTooltip for the entry, for example \"View sites\r\non the Internet\". The value should not be\r\nredundant with the values of Name and\r\nGenericName .\r\nlocalestring NO 1-3\r\nIcon Icon to display in file manager, menus, etc. If\r\nthe name is an absolute path, the given file\r\nwill be used. If the name is not an absolute\r\niconstring NO 1-3\r\nhttps://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html\r\nPage 1 of 5\n\nKey Description Value Type REQ? Type\r\npath, the algorithm described in the Icon\r\nTheme Specification\r\n(http://freedesktop.org/wiki/Standards/icon-theme-spec) will be used to locate the icon.\r\nHidden\r\nHidden should have been called Deleted . It\r\nmeans the user deleted (at their level)\r\nsomething that was present (at an upper level,\r\ne.g. in the system dirs). It's strictly equivalent\r\nto the .desktop file not existing at all, as far\r\nas that user is concerned. This can also be used\r\nto \"uninstall\" existing files (e.g. due to a\r\nrenaming) - by letting make install install a\r\nfile with Hidden=true in it.\r\nboolean NO 1-3\r\nOnlyShowIn ,\r\nNotShowIn\r\nA list of strings identifying the desktop\r\nenvironments that should display/not display a\r\ngiven desktop entry.\r\nBy default, a desktop file should be shown,\r\nunless an OnlyShowIn key is present, in which\r\ncase, the default is for the file not to be shown.\r\nIf $XDG_CURRENT_DESKTOP is set then it\r\ncontains a colon-separated list of strings. In\r\norder, each string is considered. If a matching\r\nentry is found in OnlyShowIn then the\r\ndesktop file is shown. If an entry is found in\r\nNotShowIn then the desktop file is not shown.\r\nIf none of the strings match then the default\r\naction is taken (as above).\r\n$XDG_CURRENT_DESKTOP should have been set\r\nby the login manager, according to the value\r\nof the DesktopNames found in the session\r\nfile. The entry in the session file has multiple\r\nvalues separated in the usual way: with a\r\nsemicolon.\r\nThe same desktop name may not appear in\r\nboth OnlyShowIn and NotShowIn of a group.\r\nstring(s) NO 1-3\r\nhttps://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html\r\nPage 2 of 5\n\nKey Description Value Type REQ? Type\r\nDBusActivatable\r\nA boolean value specifying if D-Bus activation\r\nis supported for this application. If this key is\r\nmissing, the default value is false . If the\r\nvalue is true then implementations should\r\nignore the Exec key and send a D-Bus\r\nmessage to launch the application. See D-Bus\r\nActivation for more information on how this\r\nworks. Applications should still include Exec=\r\nlines in their desktop files for compatibility\r\nwith implementations that do not understand\r\nthe DBusActivatable key.\r\nboolean NO  \r\nTryExec\r\nPath to an executable file on disk used to\r\ndetermine if the program is actually installed.\r\nIf the path is not an absolute path, the file is\r\nlooked up in the $PATH environment variable.\r\nIf the file is not present or if it is not\r\nexecutable, the entry may be ignored (not be\r\nused in menus, for example).\r\nstring NO 1\r\nExec\r\nProgram to execute, possibly with arguments.\r\nSee the Exec key for details on how this key\r\nworks. The Exec key is required if\r\nDBusActivatable is not set to true . Even if\r\nDBusActivatable is true , Exec should be\r\nspecified for compatibility with\r\nimplementations that do not understand\r\nDBusActivatable .\r\nstring NO 1\r\nPath\r\nIf entry is of type Application , the working\r\ndirectory to run the program in.\r\nstring NO 1\r\nTerminal\r\nWhether the program runs in a terminal\r\nwindow.\r\nboolean NO 1\r\nActions\r\nIdentifiers for application actions. This can be\r\nused to tell the application to make a specific\r\naction, different from the default behavior. The\r\nApplication actions section describes how\r\nactions work.\r\nstring(s) NO 1\r\nMimeType\r\nThe MIME type(s) supported by this\r\napplication.\r\nstring(s) NO 1\r\nhttps://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html\r\nPage 3 of 5\n\nKey Description Value Type REQ? Type\r\nCategories\r\nCategories in which the entry should be shown\r\nin a menu (for possible values see the Desktop\r\nMenu Specification\r\n(http://www.freedesktop.org/Standards/menu-spec)).\r\nstring(s) NO 1\r\nImplements\r\nA list of interfaces that this application\r\nimplements. By default, a desktop file\r\nimplements no interfaces. See Interfaces for\r\nmore information on how this works.\r\nstring(s) NO  \r\nKeywords\r\nA list of strings which may be used in addition\r\nto other metadata to describe this entry. This\r\ncan be useful e.g. to facilitate searching\r\nthrough entries. The values are not meant for\r\ndisplay, and should not be redundant with the\r\nvalues of Name or GenericName .\r\nlocalestring(s) NO 1\r\nStartupNotify\r\nIf true, it is KNOWN that the application will\r\nsend a \"remove\" message when started with\r\nthe DESKTOP_STARTUP_ID environment\r\nvariable set. If false, it is KNOWN that the\r\napplication does not work with startup\r\nnotification at all (does not shown any\r\nwindow, breaks even when using\r\nStartupWMClass, etc.). If absent, a reasonable\r\nhandling is up to implementations (assuming\r\nfalse, using StartupWMClass, etc.). (See the\r\nStartup Notification Protocol Specification\r\n(http://www.freedesktop.org/Standards/startup-notification-spec) for more details).\r\nboolean NO 1\r\nStartupWMClass\r\nIf specified, it is known that the application\r\nwill map at least one window with the given\r\nstring as its WM class or WM name hint (see\r\nthe Startup Notification Protocol Specification\r\n(http://www.freedesktop.org/Standards/startup-notification-spec) for more details).\r\nstring NO 1\r\nURL If entry is Link type, the URL to access. string YES 2\r\nPrefersNonDefaultGPU If true, the application prefers to be run on a\r\nmore powerful discrete GPU if available,\r\nboolean NO 1\r\nhttps://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html\r\nPage 4 of 5\n\nKey Description Value Type REQ? Type\r\nwhich we describe as “a GPU other than the\r\ndefault one” in this spec to avoid the need to\r\ndefine what a discrete GPU is and in which\r\ncases it might be considered more powerful\r\nthan the default GPU. This key is only a hint\r\nand support might not be present depending on\r\nthe implementation.\r\nSingleMainWindow\r\nIf true, the application has a single main\r\nwindow, and does not support having an\r\nadditional one opened. This key is used to\r\nsignal to the implementation to avoid offering\r\na UI to launch another window of the app.\r\nThis key is only a hint and support might not\r\nbe present depending on the implementation.\r\nboolean NO 1\r\nSource: https://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html\r\nhttps://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html\r\nPage 5 of 5",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html"
	],
	"report_names": [
		"recognized-keys.html"
	],
	"threat_actors": [],
	"ts_created_at": 1775434132,
	"ts_updated_at": 1775791200,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/9bb3c81cb209a6ed6a44236abb3fdb7e2f88b20c.pdf",
		"text": "https://archive.orkl.eu/9bb3c81cb209a6ed6a44236abb3fdb7e2f88b20c.txt",
		"img": "https://archive.orkl.eu/9bb3c81cb209a6ed6a44236abb3fdb7e2f88b20c.jpg"
	}
}