Desktop Migration and Administration Guide

Procedure 10.1. Setting the Distribution Name

1. As root, open the /etc/default/grub file.
2. Use the GRUB_DISTRIBUTOR variable to specify your own distribution name. The following is the excerpt of the /etc/default/grub file. Update the second line with the GRUB_DISTRIBUTOR variable:

   GRUB_TIMEOUT=5
   GRUB_DISTRIBUTOR=Our Corporate Distro V1.2
   GRUB_DEFAULT=saved
   GRUB_DISABLE_SUBMENU=true
   ...
   

3. Run the following command as root to ensure the changes take effect:

   grub2-mkconfig -o /boot/grub2/grub.cfg

   Note

   You need to update the /etc/default/grub directory after every change you make in there.

Procedure 10.2. Adding an Image to the Boot Loader Screen

1. Open the /etc/default/grub file as root.
2. Edit the following configuration variables in the file:

   GRUB_TERMINAL=gfxterm
   GRUB_BACKGROUND=path_to_the_image.png

   Supported formats are PNG, JPG, JPEG, and TGA.
3. Create a new configuration file with a background image:

   grub2-mkconfig -o /boot/grub2/grub.cfg

4. Reboot your system.

Procedure 10.3. Changing the Plymouth Theme

1. Search for the existing Plymouth themes and choose the most preferable one. Run the following command:

   # yum search plymouth-theme

   Or run the plymouth-set-default-theme --list command to view the installed themes.
   You can also install all the themes when installing all the plymouth packages. However, you will install a number of unnecessary packages as well.

   # yum install plymouth\*

2. Set the new theme as default with the plymouth-set-default-theme theme_name command.

   Example 10.3. Set "spinfinity" as the Default Theme

   You have chosen the spinfinity theme, so you run:

   # plymouth-set-default-theme spinfinity

3. Rebuild the initrd daemon after editing otherwise your theme will not show in the boot screen. Do so by running:

   # dracut -f

Procedure 10.4. Creating Your Own Theme from an Existing Theme

1. Copy an entire content of a plymouth/ directory. As a template directory, use, for example, the default theme for Red Hat Enterprise Linux 7, /usr/share/plymouth/themes/charge/charge.plymouth, which uses a two-step splash plugin (two-step is a popular boot load feature of a two phased boot process that starts with a progressing animation synced to boot time and finishes with a short, fast one-shot animation):

   [Plymouth Theme]
   Name=Charge
   Description=A theme that features the shadowy hull of my logo charge up and finally burst into full form.
   ModuleName=two-step
   
   [two-step]
   ImageDir=/usr/share/plymouth/themes/charge
   HorizontalAlignment=.5
   VerticalAlignment=.5
   Transition=none
   TransitionDuration=0.0
   BackgroundStartColor=0x202020
   BackgroundEndColor=0x202020
   

2. Save the charge.plymouth file with a new name in the /usr/share/plymouth/themes/newtheme/ directory, in the following format:

   newtheme.plymouth

3. Update the settings in your /usr/share/plymouth/themes/newtheme/newtheme.plymouth file according to your preferences, changing color, alignment, or transition.
4. Set your newtheme as default by running the following command:

   # plymouth-set-default-theme newtheme

5. Rebuild the initrd daemon after changing the theme by running the command below:

   # dracut -f

Procedure 10.6. Adding a logo to the login screen

1. Create or edit the gdm profile in /etc/dconf/profile/gdm which contains the following lines:

   user-db:user
   system-db:gdm
   file-db:/usr/share/gdm/greeter-dconf-defaults

   gdm is the name of a dconf database.
2. Create a gdm database for machine-wide settings in /etc/dconf/db/gdm.d/01-logo:

   [org/gnome/login-screen]
   logo='/usr/share/pixmaps/logo/greeter-logo.png'
   

   Replace /usr/share/pixmaps/logo/greeter-logo.png with the path to the image file you want to use as the greeter logo.
3. Update the system databases:

   # dconf update

Procedure 10.7. Displaying a Text Banner on the Login Screen

1. Create or edit the gdm profile in /etc/dconf/profile/gdm which contains the following lines:

   user-db:user
   system-db:gdm
   file-db:/usr/share/gdm/greeter-dconf-defaults

   gdm is the name of a dconf database.
