Red Hat DESKTOP Quick reference guide

Red Hat Desktop
Deployment Guide

Red Hat Desktop: Deployment Guide
Copyright © 2005 Red Hat, Inc.
Red Hat, Inc.
1801 Varsity Drive
Raleigh NC 27606-2072 USA
Phone: [phone]
Phone: [phone]
Fax: [phone]
PO Box 13588
Research Triangle Park NC 27709 USA
rhd-dg(EN)-4-Print-RHI (2005-03-09T16:26)
Copyright © 2005 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the
Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright
holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited
unless prior permission is obtained from the copyright holder.
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other
countries.
All other trademarks referenced herein are the property of their respective owners.
The GPG fingerprint of the [email protected] key is:
CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E

Table of Contents
Introduction.......................................................................................................................................... i
1. Document Conventions .......................................................................................................... i
2. Activate Your Subscription .................................................................................................. iii
2.1. Provide a Red Hat Login....................................................................................... iv
2.2. Provide Your Subscription Number ...................................................................... iv
2.3. Connect Your System............................................................................................ iv
3. We Need Feedback! .............................................................................................................. v
1. Configuration Overview: The GConf System .............................................................................. 1
1.1. Background: Configuration Sources .................................................................................. 1
1.2. Setting System-Wide Default and Mandatory Preferences................................................ 3
1.2.1. Using GConf Editor ............................................................................................ 3
1.2.2. Using the gconftool-2 Utility ......................................................................... 4
2. Configuring the Panel ..................................................................................................................... 5
2.1. Panel Configuration ........................................................................................................... 5
2.1.1. Configuration Layout .......................................................................................... 5
2.1.2. Default Configuration ......................................................................................... 6
2.1.3. Modifying the Default Configuration ................................................................. 6
3. Menu Editing and Configuration .................................................................................................. 9
3.1. Overview of the Menu System........................................................................................... 9
3.2. Removing Menu Items for Individual Users.................................................................... 10
3.3. Removing Submenus for Individual Users ...................................................................... 11
3.4. Removing Menu Items for All Users............................................................................... 11
3.5. Removing System Menus for All Users .......................................................................... 11
4. Locking Down the Desktop: Disabling GNOME Desktop Features ........................................ 13
4.1. Disabling Lock Screen and Log Out................................................................................ 13
4.2. Disabling [Ctrl]-[Alt]-[Delete]......................................................................................... 13
4.2.1. Window Manager Configuration....................................................................... 14
4.2.2. System-Level Configuration ............................................................................. 15
4.2.3. Disabling [Ctrl]-[Alt]-[Backspace] ................................................................... 15
4.3. Locking Down the Panel .................................................................................................. 15
4.3.1. Disabling Applets.............................................................................................. 16
4.4. Disabling Command Line Access.................................................................................... 17
4.5. Restricting the Number of Workspaces ........................................................................... 18
4.6. Removing Desktop Icons ................................................................................................. 19
4.7. Other Kiosk-related Configuration Tasks ........................................................................ 22
4.7.1. Preventing Automounting of Drives ................................................................. 22
4.7.2. Disabling Printing Functionality ....................................................................... 23
4.7.3. Disabling File Saving........................................................................................ 24
4.7.4. Disabling Application Force Quit ..................................................................... 25
4.7.5. Locking Down Preferences for the Firefox Web Browser ................................ 26
4.7.6. Automatic Login for Public Kiosks .................................................................. 26
5. Remote Desktop Access ................................................................................................................ 29
5.1. Allowing Access .............................................................................................................. 29
5.1.1. Gaining Remote Administrative Access ........................................................... 30
5.2. Connecting Using vncviewer ........................................................................................... 31
5.3. Connecting Using Terminal Server Client ....................................................................... 31
5.3.1. Connecting to a Remote Linux Desktop ........................................................... 32
5.3.2. Connecting to a Remote Windows Desktop ..................................................... 33
Index................................................................................................................................................... 35
Colophon............................................................................................................................................ 37