2. Create a gdm database for machine-wide settings in /etc/dconf/db/gdm.d/01-banner-message:

   [org/gnome/login-screen]
   banner-message-enable=true
   banner-message-text='Type the banner message here'
   

   Note

   There is no character limit for the banner message. GNOME Shell autodetects longer stretches of text and enters two column mode. However, the banner message text cannot be read from an external file.
3. Update the system databases:

   # dconf update

Procedure 10.8. Changing the System Keyboard Layout Settings

1. Find the codes of the required language layouts in the /usr/share/X11/xkb/rules/base.lst file under the section named ! layout.
2. Use the localectl tool to change the system keyboard layout settings as follows:

   $ localectl set-x11-keymap layout

   You can specify multiple layouts as a comma-separated list. For example, to set es as the default layout, and us as the secondary layout, run the following command:

   $ localectl set-x11-keymap es,us

3. Log out to find that the defined layouts are available at the top bar on the login screen.

Procedure 10.9. Setting the org.gnome.login-screen.disable-user-list Key

1. Create or edit the gdm profile in /etc/dconf/profile/gdm which contains the following lines:

   user-db:user
   system-db:gdm
   file-db:/usr/share/gdm/greeter-dconf-defaults

   gdm is the name of a dconf database.
2. Create a gdm database for machine-wide settings in /etc/dconf/db/gdm.d/00-login-screen:

   [org/gnome/login-screen]
   # Do not show the user list
   disable-user-list=true
   

3. Update the system databases by updating the dconf utility:

   # dconf update

Procedure 10.10. Setting the Default Background

1. Create a local database for machine-wide settings in /etc/dconf/db/local.d/00-background:

   # Specify the dconf path
   [org/gnome/desktop/background]
   
   # Specify the path to the desktop background image file
   picture-uri='file:///usr/local/share/backgrounds/wallpaper.jpg'
   # Specify one of the rendering options for the background image:
   # 'none', 'wallpaper', 'centered', 'scaled', 'stretched', 'zoom', 'spanned'
   picture-options='scaled'
   # Specify the left or top color when drawing gradients or the solid color
   primary-color='000000'
   # Specify the right or bottom color when drawing gradients
   secondary-color='FFFFFF'

2. Override the user's setting to prevent the user from changing it in /etc/dconf/db/local.d/locks/background:

   # List the keys used to configure the desktop background
   /org/gnome/desktop/background/picture-uri
   /org/gnome/desktop/background/picture-options
   /org/gnome/desktop/background/primary-color
   /org/gnome/desktop/background/secondary-color

   For more information, see Section 9.5.1, “Locking Down Specific Settings”.
3. Update the system databases:

   # dconf update

4. Users must log out and back in again before the system-wide settings take effect.

1. Create a filename.xml file (there are no requirements for file names) specifying your extra background's appearance using the org.gnome.desktop.background schemas. Here is a list of the most frequently used schemas:

   Table 10.1. org.gnome.desktop.background schemas GSettings Keys

   Key Name	Possible Values	Description
   picture-options	"none", "wallpaper", "centered", "scaled", "stretched", "zoom", "spanned"	Determines how the image set by wallpaper_filename is rendered.
   color-shading-type	"horizontal", "vertical", and "solid"	How to shade the background color.
   primary-color	default: #023c88	Left or Top color when drawing gradients, or the solid color.
   secondary-color	default: #5789ca	Right or Bottom color when drawing gradients, not used for solid color.

   The full range of options is to be found in the dconf-editor GUI or gsettings command-line utility. For more information, see Section 9.3, “Browsing GSettings Values for Desktop Applications”.
2. Store the filename.xml file in the /usr/share/gnome-background-properties/ directory.

Procedure 10.11. Adding a Logo to the Screen Shield

1. Create a gdm database for machine-wide settings in /etc/dconf/db/gdm.d/01-screensaver:

   [org/gnome/desktop/screensaver]
   picture-uri='file:///opt/corp/background.jpg'
   

   Replace /opt/corp/background.jpg with the path to the image file you want to use as the Screen Shield.
   Supported formats are PNG, JPG, JPEG, and TGA. The image will be scaled if necessary to fit the screen.
2. Update the system databases:

   # dconf update

3. You must log out before the system-wide settings take effect.

Procedure 10.12. Installing an Extra Font

1. As the root user, create the /usr/local/share/fonts/ directory and copy the font into it.
   Create a subdirectory for each font-family you are installing as some fonts have multiple files for bold, italic, and so on.
2. Make sure that the font cache is updated by running the following command:

   # fc-cache /usr/local/share/fonts/

Procedure 10.13. Installing an Extra Font

1. As the root user, create your own machine-wide /etc/fonts/local.conf configuration file including the directory with fonts.

        
   <?xml version="1.0"?>
   <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
   <fontconfig>
       <dir>/PATH/TO/YOUR/DIRECTORY_NAME</dir>
   </fontconfig>
   

2. Ensure the permissions for your directory are set to 755.

   # chmod -R 755 /PATH/TO/YOUR/DIRECTORY_NAME

3. Specify the directory name when updating the font cache with the fc-cache command.

   # fc-cache DIRECTORY_NAME

Procedure 10.14. Installing an Extra Font

1. Copy the font to the ~/.local/share/fonts/ directory to install it.
2. Make sure that the font cache is updated by running the following command:

   $ fc-cache ~/.local/share/fonts

Procedure 10.15. Substituting a Font

1. Start the Fonts Tweak Tool by pressing the Super key to enter the Activities Overview, type Fonts Tweak Tool, and then press Enter.
2. Click the Font Substitutions tab.
3. Click the + button at the bottom left of the left pane, select or type the name of the font you want to substitute, and then click Add.
4. Click the + button at the bottom left of the right pane, select the name of the font you want to use to substitute for the first font, and then click Add.
5. Click Close.

Procedure 10.16. Configuring a Font Alias

1. Start the Fonts Tweak Tool by pressing the Super key to enter the Activities Overview, type Fonts Tweak Tool, and then press Enter.
2. Click the Font Aliases tab.
3. Click the + button at the bottom left of the left pane, select or type the name of the locale you want to configure the font aliases for, and then click Add.
   To configure default font aliases regardless of the used locale, select Default from the list of locales.
4. At the right pane, locate the font alias you want to override the system defaults for, and select the custom font from the drop-down list.
5. Click Close.

Procedure 10.17. Configuring Multiple Languages

1. Start the Fonts Tweak Tool by pressing the Super key to enter the Activities Overview, type Fonts Tweak Tool, and then press Enter.
2. Click the Language Ordering tab.
3. Click the + button at the bottom left of the window, select or type the name of the language you want to configure as primary, and then click Add.
4. To add another language, click the + button at the bottom left of the window, select the name of the language you want to configure as secondary, and then click Add.
   Repeat this step to add more languages.
5. Click Close.

Procedure 10.18. Changing the Font Properties

1. Start the Fonts Tweak Tool by pressing the Super key to enter the Activities Overview, type Fonts Tweak Tool, and then press Enter.
2. Click the Fonts Properties tab.
3. Click the + button at the bottom left of the window, select or type the name of the font you want to change the properties for, and then click Add.
   Repeat this step to add more fonts.
4. Change the font properties as needed.
5. Click Close.

Procedure 12.1. Example: Remove the Calculator menu item from the Accessories submenu

1. Consult the contents of the /usr/share/applications/ directory and determine a .desktop file that corresponds to the menu item you want to remove:

   $ grep -r "Name=Calculator" /usr/share/applications/
   /usr/share/applications/gcalctool.desktop:Name=Calculator

   As shown above, the Calculator menu item corresponds to the /usr/share/applications/gcalctool.desktop file.
2. Create a ~/.config/menus/gnome-applications.menu file:

   <!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
   "http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
   
   <Menu>
     <Name>Applications</Name>
     <MergeFile type="parent">/etc/xdg/menus/gnome-applications.menu</MergeFile>
   
   <!-- Removes the Calculator from the Accessories submenu -->
     <Menu>
       <Name>Accessories</Name>
       <Exclude>
         <Filename>gcalctool.desktop</Filename>
       </Exclude>
     </Menu>
   <!-- END of Calculator removal content -->
   
   </Menu>

   As shown above, the file contains a <Menu> section that specifies the name of the submenu (Accessories), the name of the .desktop file (gcalctool.desktop), and includes the <Exclude> element.

Procedure 12.2. Example: Remove the Calculator menu item from the Accessories submenu

1. Consult the contents of the /usr/share/applications/ directory and determine a .desktop file that corresponds to the menu item you want to remove:

   $ grep -r "Name=Calculator" /usr/share/applications/
   /usr/share/applications/gcalctool.desktop:Name=Calculator

   As shown above, the Calculator menu item corresponds to the /usr/share/applications/gcalctool.desktop file.