Introduction
Welcome to the Red Hat Desktop Deployment Guide!
Deploying the GNOME Desktop across an organization commonly requires that some aspects of
the desktop enviroment be modified for that specific deployment. This document aims to enumerate
common deployment tasks and establish best practices for those tasks.
This document is not intended to address the more general topic of system administration and the
GNOME Desktop. The GNOME Desktop System Administration Guide already serves this purpose
and readers are encouraged to refer to this guide through Applications (the main menu on the panel)
=> Help, by selecting the Desktop Category, and then selecting the System Administration Guide
Document from the menu.
1. Document Conventions
When you read this manual, certain words are represented in different fonts, typefaces, sizes, and
weights. This highlighting is systematic; different words are represented in the same style to indicate
their inclusion in a specific category. The types of words that are represented this way include the
following:
command
Linux commands (and other operating system commands, when used) are represented this way.
This style should indicate to you that you can type the word or phrase on the command line
and press [Enter] to invoke a command. Sometimes a command contains words that would be
displayed in a different style on their own (such as file names). In these cases, they are considered
to be part of the command, so the entire phrase is displayed as a command. For example:
Use the cat testfile command to view the contents of a file, named testfile, in the current
working directory.
file name
File names, directory names, paths, and RPM package names are represented this way. This style
should indicate that a particular file or directory exists by that name on your system. Examples:
The .bashrc file in your home directory contains bash shell definitions and aliases for your own
use.
The /etc/fstab file contains information about different system devices and file systems.
Install the webalizer RPM if you want to use a Web server log file analysis program.
application
This style indicates that the program is an end-user application (as opposed to system software).
For example:
Use Mozilla to browse the Web.
[key]
A key on the keyboard is shown in this style. For example:
To use [Tab] completion, type in a character and then press the [Tab] key. Your terminal displays
the list of files in the directory that start with that letter.

ii Introduction
[key]-[combination]
A combination of keystrokes is represented in this way. For example:
The [Ctrl]-[Alt]-[Backspace] key combination exits your graphical session and returns you to the
graphical login screen or the console.
text found on a GUI interface
A title, word, or phrase found on a GUI interface screen or window is shown in this style. Text
shown in this style is being used to identify a particular GUI screen or an element on a GUI
screen (such as text associated with a checkbox or field). Example:
Select the Require Password checkbox if you would like your screensaver to require a password
before stopping.
top level of a menu on a GUI screen or window
A word in this style indicates that the word is the top level of a pulldown menu. If you click on
the word on the GUI screen, the rest of the menu should appear. For example:
Under File on a GNOME terminal, the New Tab option allows you to open multiple shell
prompts in the same window.
If you need to type in a sequence of commands from a GUI menu, they are shown like the
following example:
Go to Applications (the main menu on the panel) => Programming => Emacs Text Editor to
start the Emacs text editor.
button on a GUI screen or window
This style indicates that the text can be found on a clickable button on a GUI screen. For example:
Click on the Back button to return to the webpage you last viewed.
computer output
Text in this style indicates text displayed to a shell prompt such as error messages and responses
to commands. For example:
The ls command displays the contents of a directory. For example:
Desktop about.html logs paulwesterberg.png
Mail backupfiles mail reports
The output returned in response to the command (in this case, the contents of the directory) is
shown in this style.
prompt
A prompt, which is a computer’s way of signifying that it is ready for you to input something, is
shown in this style. Examples:
$
#
[stephen@maturin stephen]$
leopard login:
user input
Text that the user has to type, either on the command line, or into a text box on a GUI screen, is
displayed in this style. In the following example, text is displayed in this style:
To boot your system into the text based installation program, you must type in the text com-
mand at the boot: prompt.

Introduction iii
<replaceable>
Text used for examples, which is meant to be replaced with data provided by the user, is displayed
in this style. In the following example, <version-number>is displayed in this style:
The directory for the kernel source is /usr/src/kernels/<version-number>/, where
<version-number>is the version and type of kernel installed on this system.
Additionally, we use several different strategies to draw your attention to certain pieces of information.
In order of how critical the information is to your system, these items are marked as a note, tip,
important, caution, or warning. For example:
Note
Remember that Linux is case sensitive. In other words, a rose is not a ROSE is not a rOsE.
Tip
The directory /usr/share/doc/ contains additional documentation for packages installed on your
system.
Important
If you modify the DHCP configuration file, the changes do not take effect until you restart the DHCP
daemon.
Caution
Do not perform routine tasks as root — use a regular user account unless you need to use the root
account for system administration tasks.
Warning
Be careful to remove only the necessary partitions. Removing other partitions could result in data
loss or a corrupted system environment.

iv Introduction
2. Activate Your Subscription
Before you can access service and software maintenance information, and the support documenta-
tion included in your subscription, you must activate your subscription by registering with Red Hat.
Registration includes these simple steps:
•Provide a Red Hat login
•Provide a subscription number
•Connect your system
The first time you boot your installation of Red Hat Enterprise Linux, you are prompted to register
with Red Hat using the Setup Agent. If you follow the prompts during the Setup Agent, you can
complete the registration steps and activate your subscription.
If you can not complete registration during the Setup Agent (which requires network access), you
can alternatively complete the Red Hat registration process online at http://www.redhat.com/register/.
2.1. Provide a Red Hat Login
If you do not have an existing Red Hat login, you can create one when prompted during the Setup
Agent or online at:
https://www.redhat.com/apps/activate/newlogin.html
A Red Hat login enables your access to:
•Software updates, errata and maintenance via Red Hat Network
•Red Hat technical support resources, documentation, and Knowledgebase
If you have forgotten your Red Hat login, you can search for your Red Hat login online at:
https://rhn.redhat.com/help/forgot_password.pxt
2.2. Provide Your Subscription Number
Your subscription number is located in the package that came with your order. If your package did not
include a subscription number, your subscription was activated for you and you can skip this step.
You can provide your subscription number when prompted during the Setup Agent or by visiting
http://www.redhat.com/register/.
2.3. Connect Your System
The Red Hat Network Registration Client helps you connect your system so that you can begin to get
updates and perform systems management. There are three ways to connect:
1. During the Setup Agent — Check the Send hardware information and Send system package
list options when prompted.
2. After the Setup Agent has been completed — From Applications (the main menu on the panel),
go to System Tools, then select Red Hat Network.
3. After the Setup Agent has been completed — Enter the following command from the command
line as the root user:

Introduction v
•/usr/bin/up2date --register
3. We Need Feedback!
If you spot a typographical error in the Red Hat Desktop Deployment Guide, or if you have thought of
a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla:
http://bugzilla.redhat.com/bugzilla/ against the component rhd-dg.
When submitting a bug report, be sure to mention the manual’s identifier:
rhd-dg(EN)-4-Print-RHI (2005-03-09T16:26)
If you have a suggestion for improving the documentation, try to be as specific as possible when de-
scribing it. If you have found an error, please include the section number and some of the surrounding
text so we can find it easily.

vi Introduction

Chapter 1.
Configuration Overview: The GConf System
The GConf system is one of the primary means to configure the users’ desktops, therefore a brief
overview of this system is provided below.
Many configurable quantities are accessible via key/value pairs using the graphical GConf editor tool.
This tool is available from the command-line using the command /usr/bin/gconf-editor, or,
more simply by typing gconf-editor in a terminal. The GConf editor is also available through
Applications (the main menu on the panel) => System Tools => Configuration Editor.
For more detailed information on GConf Editor, refer to the Configuration Editor Manual through
Applications (the main menu on the panel) => Help, and by selecting the Applications Category, then
the Utilities Category, and finally, by selecting the Configuration Editor Manual Document.
Figure 1-1. The GConf Editor
1.1. Background: Configuration Sources
The following provides background material that the administrator may find useful, especially when
saving current desktop preferences.