2. Edit the /etc/xdg/menus/applications.menu file and add a new <Menu> section before the final </Menu> tag at the end of that .menu file using the <Exclude> element as shown below:

   <!-- Removes the Calculator from the Accessories submenu -->
   
     <Menu>
       <Name>Accessories</Name>
       <Exclude>
         <Filename>gcalctool.desktop</Filename>
       </Exclude>
     </Menu>
   
   <!-- END of Calculator removal content -->
   
   </Menu> <!-- End Applications -->

Procedure 12.3. Adding a Custom application/x-newtype MIME Type for All Users

1. Create the /usr/share/mime/packages/application-x-newtype.xml file:

   <?xml version="1.0" encoding="UTF-8"?>
   
   <mime-info xmlns="http://www.freedesktop.org/standards/shared-mime-info">
     <mime-type type="application/x-newtype">
       <comment>new mime type</comment>
       <glob pattern="*.xyz"/>
     </mime-type>
   </mime-info>

   The sample application-x-newtype.xml file above defines a new MIME type application/x-newtype and assigns file names with the .xyz extension to that MIME type.
2. Create a new .desktop file named, for example, myapplication1.desktop, and place it in the /usr/share/applications/ directory:

   [Desktop Entry]
   Type=Application
   MimeType=application/x-newtype
   Name=My Application 1
   Exec=myapplication1 field_code

   The sample myapplication1.desktop file above associates the application/x-newtype MIME type with an application named My Application 1, which is run by the command myapplication1.
   Based on how myapplication1 gets started, choose one respective field code from Desktop Entry Specification. For example, for an application capable of opening multiple files, use:

   Exec=myapplication1 %F

3. As root, update the MIME database for your changes to take effect:

   # update-mime-database /usr/share/mime

4. As root, update the application database:

   # update-desktop-database /usr/share/applications

5. To verify that you have successfully associated *.xyz files with the application/x-newtype MIME type, first create an empty file, for example test.xyz:

   $ touch test.xyz

   Then run the gvfs-info command:

   $ gvfs-info test.xyz | grep "standard::content-type"
     standard::content-type: application/x-newtype
   

6. To verify that myapplication1.desktop has been correctly set as the default registered application for the application/x-newtype MIME type, run the gvfs-mime --query command:

   $ gvfs-mime --query application/x-newtype
   Default application for 'application/x-newtype': myapplication1.desktop
   Registered applications:
   	myapplication1.desktop
   Recommended applications:
   	myapplication1.desktop

Procedure 12.4. Adding a Custom application/x-newtype MIME Type for Individual Users

1. Create the ~/.local/share/mime/packages/application-x-newtype.xml file:

   <?xml version="1.0" encoding="UTF-8"?>
   <mime-info xmlns="http://www.freedesktop.org/standards/shared-mime-info">
     <mime-type type="application/x-newtype">
       <comment>new mime type</comment>
       <glob pattern="*.xyz"/>
     </mime-type>
   </mime-info>

   The sample application-x-newtype.xml file above defines a new MIME type application/x-newtype and assigns file names with the .xyz extension to that MIME type.
2. Create a new .desktop file named, for example, myapplication1.desktop, and place it in the ~/.local/share/applications/ directory:

   [Desktop Entry]
   Type=Application
   MimeType=application/x-newtype
   Name=My Application 1
   Exec=myapplication1 field_code

   The sample myapplication1.desktop file above associates the application/x-newtype MIME type with an application named My Application 1, which is run by the command myapplication1.
   Based on how myapplication1 gets started, choose one respective field code from Desktop Entry Specification. For example, for an application capable of opening multiple files, use:

   Exec=myapplication1 %F

3. Update the MIME database for your changes to take effect:

   $ update-mime-database ~/.local/share/mime

4. Update the application database:

   $ update-desktop-database ~/.local/share/applications

5. To verify that you have successfully associated *.xyz files with the application/x-newtype MIME type, first create an empty file, for example test.xyz:

   $ touch test.xyz

   Then run the gvfs-info command:

   $ gvfs-info test.xyz | grep "standard::content-type"
     standard::content-type: application/x-newtype
   

6. To verify that myapplication1.desktop has been correctly set as the default registered application for the application/x-newtype MIME type, run the gvfs-mime --query command:

   $ gvfs-mime --query application/x-newtype
   Default application for 'application/x-newtype': myapplication1.desktop
   Registered applications:
   	myapplication1.desktop
   Recommended applications:
   	myapplication1.desktop

Procedure 12.5. Overriding the Default Registered Application for All Users

1. Consult the /usr/share/applications/mimeapps.list file to determine the MIME types for which you want to change the default registered application. For example, the following sample of the mimeapps.list file specifies the default registered application for the text/html and application/xhtml+xml MIME types:

   [Default Applications]
   text/html=firefox.desktop
   application/xhtml+xml=firefox.desktop
   

   The default application (Firefox) is defined by specifying its corresponding .desktop file (firefox.desktop). The default location for other applications' .desktop files is /usr/share/applications/.
2. Create the /etc/xdg/mimeapps.list file. In the file, specify the MIME types and their corresponding default registered applications:

   [Default Applications]
   text/html=myapplication1.desktop
   application/xhtml+xml=myapplication2.desktop

   This sets the default registered application for the text/html MIME type to myapplication1.desktop, and the default registered application for the application/xhtml+xml MIME type to myapplication2.desktop.
   For these settings to function properly, ensure that both the myapplication1.desktop and myapplication2.desktop files are placed in the /usr/share/applications/ directory.
3. You can use the gvfs-mime query command to verify that the default registered application has been set correctly:

   $gvfs-mime query text/html
   Default application for 'text/html': myapplication1.desktop
   Registered applications:
   	myapplication1.desktop
   	firefox.desktop
   Recommended applications:
   	myapplication1.desktop
   	firefox.desktop

Procedure 12.6. Overriding the Default Registered Application for Individual Users

1. Consult the /usr/share/applications/mimeapps.list file to determine the MIME types for which you want to change the default registered application. For example, the following sample of the mimeapps.list file specifies the default registered application for the text/html and application/xhtml+xml MIME types:

   [Default Applications]
   text/html=firefox.desktop
   application/xhtml+xml=firefox.desktop
   

   The default application (Firefox) is defined by specifying its corresponding .desktop file (firefox.desktop). The system default location for other applications' .desktop files is /usr/share/applications/. Individual users' .desktop files can be stored in ~/.local/share/applications/.
2. Create the ~/.local/share/applications/mimeapps.list file. In the file, specify the MIME types and their corresponding default registered applications:

   [Default Applications]
   text/html=myapplication1.desktop
   application/xhtml+xml=myapplication2.desktop

   This sets the default registered application for the text/html MIME type to myapplication1.desktop, and the default registered application for the application/xhtml+xml MIME type to myapplication2.desktop.
   For these settings to function properly, ensure that both the myapplication1.desktop and myapplication2.desktop files are placed in the /usr/share/applications/ directory.
3. You can use the gvfs-mime --query command to verify that the default registered application has been set correctly:

   $gvfs-mime --query text/html
   Default application for 'text/html': myapplication1.desktop
   Registered applications:
   	myapplication1.desktop
   	firefox.desktop
   Recommended applications:
   	myapplication1.desktop
   	firefox.desktop

1. Create a local database for machine-wide settings in /etc/dconf/db/local.d/00-lockdown:

   [org/gnome/desktop/lockdown]
   # Disable command-line access
   disable-command-line=true

2. Override the user's setting and prevent the user from changing it in /etc/dconf/db/local.d/locks/lockdown:

   # Lock the disabled command-line access
   /org/gnome/desktop/lockdown
   

3. Update the system databases:

   # dconf update

4. Users must log out and back in again before the system-wide settings take effect.

Procedure 13.4. Disabling Access to Virtual Terminals

1. Create or edit an X configuration file in the /etc/X11/xorg.conf.d/ directory:

   Note

   By convention, these host-specific configuration file names start with two digits and a hyphen and always have the .conf extension. Thus, the following file name can be /etc/X11/xorg.conf.d/10-xorg.conf.

   Section "Serverflags"
   
   Option "DontVTSwitch" "yes"
   
   EndSection

2. Restart the X server for your changes to take effect.

Procedure 14.3. Enabling smart card authentication using dconf editor GUI

1. Uncheck the box for the org.gnome.login-screen enable-password-authentication dcof key.
2. Check the box for the org.gnome.login-screen enable-smartcard-authentication dcof key.