2 Chapter 1. Configuration Overview: The GConf System
Tip
Readers might first wish to refer to the GConf section of the GNOME Desktop System
Administration Guide available through Applications (the main menu on the panel) => Help, and
by selecting the Desktop Category, selecting the System Administration Guide Document, and
reading the chapter titled Using GConf , and also the GConf project page located on the web at
http://www.gnome.org/projects/gconf/ before continuing. Specifically, the use of gconftool-2 to
load and dump preference settings is not discussed in depth in this document, but is detailed in the
GNOME Guide.
GConf stores preferences data in a set of configuration sources. The sources used, their properties,
and the order in which they are used by GConf is defined in the /etc/gconf/2/path file.
Each configuration source entry has three parts:
Storage Backend Identifier
The only commonly used configuration backend is the XML backend whose identifier is xml.
Configuration Source Flags
A comma separated list of flags which is interpreted by the storage backend. The XML backend
recognizes two flags - readonly and readwrite which determine whether the configuration
source is writable.
Storage Location
The location in which the storage backend should store the preferences data. The exact meaning
of this storage location depends on the storage backend in use. With the XML backend, the
location is the path to a filesystem directory.
By default there is a Mandatory Source, a User Source and a Defaults Source. They are:
•xml:readonly:/etc/gconf/gconf.xml.mandatory
•xml:readwrite:$(HOME)/.gconf
•xml:readonly:/etc/gconf/gconf.xml.defaults
The order of the configuration sources is intentional. If a key is set in the Mandatory Source and the
Defaults Source, then the value in the Mandatory Source takes precedence. Therefore, by setting the
value of a key in the Mandatory Source, users will not be able to modify that key.
The default GConf path file also includes a number of other path files if they exist. The
/etc/gconf/2/path file allows administrators to define new configuration sources and include
them in the set of configuration sources used by GConf. The configuration sources specified in the
path file are included before the standard Defaults Source.
One final item of note is that the storage location specifier for a source may also reference
the value of environmental variables. For example, the standard User Source is defined as
xml:readwrite:$(HOME)/.gconf. Environmental variables may be defined as follows:
$(HOME)
The user’s home directory.
$(USER)
The user’s username.

Chapter 1. Configuration Overview: The GConf System 3
$(ENV_name)
Any other environmental variable may be referenced by prefixing the environmental variables
name with ENV_.
1.2. Setting System-Wide Default and Mandatory Preferences
You can set system-wide settings using either the graphical GConf editor or the command line utility,
gconftool-2. Examples of each method are given below.
Caution
You should make sure that all users are logged out before changing any system-wide default or
mandatory preference settings.
1.2.1. Using GConf Editor
When logged in as root, you can use GConf editor to set system-wide default and system-wide
mandatory settings by opening a special GConf editor window. For example, to set mandatory
system-wide settings, run GConf editor and choose New Mandatory Window from the File menu
as shown in Figure 1-2.
Figure 1-2. Mandatory Settings Using GConf Editor

4 Chapter 1. Configuration Overview: The GConf System
Tip
Refer to the Configuration Editor Manual (available through the online help system) for more detailed
information on using the GConf editor.
1.2.2. Using the gconftool-2 Utility
For example, using gconftool-2 you can set the system-wide default number of workspaces to 5 by
issuing the command:
# gconftool-2 --direct --config-source \
xml:readwrite:/etc/gconf/gconf.xml.defaults \
xml:readwrite:/etc/gconf/gconf.xml.defaults --type int --set \
/apps/metacity/general/num_workspaces 5
Tip
Refer to the GConf Section of the GNOME Desktop System Administration Guide (available through
the online help system) for more detailed information regarding the use of gconftool-2.

Chapter 2.
Configuring the Panel
Tip
For more information on configuring panels, refer to the GConf chapter of the GNOME Desktop Ad-
ministration Guide available through Applications (the main menu on the panel) => Help, selecting
the Desktop Category, and choosing the System Administration Guide Document.
Note
For information on locking down the panel, refer to Section 4.3 Locking Down the Panel.
2.1. Panel Configuration
The following material is meant to serve as a more technical reference for panel configuration.
2.1.1. Configuration Layout
The panel configuration contains a more complex set of GConf keys. This section gives an overview
of how those keys are organized.
Most of the panel configuration is stored in /apps/panel/. The general/ directory contains the
following keys:
toplevel_id_list
The list of panel identifiers. Each identifier is also the name of the sub-directory in the
toplevels directory which contains the actual preferences for that panel.
object_id_list
The list of panel object identifiers. Each identifier is also the name of the sub-directory in the
objects directory which contains the actual preferences for that panel object.
applet_id_list
The list of panel applet identifiers. Each identifier is also the name of the subdirectory in the
applets directory, which contains the actual preferences for that panel applet.
Thus, the default contents of /apps/panel/ looks something like:
/apps/panel/general:
applet_id_list = [mixer,clock,systray,...]
object_id_list = [menu_bar,web_launcher,...]