Procedure 14.4. Enabling smart card authentication using dconf-tool

1. Create a keyfile in the /etc/dconf/db/gdm.d directory.
2. Add the following content to this keyfile:

   [org/gnome/login-screen]
   enable-password-authentication='false'
   enable-smartcard-authentication='true'
   

3. Update the system dconf databases:

   # dconf update

Procedure 14.5. Specifying a Default Session for a User

1. Make sure that you have the gnome-session-xsession package installed by running the following command:

   # yum install gnome-session-xsession

2. Navigate to the /usr/share/xsessions directory where you can find .desktop files for each of the available sessions. Consult the contents of the .desktop files to determine the session you want to use.
3. To specify a default session for a user, update the user's account service in the /var/lib/AccountsService/users/username file:

   [User]
   Language=
   XSession=gnome

   In this sample, GNOME has been set as the default session, using the /usr/share/xsessions/gnome.desktop file. Note that the system default in Red Hat Enterprise Linux 7 is GNOME Classic (the /usr/share/xsessions/gnome-classic.desktop file).

1. Create a .desktop file in /etc/X11/sessions/new-session.desktop. Make sure that the file specifies the following entries:

   [Desktop Entry]
   Encoding=UTF-8
   Type=Application
   Name=Custom Session
   Comment=This is our custom session
   Exec=gnome-session --session=new-session

   The Exec entry specifies the command, possibly with arguments, to execute. You can run the custom session with the gnome-session --session=new-session command.
   For more information on the parameters that you can use with gnome-session, see the gnome-session(1) man page.
2. Create a custom session file in /usr/share/gnome-session/sessions/new-session.session where you can specify the name and required components for the session:

   [GNOME Session]
   Name=Custom Session
   RequiredComponents=gnome-shell-classic;gnome-settings-daemon;

   Note that any item that you specify in RequiredComponents needs to have its corresponding .desktop file in /usr/share/applications/.

Procedure 14.6. Viewing User Session Logs

1. Determine your user ID (uid) by running the following command:

   $ id --user
   1000

2. View the journal logs for the user ID determined above:

   $ journalctl _UID=1000

Procedure 14.7. Adding an Autostart (Startup) Application for All Users

1. Create a .desktop file in the /etc/xdg/autostart/ directory:

   [Desktop Entry]
   Type=Application
   Name=Files
   Exec=nautilus -n
   OnlyShowIn=GNOME;
   AutostartCondition=GSettings org.gnome.desktop.background show-desktop-icons

2. Replace Files with the name of the application.
3. Replace nautilus -n with the command you wish to use to run the application.
4. You can use the AutostartCondition key to check for a value of a GSettings key.
   The session manager runs the application automatically if the key's value is true. If the key's value changes in the running session, the session manager starts or stops the application, depending on what the previous value for the key was.

Procedure 14.8. Setting Automatic Logout for a Mains Powered Machine

1. Create a local database for machine-wide settings in /etc/dconf/db/local.d/00-autologout:

   [org/gnome/settings-daemon/plugins/power]
   # Set the timeout to 900 seconds when on mains power
   sleep-inactive-ac-timeout=900
   # Set action after timeout to be logout when on mains power
   sleep-inactive-ac-type='logout'

2. Override the user's setting and prevent the user from changing it in /etc/dconf/db/local.d/locks/autologout:

   # Lock automatic logout settings
   /org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
   /org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
   

3. Update the system databases:

   # dconf update

4. Users must log out and back in again before the system-wide settings take effect.

Procedure 14.9. Enabling the Screensaver and Locking the Screen

1. Create a local database for system-wide settings in /etc/dconf/db/local.d/00-screensaver:

   [org/gnome/desktop/session]
   # Set the lock time out to 180 seconds before the session is considered idle
   idle-delay=uint32 180
   [org/gnome/desktop/screensaver]
   # Set this to true to lock the screen when the screensaver activates
   lock-enabled=true
   # Set the lock timeout to 180 seconds after the screensaver has been activated
   lock-delay=uint32 180

   You must include the uint32 along with the integer key values as shown.
2. Override the user's setting and prevent the user from changing it in the /etc/dconf/db/local.d/locks/screensaver file:

   # Lock desktop screensaver settings
   /org/gnome/desktop/session/idle-delay
   /org/gnome/desktop/screensaver/lock-enabled
   /org/gnome/desktop/screensaver/lock-delay
   

3. Update the system databases:

   # dconf update

4. Users must log out and back in again before the system-wide settings take effect.

Procedure 14.10. Making a Screencast

1. To start the recording, press Ctrl+Alt+Shift+R.
   When the recorder is capturing the screen activity, it displays a red circle in the bottom-right corner of the screen.
2. To stop the recording, press Ctrl+Alt+Shift+R. The red circle in the bottom-right corner of the screen disappears.
3. Navigate to the ~/Videos folder where you can find the recorded video with a file name that starts with Screencast and includes the date and time of the recording.

1. Find the UID (system user ID) for the /run/user/UID/gvfs/ path by running the id command (the gvfsd-fuse daemon requires a path it is supposed to expose its services at).
   Or, when the /run/user/UID/gvfs/ path is unavailable, gvfsd-fuse uses a .gvfs path in your home directory.
2. Start the gvfsd-fuse daemon by running the /usr/libexec/gvfsd-fuse -f /run/user/UID/gvfs command.
3. Now, the VFS mount is available and you can manually browse for the path in your application.

1. Open Disks by pressing the Super key to enter the Activities Overview, typing Disks, and then pressing Enter.
2. In the Volumes actions menu, click Edit Mount Options....
3. Click Show in user interface.
4. Confirm by clicking OK.

1. Open Disks by pressing the Super key to enter the Activities Overview, typing Disks, and then pressing Enter.
2. In the Volumes actions menu, click Edit Mount Options....
3. Uncheck Show in user interface and confirm by clicking OK.

Procedure 16.1. How to add tablet descriptions

1. Use the libwacom-list-local-devices tool to list all local devices recognized by libwacom.
   If your device is not listed, but it is available as an event device in the kernel (see /proc/bus/input/devices) and in the X session (see xinput list), the device is missing from libwacom's database.
2. Create a new tablet definition file. Use data/wacom.example below and edit the respective lines.

   Note

   The new .tablet file may already be available, so check the upstream repository first at https://sourceforge.net/p/linuxwacom/libwacom/ci/master/tree/. If you find your tablet model on the list, it is sufficient to copy the file to the local machine.

   # Example model file description for a tablet
   [Device]
   
   # The product is the product name announced by the kernel
   Product=Intuos 4 WL 6x9
   
   # Vendor name of this tablet
   Vendor=Wacom
   
   # DeviceMatch includes the bus (usb, serial), the vendor ID and the actual
   # product ID 
   DeviceMatch=usb:056a:00bc
   
   # Class of the tablet. Valid classes include Intuos3, Intuos4, Graphire, Bamboo, Cintiq
   Class=Intuos4
   
   # Exact model of the tablet, not including the size.
   Model=Intuos 4 Wireless
   
   # Width in inches, as advertised by the manufacturer
   Width=9
   
   # Height in inches, as advertised by the manufacturer
   Height=6
   
   # Optional features that this tablet supports
   # Some features are dependent on the actual tool used, e.g. not all styli
   # have an eraser and some styli have additional custom axes (e.g. the
   # airbrush pen). These features describe those available on the tablet.
   #
   # Features not set in a file default to false/0
   
   [Features]
   # This tablet supports styli (and erasers, if present on the actual stylus)
   Stylus=true
   
   # This tablet supports touch.
   Touch=false
   
   # This tablet has a touch ring (Intuos4 and Cintiq 24HD)
   Ring=true
   # This tablet has a second touch ring (Cintiq 24HD)
   Ring2=false
   
   # This tablet has a vertical/horizontal scroll strip
   VStrip=false
   HStrip=false
   
   # Number of buttons on the tablet
   Buttons=9
   
   # This tablet is built-in (most serial tablets, Cintiqs) 
   BuiltIn=false

3. Add and install the new file with the .tablet suffix:

   cp the-new-file.tablet /usr/share/libwacom/

   Once installed, the tablet is part of libwacom's database. The tablet is then available through libwacom-list-local-devices.
4. Create a new file /etc/udev/rules/99-libwacom-override.rules with the following content so that your settings are not overwritten:

   ACTION!="add|change", GOTO="libwacom_end"
   KERNEL!="event[0-9]*", GOTO="libwacom_end"
   
   [new tablet match entries go here]
   
   LABEL="libwacom_end"
   

5. Reboot your system.