6 Chapter 2. Configuring the Panel
toplevel_id_list = [top_panel,bottom_panel]
...
/apps/panel/toplevels/bottom_panel:
size = 24
expand = true
name = Bottom Panel
orientation = bottom
...
/apps/panel/objects/menu_bar:
toplevel_id = top_panel
object_type = menu-bar
position = 0
locked = true
...
/apps/panel/objects/web_launcher:
toplevel_id = top_panel
object_type = launcher-object
position = 1
launcher_location = file:///usr/share/applications/redhat-web.desktop
...
/apps/panel/applets/clock:
toplevel_id = top_panel
object_type = bonobo-applet
position = 1
panel_right_stick = true
locked = true
bonobo_iid = OAFIID:GNOME_ClockApplet
...
2.1.2. Default Configuration
The default panel configuration is specified in
/etc/gconf/schemas/panel-default-setup.entries. When the
panel is installed, the default configuration is loaded into the Defaults Source using the
gconftool-2 "--load" argument:
# gconftool-2 \
--config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults \
--direct --load /etc/gconf/schemas/panel-default-setup.entries
This command loads the default configuration into the /apps/panel/default_setup GConf di-
rectory.
2.1.3. Modifying the Default Configuration
Modifying the default panel configuration can be a difficult task. Unfortunately, it is also one of the
more common tasks for administrators wishing to deploy a modified desktop environment configura-
tion.

Chapter 2. Configuring the Panel 7
Tip
Refer to the GNOME Desktop System Administration Guide for an alternative method for changing
the default panel configuration to that described below.
The following provides a more complex example of how to modify the default panel configuration.
2.1.3.1. Example: Removing the Print Manager launcher and the Notification
Area
Consider a relatively straightforward example and assume that we wish to remove the Print Manager
launcher and the Notification Area from the default configuration.
•Make a copy of /etc/gconf/schemas/panel-default-setup.entries:
# cp /etc/gconf/schemas/panel-default-setup.entries \
/etc/gconf/schemas/local-panel-default-setup.entries
•Edit local-panel-default-setup.entries, removing the print_launcher entry from
object_id_list and removing the print_launcher directory from the objects directory:
<value>
<string>spreadsheet_launcher</string>
</value>
<value>
<string>print_launcher</string>
</value>
</list>
</list>
</value>
</entry>
...
<!-- Print Launcher -->
<entry>
<key>objects/print_launcher/object_type</key>
<schema_key>/schemas/apps/panel/objects/object_type</schema_key>
<value>
<string>launcher-object</string>
</value>
</entry>
...
<entry>
<key>objects/print_launcher/menu_path</key>
<schema_key>/schemas/apps/panel/objects/menu_path</schema_key>
</entry>
<entry>
<key>objects/print_launcher/action_type</key>
<schema_key>/schemas/apps/panel/objects/action_type</schema_key>
</entry>
<!-- Workspace Switcher Applet -->
•Next, remove the systray entry from applet_id_list and remove the systray directory from
the applets directory:
<string>mixer</string>
</value>
<value>
<string>systray</string>
</value>
<value>

8 Chapter 2. Configuring the Panel
<string>clock</string>
</value>
<value>
...
<!-- System Tray Applet -->
<entry>
<key>applets/systray/object_type</key>
<schema_key>/schemas/apps/panel/objects/object_type</schema_key>
<value>
<string>bonobo-applet</string>
</value>
</entry>
...
<entry>
<key>applets/systray/menu_path</key>
<schema_key>/schemas/apps/panel/objects/menu_path</schema_key>
</entry>
<entry>
<key>applets/systray/launcher_location</key>
<schema_key>/schemas/apps/panel/objects/launcher_location</schema_key>
</entry>
<entry>
<key>applets/systray/action_type</key>
<schema_key>/schemas/apps/panel/objects/action_type</schema_key>
</entry>
<!-- Clock Applet -->
•Create the configuration source into which you will load your modified default setup:
# mkdir --mode a=rwx,g=rx,o=rx \
/etc/gconf/local.xml.defaults
It is important that your configuration source be created using the correct --mode argument to
ensure it is readable by all users. GConf will use the permissions from this toplevel directory when
creating new files or directories in the configuration source.
•Load the new default setup into /apps/panel/default_setup in the new configuration source:
# gconftool-2 --config-source=xml:readwrite:/etc/gconf/local.xml.defaults \
--direct --load \
/etc/gconf/schemas/local-panel-default-setup.entries
•Add the new configuration source to /etc/gconf/2/path, which will cause the source to appear
before the Defaults Source for all users:
# echo "xml:readonly:/etc/gconf/local.xml.defaults" \
>> /etc/gconf/2/path
Note
This change will only come into effect when the GConf daemon is re-started. Therefore, it is
preferable to make the change with all users logged out.

Chapter 3.
Menu Editing and Configuration
Tip
For detailed information describing the implementation of the menu system, refer to the Desktop
Menu Specification located at the freedesktop.org website: http://standards.freedesktop.org/menu-
spec/latest.
It is often useful for an administrator to add or remove items from the main desktop Applications
menu. Owing to the complexity of the menu system, modifying the Applications menu can sometimes
be a difficult task. For example, it is much more difficult to add a menu item than it is to remove a
menu item.
This chapter provides an overview of the menu system and documents methods for:
•Removing menu items for individual users
•Removing menu items for all users
•Removing submenus for individual users
•Removing submenus for all users
3.1. Overview of the Menu System
Note
This overview of the menu system is not intended to to be comprehensive in its scope. For detailed
information about the menu system, refer to the various menu-related specifications at the freedesk-
top.org web site: http://www.freedesktop.org
The Red Hat menu system is based on the the freedesktop.org Desktop Menu Specification and con-
sists of three major sets of configuration and data files:
Menu (*.menu) Files
The *.menu files are XML configuration files that specify the order, hierarchy, and merging of
both menus and menu items.
The system *.menu files are located in /etc/xdg/menus/. User-specific *.menu files are lo-
cated in $HOME/.config/menus/ and can be edited to override the values specified in the
system *.menu files.
In particular, the /etc/xdg/menus/applications.menu file contains the definition of the
main application menu layout.

10 Chapter 3. Menu Editing and Configuration
Directory Entry (*.directory) Files
The *.directory files provide data about a menu such as its name, tooltip, and icon, and
are located in /usr/share/desktop-directories/. Refer to the GNOME Desktop System
Administration Guide for more information on directory entry files.
Desktop Entry (*.desktop) Files
The *.desktop files provide data about a menu item such as its name, command to run,
and its icon. The desktop entry files also contain keywords that determine the location
of the menu item in the menu hierarchy. The system desktop entry files are located in
/usr/share/applications/. Refer to the GNOME Desktop System Administration Guide
for more information on desktop entry files.
User-specific desktop entry files are located in $HOME/.local/share/applications/ and
can be used to add applications to the "Open With =>" submenu that appears when right-
clicking on a file. The $HOME/.local/share/applications/mimeinfo.cache contains
MIME type information associating the $HOME/.local/share/applications/*.desktop
applications with the file types specified in the *.desktop files.
3.2. Removing Menu Items for Individual Users
The menu configuration files for a given user are located in the $HOME/.config/menus/ directory.
The *.menu files are XML configuration files that allow you to override the system menu defaults.
For example, to remove the Calculator menu item from the Accessories submenu, edit the
applications.menu file in the $HOME/.config/menus/ directory, adding a new <Menu>
section using the <Exclude>element as shown:
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
<!-- File created by desktop-file-utils version 0.8 -->
<Menu>
<Name>Applications</Name>
<MergeFile>/etc/xdg/menus/applications.menu</MergeFile>
<!-- Removes the Calculator from the Accessories submenu -->
<Menu>
<Name>Accessories</Name>
<Exclude>
<Filename>gnome-gcalctool.desktop</Filename>
</Exclude>
</Menu>
<!-- END of Calculator removal content -->
</Menu>
The *.desktop file that corresponds to a given menu item can be found in the
/usr/share/applications/ directory. The gnome-gcalctool.desktop file corresponds to
the Calculator menu item. Note that the name of the submenu (Accessories, in this case) can be
determined from the files located in the /usr/share/desktop-directories/ directory.
Similar methods can be used to remove other items from the Applications menu and its submenus.