[gnome-user-docs] General updates to system-admin-guide
- From: Petr Kovář <pmkovar src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-user-docs] General updates to system-admin-guide
- Date: Sun, 17 Feb 2019 18:09:26 +0000 (UTC)
commit 327191af442c241a1995c0f85baa69f5bb5821cf
Author: Petr Kovar <pkovar redhat com>
Date: Sun Feb 10 19:30:22 2019 +0100
General updates to system-admin-guide
Update and reorg dconf pages. Fixes #4, fixes #3.
Update and re-include stub pages, reuse content from old patches
in BZ. Fixes #11, fixes #15, fixes #16.
Add missing authors & editors.
Enjoy.
...tions.page.stub => autostart-applications.page} | 9 +-
system-admin-guide/C/backgrounds-extra.page | 141 +++++++++++++++++++++
system-admin-guide/C/backgrounds-extra.page.stub | 126 ------------------
system-admin-guide/C/dconf-custom-defaults.page | 30 +++--
system-admin-guide/C/dconf-keyfiles.page | 35 ++---
system-admin-guide/C/dconf-lockdown.page | 44 +++----
system-admin-guide/C/dconf-nfs-home.page | 3 +-
system-admin-guide/C/dconf-profiles.page | 81 +++++++++---
system-admin-guide/C/dconf.page | 54 ++------
system-admin-guide/C/desktop-lockscreen.page | 36 +++---
system-admin-guide/C/desktop-shield.page | 9 +-
system-admin-guide/C/extensions-enable.page | 16 ++-
system-admin-guide/C/extensions-lockdown.page | 1 +
system-admin-guide/C/gsettings-browse.page | 70 ++++++++++
system-admin-guide/C/gsettings-browse.page.stub | 57 ---------
...ose-key.page.stub => keyboard-compose-key.page} | 27 ++--
system-admin-guide/C/legal.xml | 4 +-
system-admin-guide/C/lockdown-command-line.page | 46 +++++--
system-admin-guide/C/lockdown-logout.page | 77 +++++++++++
system-admin-guide/C/lockdown-online-accounts.page | 88 +++++++------
system-admin-guide/C/lockdown-single-app-mode.page | 116 +++++++++++++++++
system-admin-guide/C/login-banner.page | 9 +-
system-admin-guide/C/login-fingerprint.page | 2 +-
.../C/mime-types-application-user.page | 32 +++--
system-admin-guide/C/mime-types-application.page | 33 +++--
system-admin-guide/C/network-printer-config.page | 6 +-
system-admin-guide/C/overrides.page | 37 +++---
system-admin-guide/C/processes.page | 32 +++--
system-admin-guide/C/session-custom.page | 6 +-
system-admin-guide/C/session-debug.page | 4 +-
system-admin-guide/Makefile.am | 6 +
31 files changed, 784 insertions(+), 453 deletions(-)
---
diff --git a/system-admin-guide/C/autostart-applications.page.stub
b/system-admin-guide/C/autostart-applications.page
similarity index 87%
rename from system-admin-guide/C/autostart-applications.page.stub
rename to system-admin-guide/C/autostart-applications.page
index 08e4a303..b9a03a21 100644
--- a/system-admin-guide/C/autostart-applications.page.stub
+++ b/system-admin-guide/C/autostart-applications.page
@@ -3,8 +3,8 @@
id="autostart-applications">
<info>
- <link type="guide" xref="software#application" />
- <revision pkgversion="3.12" date="2014-01-27" status="review"/>
+ <link type="guide" xref="software#management" />
+ <revision pkgversion="3.30" date="2019-02-08" status="draft"/>
<credit type="author copyright">
<name>Jana Svarova</name>
@@ -17,6 +17,8 @@
<years>2014</years>
</credit>
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+
<desc>How can I add an autostart application for all users?</desc>
</info>
@@ -26,9 +28,6 @@
you need to create a <file>.desktop</file> file for that application in the
<file>/etc/xdg/autostart/</file> directory.</p>
- <p>To manage autostart (startup) applications for individual users, use the
- <app>gnome-session-properties</app> application.</p>
-
<steps>
<title>To add an autostart application for all users:</title>
<item><p>Create a <file>.desktop</file> file in the
diff --git a/system-admin-guide/C/backgrounds-extra.page b/system-admin-guide/C/backgrounds-extra.page
new file mode 100644
index 00000000..a01918b2
--- /dev/null
+++ b/system-admin-guide/C/backgrounds-extra.page
@@ -0,0 +1,141 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="backgrounds-extra">
+
+ <info>
+ <link type="guide" xref="appearance" />
+ <revision pkgversion="3.30" date="2019-02-08" status="draft"/>
+
+ <credit type="author copyright">
+ <name>Matthias Clasen</name>
+ <email>matthias clasen gmail com</email>
+ <years>2012</years>
+ </credit>
+ <credit type="editor">
+ <name>Jana Svarova</name>
+ <email>jana svarova gmail com</email>
+ <years>2013</years>
+ </credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
+
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+
+ <desc>How do I make extra backgrounds available to my users?</desc>
+ </info>
+
+ <title>Add extra backgrounds</title>
+
+ <p>You can make extra backgrounds available to users on your system by
+ following the steps below.</p>
+
+ <steps>
+ <title>Set extra backgrounds</title>
+ <item>
+ <p>Create an XML file, for example <file><var>filename</var>.xml</file>.
+ In this file, use keys from the <sys>org.gnome.desktop.background</sys>
+ GSettings schema to specify extra backgrounds and their appearance.</p>
+
+ <p>Below is a list of the most frequently used keys:</p>
+
+ <table frame="top bottom" rules="all" shade="rows">
+ <title>org.gnome.desktop.background schemas GSettings keys</title>
+ <tbody>
+ <tr>
+ <td><p>Key name</p></td>
+ <td><p>Possible values</p></td>
+ <td><p>Description</p></td>
+ </tr>
+ <tr>
+ <td><p>picture-options</p></td>
+ <td><p>"none", "wallpaper", "centered", "scaled", "stretched", "zoom", "spanned"</p></td>
+ <td><p>Determines how the image set by <var>wallpaper_filename</var> is rendered.</p></td>
+ </tr>
+ <tr>
+ <td><p>color-shading-type</p></td>
+ <td><p>"horizontal", "vertical", and "solid"</p></td>
+ <td><p>How to shade the background color.</p></td>
+ </tr>
+ <tr>
+ <td><p>primary-color</p></td>
+ <td><p>default: #023c88</p></td>
+ <td><p>Left or top color when drawing gradients, or the solid color.</p></td>
+ </tr>
+ <tr>
+ <td><p>secondary-color</p></td>
+ <td><p>default: #5789ca</p></td>
+ <td><p>Right or bottom color when drawing gradients, not used for solid color.</p></td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>You can view a complete list of <sys>org.gnome.desktop.background</sys>
+ keys and possible values using <app>dconf-editor</app> or the <cmd>gsettings</cmd>
+ command-line utility. See <link xref="gsettings-browse"/> for more information.
+ </p>
+ <p>Below is a sample <file><var>filename</var>.xml</file> file:</p>
+
+<code><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE wallpapers SYSTEM "gnome-wp-list.dtd">
+<wallpapers>
+ <wallpaper deleted="false">
+ <name>Company Background</name>
+ <name xml:lang="de">Firmenhintergrund</name>
+ <filename>/usr/local/share/backgrounds/company-wallpaper.jpg</filename>
+ <options>zoom</options>
+ <shade_type>solid</shade_type>
+ <pcolor>#ffffff</pcolor>
+ <scolor>#000000</scolor>
+ </wallpaper>
+</wallpapers>
+]]>
+</code>
+
+ </item>
+ <item>
+ <p>Place the <file><var>filename</var>.xml</file> file in the
+ <file>/usr/share/gnome-background-properties/</file> directory.</p>
+ <p>Users will have the extra backgrounds available for configuration from
+ <guiseq><gui>Settings</gui> <gui>Background</gui></guiseq>.</p>
+ </item>
+ </steps>
+
+
+ <section id="backgrounds-extra-two-wallpapers">
+ <title>Specify multiple backgrounds</title>
+ <p>In one configuration file, you can specify multiple
+ <code><wallpaper></code> elements to add more backgrounds.</p>
+ <p>See the following example with two <code><wallpaper></code> elements,
+ adding two different backgrounds:</p>
+
+<code><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE wallpapers SYSTEM "gnome-wp-list.dtd">
+<wallpapers>
+ <wallpaper deleted="false">
+ <name>Company Background</name>
+ <name xml:lang="de">Firmenhintergrund</name>
+ <filename>/usr/local/share/backgrounds/company-wallpaper.jpg</filename>
+ <options>zoom</options>
+ <shade_type>solid</shade_type>
+ <pcolor>#ffffff</pcolor>
+ <scolor>#000000</scolor>
+ </wallpaper>
+ <wallpaper deleted="false">
+ <name>Company Background 2</name>
+ <name xml:lang="de">Firmenhintergrund 2</name>
+ <filename>/usr/local/share/backgrounds/company-wallpaper-2.jpg</filename>
+ <options>zoom</options>
+ <shade_type>solid</shade_type>
+ <pcolor>#ff0000</pcolor>
+ <scolor>#00ffff</scolor>
+ </wallpaper>
+</wallpapers>
+]]></code>
+
+</section>
+</page>
diff --git a/system-admin-guide/C/dconf-custom-defaults.page b/system-admin-guide/C/dconf-custom-defaults.page
index 3d2fa1fa..0f7d142a 100644
--- a/system-admin-guide/C/dconf-custom-defaults.page
+++ b/system-admin-guide/C/dconf-custom-defaults.page
@@ -8,7 +8,7 @@
<link type="seealso" xref="dconf-profiles" />
<link type="seealso" xref="dconf-lockdown" />
<link type="seealso" xref="dconf" />
- <revision pkgversion="3.6" version="0.1" date="2012-05-21" status="draft"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="draft"/>
<credit type="author copyright">
<name>Ryan Lortie</name>
@@ -35,6 +35,11 @@
<email>kittykat3756 gmail com</email>
<years>2013</years>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
@@ -45,8 +50,6 @@
<title>Custom default values for system settings</title>
- <!-- TODO: reveiw against dconf-lockdown.page -->
-
<p>System-wide default settings can be set by providing a default for a key
in a <sys its:translate="no">dconf</sys> profile. These defaults can be
overridden by the user.</p>
@@ -67,13 +70,15 @@
</comment>
<steps>
- <title>An example demonstrating how to set the default background</title>
+ <title>An example setting the default background</title>
<item>
<p>Create the <file its:translate="no">user</file> profile:</p>
<listing its:translate="no">
<title><file>/etc/dconf/profile/user</file></title>
- <code>user-db:user
-system-db:local</code>
+<code>
+user-db:user
+system-db:local
+</code>
</listing>
<p><input its:translate="no">local</input> is the name of a
<sys its:translate="no">dconf</sys> database.</p>
@@ -83,14 +88,16 @@ system-db:local</code>
database which contains the default settings:</p>
<listing its:translate="no">
<title><file>/etc/dconf/db/local.d/01-background</file></title>
-<code># <span its:translate="yes">dconf path</span>
+<code>
+# <span its:translate="yes">dconf path</span>
[org/gnome/desktop/background]
# <span its:translate="yes">dconf key names and their corresponding values</span>
picture-uri='file:///usr/local/share/backgrounds/wallpaper.jpg'
picture-options='scaled'
primary-color='000000'
-secondary-color='FFFFFF'</code>
+secondary-color='FFFFFF'
+</code>
</listing>
</item>
<include href="dconf-snippets.xml"
@@ -104,6 +111,13 @@ secondary-color='FFFFFF'</code>
will be applied.</p>
</note>
+ <p>If you want to avoid creating the <sys its:translate="no">user</sys>
+ profile, you can use the <cmd>dconf</cmd> command-line utility to read and
+ write individual values or entire directories from and to a
+ <sys its:translate="no">dconf</sys> database. For more information, see the
+ <link its:translate="no" href="man:dconf"><cmd>dconf</cmd>(1)</link> man
+ page.</p>
+
</section>
</page>
diff --git a/system-admin-guide/C/dconf-keyfiles.page b/system-admin-guide/C/dconf-keyfiles.page
index 94a65251..a3a9bb43 100644
--- a/system-admin-guide/C/dconf-keyfiles.page
+++ b/system-admin-guide/C/dconf-keyfiles.page
@@ -5,8 +5,9 @@
<info>
<link type="guide" xref="setup" />
-<!-- <link type="seealso" xref="dconf-profiles" />-->
- <revision pkgversion="3.9" date="2013-08-06" status="stub"/>
+ <link type="seealso" xref="dconf" />
+ <link type="seealso" xref="dconf-profiles" />
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author copyright">
<name>Ryan Lortie</name>
@@ -17,6 +18,11 @@
<name>Aruna Sankaranarayanan</name>
<email>aruna evam gmail com</email>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
@@ -26,19 +32,6 @@
<title>Control system settings with keyfiles</title>
- <comment>
- <cite date="2013-08-06" href="mailto:mdhillca gmail com">Michael Hill</cite>
- <p>Separate page incorporating description from dconf.page.stub and
- paragraph from dconf-favorite-applications#all-users, but including an
- example?</p>
-
- <p>To support the ability to configure the system with a text editor,
- <sys its:translate="no">dconf</sys> has introduced
- <em>keyfile directories</em>. For any given system database, a corresponding
- directory can be created (with ".d" added to the filename, for example
- <file>/etc/dconf/db/local.d</file>).</p>
- </comment>
-
<p>System database files, located in
<file its:translate="no">/etc/dconf/db</file>, cannot be edited because
they are written in GVDB format. In order to change system settings using a
@@ -73,8 +66,18 @@ picture-uri='file:///usr/local/rupert-corp/company-wallpaper.jpeg'
recent than the one on the database file,
<sys its:translate="no">dconf</sys> regenerates the
<code>system-db</code> file and sends a notification to the system
- <sys>Dbus</sys>, which in turn notifies all running applications to
+ <sys>D-Bus</sys>, which in turn notifies all running applications to
reread their settings.</p>
</note>
+ <p>The group name in the keyfile references a
+ <link href="https://developer.gnome.org/GSettings/";>GSettings schema ID</link>.
+ For example, <code>org/gnome/desktop/background</code> references the
+ schema <code>org.gnome.desktop.background</code>, which contains the key
+ <code>picture-uri</code>.</p>
+
+ <p>The values under a group are expected in
+ <link href="https://developer.gnome.org/glib/stable/gvariant-text.html";>serialized
+ GVariant form</link>.</p>
+
</page>
diff --git a/system-admin-guide/C/dconf-lockdown.page b/system-admin-guide/C/dconf-lockdown.page
index b7eb552e..2a0d12c3 100644
--- a/system-admin-guide/C/dconf-lockdown.page
+++ b/system-admin-guide/C/dconf-lockdown.page
@@ -6,10 +6,9 @@
<info>
<link type="guide" xref="user-settings#lockdown" />
<link type="guide" xref="setup" />
-<!-- <link type="seealso" xref="dconf-profiles" />-->
- <revision version="0.1" date="2012-05-21" status="review"/>
- <revision pkgversion="3.8" date="2013-04-26" status="review"/>
- <revision pkgversion="3.15" date="2015-02-13" status="review"/>
+ <link type="seealso" xref="dconf" />
+ <link type="seealso" xref="dconf-profiles" />
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author copyright">
<name>Ryan Lortie</name>
@@ -21,6 +20,11 @@
<email>kittykat3756 gmail com</email>
<years>2013, 2015</years>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
@@ -30,22 +34,24 @@
<title>Lock down specific settings</title>
- <!-- TODO: reveiw against dconf-custom-defaults.page -->
+ <p>By using the lockdown mode in dconf, you can prevent users from changing
+ specific settings. Without locking down the system settings, user settings
+ take precedence over the system settings.</p>
- <p>To <em>lock down</em> a <sys its:translate="no">dconf</sys> key, you will
- need to create a <file its:translate="no">locks</file> subdirectory in the
- keyfile directory. The files inside this directory contain a list of keys to
- lock. Just as with the
- <!--<link xref="dconf-keyfiles">-->keyfiles<!--</link>-->, you may add any
- number of files to this directory. Here is an example of what one might look
- like:</p>
+ <p>To <em>lock down</em> a <sys its:translate="no">dconf</sys> key or subpath,
+ you will need to create a <file its:translate="no">locks</file> subdirectory
+ in the keyfile directory. The files inside this directory contain a list of
+ keys or subpaths to lock. Just as with the <link xref="dconf-keyfiles">keyfiles</link>,
+ you may add any number of files to this directory.</p>
<steps>
<title>Lock a setting</title>
<item>
- <p>Before you can lock down a key, you need to set it. This example shows
- how to lock <link xref="desktop-background">a background setting</link>
- once it has been set. At this point, you should have
+ <p>Before you can lock down a key or subpath, you need to set it. This
+ example shows how to lock <link xref="desktop-background">a background
+ setting</link> once it has been set.</p>
+
+ <p>At this point, you should have
<link xref="dconf-profiles">a <sys>user</sys> profile</link> and
<link xref="dconf-keyfiles">a keyfile</link> with the settings that you
want to lock down.</p>
@@ -57,7 +63,7 @@
<item>
<p>Create a file in the
<file its:translate="no">/etc/dconf/db/local.d/locks/</file> directory
- and list one key per line. For example, create
+ and list one key or subpath per line. For example, create
<file its:translate="no">/etc/dconf/db/local.d/locks/00_default-wallpaper</file>:</p>
<code its:translate="no">
# <span its:translate="yes">prevent changes to the background</span>
@@ -72,10 +78,4 @@
xmlns="http://www.w3.org/2001/XInclude"/>
</steps>
- <note>
- <p>As of <app its:translate="no">dconf</app> 0.7.4, lockdown is only
- supported on a per-key basis for performance reasons; you may not yet lock
- entire subpaths. There are plans to address this in future releases.</p>
- </note>
-
</page>
diff --git a/system-admin-guide/C/dconf-nfs-home.page b/system-admin-guide/C/dconf-nfs-home.page
index 7bfbebaf..0e22d9bd 100644
--- a/system-admin-guide/C/dconf-nfs-home.page
+++ b/system-admin-guide/C/dconf-nfs-home.page
@@ -5,7 +5,8 @@
<info>
<link type="guide" xref="setup" />
- <link type="guide" xref="login#management" />
+ <link type="seealso" xref="dconf-profiles" />
+ <link type="seealso" xref="dconf-custom-defaults" />
<revision version="0.1" date="2013-03-19" status="draft"/>
<revision pkgversion="3.8" date="2013-05-09" status="review"/>
<revision pkgversion="3.12" date="2014-06-17" status="review"/>
diff --git a/system-admin-guide/C/dconf-profiles.page b/system-admin-guide/C/dconf-profiles.page
index 01a537a7..e42c2a5d 100644
--- a/system-admin-guide/C/dconf-profiles.page
+++ b/system-admin-guide/C/dconf-profiles.page
@@ -1,4 +1,5 @@
<page xmlns="http://projectmallard.org/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
type="topic" style="task"
id="dconf-profiles">
@@ -6,45 +7,87 @@
<link type="guide" xref="setup" />
<link type="seealso" xref="dconf-custom-defaults" />
<link type="seealso" xref="dconf" />
- <revision version="0.1" date="2013-03-25" status="draft"/>
-
+ <revision pkgversion="3.30" date="2019-02-08" status="incomplete"/>
+
<credit type="author copyright">
<name>Ryan Lortie</name>
<email>desrt desrt ca</email>
<years>2012</years>
</credit>
-
<credit type="editor">
<name>Jana Švárová</name>
<email>jana svarova gmail com</email>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
- <desc>This page gives detailed information about profile selection.</desc>
+ <desc>Detailed information about profile and profile selection.</desc>
</info>
- <title>Select a profile</title>
-
- <p>On startup, <sys>dconf</sys> consults the DCONF_PROFILE environment
- variable. If set, <sys>dconf</sys> attempts to open the named profile and
- aborts if that fails. If the environment variable is not set,
- <sys>dconf</sys> attempts to open the profile named “user”. If that
- fails, it will fall back to an internal hard-wired configuration.</p>
+ <title>Profiles</title>
+
+ <p>A <em>profile</em> is a list of configuration databases. The first
+ database in a profile is the write-to database and the remaining databases
+ are read-only. Each of the system databases is generated from a keyfile
+ directory. Each keyfile directory contains one or more keyfiles. Each keyfile
+ contains at least one dconf path and one or more keys and the corresponding
+ values.</p>
+
+ <p>Key pairs which are set in a <sys>dconf</sys> <em>profile</em> will
+ override the default settings unless there is a problem with the value that
+ you have set.</p>
+
+ <p>You will usually want your <sys>dconf</sys> profile to consist of a
+ <em>user database</em> and at least one system database. The profile must
+ list one database per line.</p>
+
+ <p>The first line in a profile is the database that changes are written to. It
+ is usually <code>user-db:<input>user</input></code>. <input>user</input> is
+ the name of the user database which can normally be found in
+ <file>~/.config/dconf</file>.</p>
- <p>Each line in a profile specifies one <sys>dconf</sys> database. The first
- line indicates the database used to write changes, and the remaining lines
- indicate read-only databases. Here is an example:</p>
-<code>
+ <p>A <code>system-db</code> line specifies a system database. These databases
+ are found in <file>/etc/dconf/db/</file>.</p>
+
+ <example>
+ <listing>
+ <title>Sample profile</title>
+<code its:translate="no">
user-db:user
-system-db:local
-system-db:site
+system-db:<input>local</input>
+system-db:<input>site</input>
</code>
+ </listing>
+ </example>
+
+ <!-- TODO: explain the profile syntax (maybe new page) -->
+ <!--TODO: explain local and site -->
-<note style="important">
+ <note style="important">
<p>The <sys>dconf</sys> profile for a session is determined at login, so users
will have to log out and log in to apply a new <sys>dconf</sys> user profile
to their session.</p>
-</note>
+ </note>
+
+ <section id="dconf-profiles">
+
+ <title>Select a profile</title>
+
+ <p>On startup, <sys>dconf</sys> consults the <sys>DCONF_PROFILE</sys>
+ environment variable. The variable can specify a relative path to a file in
+ <file>/etc/dconf/profile/</file>, or an absolute path, for example, to the
+ user's home directory.</p>
+
+ <p>If the environment variable is set, <sys>dconf</sys> attempts to open the
+ named profile and aborts if that fails. If the variable is not set,
+ <sys>dconf</sys> attempts to open the profile named “user”. If that
+ fails, it will fall back to an internal hard-wired configuration.</p>
+
+ </section>
</page>
diff --git a/system-admin-guide/C/dconf.page b/system-admin-guide/C/dconf.page
index 420bce63..a46fb8b9 100644
--- a/system-admin-guide/C/dconf.page
+++ b/system-admin-guide/C/dconf.page
@@ -5,8 +5,7 @@
<info>
<link type="guide" xref="setup" />
- <revision pkgversion="3.8" date="2013-08-08" status="incomplete"/>
- <revision pkgversion="3.14" date="2014-06-17" status="incomplete"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="incomplete"/>
<credit type="author copyright">
<name>Ekaterina Gerasimova</name>
@@ -23,6 +22,11 @@
<email>jcampbell gnome org</email>
<years>2014</years>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
@@ -39,7 +43,7 @@
<p>To give you an idea of the power of <sys>dconf</sys> within GNOME, a
<sys>dconf</sys> key exists for most every setting that a user can click on
in the GNOME desktop or in any GNOME application. In addition to this, there
- are some system and application settings that can’t even be changed from
+ are some system and application settings that cannot even be changed from
within the user interface, but which <em>can</em> be changed by using
<sys>dconf</sys>.</p>
@@ -47,47 +51,7 @@
will help you to customize GNOME and GNOME-based applications to best suit
the needs of your particular environment.</p>
- <!-- TODO: changes are written to the first database in the list, but
- multiple databases can be writable. -->
- <p>A <em>profile</em> is a list of configuration databases. The first
- database in a profile is the write-to database and the remaining databases
- are read-only. Each of the system databases is generated from a key file
- directory. Each key file directory contains one or more key files. Each key
- file contains at least one dconf path and one or more keys and the
- corresponding values.</p>
-
- <p>Key pairs which are set in a <sys>dconf</sys> <em>profile</em> will
- override the default settings unless there is a problem with the value that
- you have set.</p>
-
- <!-- TODO: databases -->
- <p></p>
-
-<section id="profile">
- <!-- TODO: explain the profile syntax (maybe new page) -->
- <title>Profiles</title>
- <p>You will usually want your <sys>dconf</sys> profile to consist of a
- <em>user database</em> and at least one system database. The profile must
- list one database per line.</p>
- <p>The first line in a profile is the database that changes are written to. It
- is usually <code>user-db:<input>user</input></code>. <input>user</input> is
- the name of the user database which can normally be found in
- <file>~/.config/dconf</file>.</p>
- <example>
- <listing>
- <title>Sample profile</title>
- <code its:translate="no">user-db:user
-system-db:<input>local</input>
-system-db:<input>site</input></code>
- </listing>
- </example>
- <!--TODO: explain local and site -->
-</section>
-
-<!--section id="key-file">
- < TODO: link to dconf-keyfiles.page? >
- <p></p>
-
-</section-->
+ <p>Users can override the customized defaults with their own settings, unless
+ the administrator locks these defaults to prevent overriding.</p>
</page>
diff --git a/system-admin-guide/C/desktop-lockscreen.page b/system-admin-guide/C/desktop-lockscreen.page
index 8e4c76c5..7a7ed825 100644
--- a/system-admin-guide/C/desktop-lockscreen.page
+++ b/system-admin-guide/C/desktop-lockscreen.page
@@ -7,22 +7,25 @@
<link type="guide" xref="appearance" />
<link type="seealso" xref="dconf-profiles" />
<link type="seealso" xref="dconf-lockdown" />
- <revision pkgversion="3.8" date="2013-08-08" status="review"/>
- <revision pkgversion="3.14" date="2014-06-18" status="final"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author copyright">
<name>Jana Svarova</name>
<email>jana svarova gmail com</email>
<years>2013</years>
</credit>
-
<credit type="editor">
<name>Shaun McCance</name>
<email>shaunm gnome org</email>
<years>2014</years>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
- <desc>Make the screen automatically lock so the user must
+ <desc>Make the screen automatically lock, so the user must
enter a password after being idle.</desc>
</info>
@@ -36,30 +39,28 @@
<steps>
<title>Enable automatic screen lock</title>
<include href="dconf-snippets.xml"
- xpointer="xpointer(/*/*[@xml:id='dconf-profile-user'])"
- xmlns="http://www.w3.org/2001/XInclude"/>
+ xpointer="xpointer(/*/*[@xml:id='dconf-profile-user'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
<include href="dconf-snippets.xml"
- xpointer="xpointer(/*/*[@xml:id='dconf-profile-user-dir'])"
- xmlns="http://www.w3.org/2001/XInclude"/>
+ xpointer="xpointer(/*/*[@xml:id='dconf-profile-user-dir'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
<item>
<p>Create the key file
<file>/etc/dconf/db/local.d/00-screensaver</file> to provide
information for the <sys>local</sys> database.</p>
<listing>
- <title><file>/etc/dconf/db/local.d/00-screensaver</file></title>
+ <title><file>/etc/dconf/db/local.d/00-screensaver</file></title>
<code>
# Specify the dconf path
[org/gnome/desktop/session]
# Number of seconds of inactivity before the screen goes blank
+# Set to 0 seconds if you want to deactivate the screensaver.
idle-delay=uint32 180
# Specify the dconf path
[org/gnome/desktop/screensaver]
-# Lock the screen after the screen is blank
-lock-enabled=true
-
# Number of seconds after the screen is blank before locking the screen
lock-delay=uint32 0
</code>
@@ -72,21 +73,20 @@ lock-delay=uint32 0
<file>/etc/dconf/db/local.d/locks/screensaver</file> with the following
content:</p>
<listing>
- <title><file>/etc/dconf/db/local.db/locks/screensaver</file></title>
+ <title><file>/etc/dconf/db/local.db/locks/screensaver</file></title>
<code>
# Lock desktop screensaver settings
/org/gnome/desktop/session/idle-delay
-/org/gnome/desktop/screensaver/lock-enabled
/org/gnome/desktop/screensaver/lock-delay
</code>
</listing>
</item>
<include href="dconf-snippets.xml"
- xpointer="xpointer(/*/*[@xml:id='dconf-update'])"
- xmlns="http://www.w3.org/2001/XInclude"/>
+ xpointer="xpointer(/*/*[@xml:id='dconf-update'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
<include href="dconf-snippets.xml"
- xpointer="xpointer(/*/*[@xml:id='dconf-logoutin'])"
- xmlns="http://www.w3.org/2001/XInclude"/>
+ xpointer="xpointer(/*/*[@xml:id='dconf-logoutin'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
</steps>
</page>
diff --git a/system-admin-guide/C/desktop-shield.page b/system-admin-guide/C/desktop-shield.page
index ba47cbd5..d38c4e8a 100644
--- a/system-admin-guide/C/desktop-shield.page
+++ b/system-admin-guide/C/desktop-shield.page
@@ -5,27 +5,26 @@
<info>
<link type="guide" xref="appearance" />
-
<revision pkgversion="3.22" date="2017-01-09" status="draft" />
<credit type="author copyright">
<name>Matthias Clasen</name>
- <email its:translate="no">matthias clasen gmail com</email>
+ <email>matthias clasen gmail com</email>
<years>2012</years>
</credit>
<credit type="author copyright">
<name>Michael Hill</name>
- <email its:translate="no">mdhillca gmail com</email>
+ <email>mdhillca gmail com</email>
<years>2012</years>
</credit>
<credit type="editor">
<name>Jana Svarova</name>
- <email its:translate="no">jana svarova gmail com</email>
+ <email>jana svarova gmail com</email>
<years>2013</years>
</credit>
<credit type="editor">
<name>Petr Kovar</name>
- <email its:translate="no">pknbe volny cz</email>
+ <email>pknbe volny cz</email>
<years>2017</years>
</credit>
diff --git a/system-admin-guide/C/extensions-enable.page b/system-admin-guide/C/extensions-enable.page
index c91e0a43..fad3bd6c 100644
--- a/system-admin-guide/C/extensions-enable.page
+++ b/system-admin-guide/C/extensions-enable.page
@@ -7,13 +7,17 @@
<link type="guide" xref="software#extension" />
<link type="seealso" xref="extensions-lockdown" />
<link type="seealso" xref="extensions" />
- <revision pkgversion="3.12" date="2014-06-17" status="review"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author copyright">
<name>Petr Kovar</name>
<email>pknbe volny cz</email>
<years>2014</years>
</credit>
+ <credit type="author">
+ <name>Jana Svarova</name>
+ <email>jana svarova gmail com</email>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
@@ -24,9 +28,13 @@
<p>To make extensions available to all users on the system, install them in
the <file>/usr/share/gnome-shell/extensions</file> directory. Note that
- newly-installed machine-wide extensions are disabled by default. To enable
- the extensions for all users, you need to set the
- <code>org.gnome.shell.enabled-extensions</code> key.</p>
+ newly-installed machine-wide extensions are disabled by default.</p>
+
+ <p>You need to set the <code>org.gnome.shell.enabled-extensions</code> key in
+ order to set the default enabled extensions. However, there is currently no
+ way to enable additional extensions for users who have already logged in. This
+ does not apply for existing users who have installed and enabled their own
+ GNOME extensions.</p>
<steps>
<title>Setting the org.gnome.shell.enabled-extensions key</title>
diff --git a/system-admin-guide/C/extensions-lockdown.page b/system-admin-guide/C/extensions-lockdown.page
index 8153a054..edf70250 100644
--- a/system-admin-guide/C/extensions-lockdown.page
+++ b/system-admin-guide/C/extensions-lockdown.page
@@ -5,6 +5,7 @@
<info>
<link type="guide" xref="software#extension" />
+ <link type="guide" xref="user-settings#lockdown"/>
<link type="seealso" xref="extensions-enable" />
<link type="seealso" xref="extensions" />
<revision pkgversion="3.12" date="2014-06-17" status="review"/>
diff --git a/system-admin-guide/C/gsettings-browse.page b/system-admin-guide/C/gsettings-browse.page
new file mode 100644
index 00000000..f695d565
--- /dev/null
+++ b/system-admin-guide/C/gsettings-browse.page
@@ -0,0 +1,70 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
+ type="topic" style="task"
+ id="gsettings-browse">
+
+ <info>
+ <link type="guide" xref="setup" />
+ <link type="seealso" xref="dconf" />
+ <link type="seealso" xref="overrides" />
+ <revision pkgversion="3.30" date="2019-02-08" status="draft"/>
+
+ <credit type="author copyright">
+ <name>Matthias Clasen</name>
+ <email>matthias clasen gmail com</email>
+ <years>2012</years>
+ </credit>
+ <credit type="author copyright">
+ <name>Jim Campbell</name>
+ <email>jwcampbell gmail com</email>
+ <years>2012</years>
+ </credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
+
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+
+ <desc>What tool can I use to explore system and application settings?</desc>
+ </info>
+
+ <title>Browse GSettings values for your applications</title>
+
+ <p>There are two tools you can use to browse system and application
+ preferences stored as GSettings values, the <app>dconf-editor</app> graphical
+ utility and the <cmd>gsettings</cmd> command line utility.</p>
+
+ <p>Both <app>dconf-editor</app> and <cmd>gsettings</cmd> also allows you to
+ change preferences for the current user.</p>
+
+ <note style="warning"><p>Note that these tools always operate using the
+ current user's GSettings database, so you should not run these
+ applications as root.</p>
+
+ <p>Both <app>dconf-editor</app> and <cmd>gsettings</cmd> require a
+ D-Bus session bus in order to make any changes. This is because the
+ <sys>dconf</sys> daemon must be activated using D-Bus.</p>
+
+ <p>You can get the required session bus by running <cmd>gsettings</cmd> under
+ the <sys>dbus-launch</sys> utility, like this:</p>
+
+ <screen><output>$ </output><input>dbus-launch gsettings set org.gnome.desktop.background draw-background
true</input></screen>
+ </note>
+
+ <p><app>dconf-editor</app> may be better to use if you are not familiar with
+ the options available in an application. It shows the hierarchy of settings
+ in a tree-view and also displays additional information about each setting,
+ including the description, type and default value.</p>
+
+ <p><cmd>gsettings</cmd> is more powerful than <app>dconf-editor</app>.
+ Bash completion is provided for <cmd>gsettings</cmd>, and you can write
+ scripts that include <cmd>gsettings</cmd> commands for automated
+ configuration.</p>
+
+ <p>For a complete list of <cmd>gsettings</cmd> options, see the
+ <link its:translate="no" href="man:gsettings"><cmd>gsettings</cmd>(1)</link>
+ man page.</p>
+
+</page>
diff --git a/system-admin-guide/C/keyboard-compose-key.page.stub
b/system-admin-guide/C/keyboard-compose-key.page
similarity index 59%
rename from system-admin-guide/C/keyboard-compose-key.page.stub
rename to system-admin-guide/C/keyboard-compose-key.page
index aca8c4e9..ad5caf96 100644
--- a/system-admin-guide/C/keyboard-compose-key.page.stub
+++ b/system-admin-guide/C/keyboard-compose-key.page
@@ -1,10 +1,11 @@
<page xmlns="http://projectmallard.org/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
type="topic" style="task"
id="keyboard-compose-key">
<info>
- <link type="guide" xref="setup" />
- <revision pkgversion="3.11" date="2014-01-29" status="draft"/>
+ <link type="guide" xref="user-settings" />
+ <revision pkgversion="3.30" date="2019-02-08" status="draft"/>
<credit type="author copyright">
<name>Petr Kovar</name>
@@ -12,6 +13,8 @@
<years>2014</years>
</credit>
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+
<desc>Enable the compose key by default for all users.</desc>
</info>
@@ -24,6 +27,12 @@
<steps>
<title>Set the Right Alt key as the Compose key</title>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-profile-user'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-profile-user-dir'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
<item>
<p>Create a <sys>local</sys> database for machine-wide settings in
<file>/etc/dconf/db/local.d/00-input-sources</file>:</p>
@@ -32,8 +41,8 @@
xkb-options=['compose:<var>ralt</var>']</code>
<p>If you want to set a different key than Right <key>Alt</key>, replace
<var>ralt</var> with the name of that key as specified in the
- <cmd>xkeyboard-config</cmd>(7) man page, section <em>Compose key
- position</em>.</p>
+ <link href="man:xkeyboard-config"><cmd>xkeyboard-config</cmd>(7)</link>
+ man page, section <em>Position of Compose key</em>.</p>
</item>
<item>
<p>Override the user's setting and prevent the user from changing it in
@@ -42,10 +51,12 @@ xkb-options=['compose:<var>ralt</var>']</code>
/org/gnome/desktop/input-sources/xkb-options
</code>
</item>
- <item>
- <p>Update the system databases for the changes to take effect:</p>
- <screen><output>$ </output><input>dconf update</input></screen>
- </item>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-update'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-logoutin'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
</steps>
</page>
diff --git a/system-admin-guide/C/legal.xml b/system-admin-guide/C/legal.xml
index cb5d83fe..91c710b9 100644
--- a/system-admin-guide/C/legal.xml
+++ b/system-admin-guide/C/legal.xml
@@ -1,5 +1,5 @@
<license xmlns="http://projectmallard.org/1.0/";
- href="http://creativecommons.org/licenses/by-sa/3.0/";>
- <p>This work is licensed under a <link href="http://creativecommons.org/licenses/by-sa/3.0/";>Creative
+ href="https://creativecommons.org/licenses/by-sa/3.0/";>
+ <p>This work is licensed under a <link href="https://creativecommons.org/licenses/by-sa/3.0/";>Creative
Commons Attribution-ShareAlike 3.0 Unported License</link>.</p>
</license>
diff --git a/system-admin-guide/C/lockdown-command-line.page b/system-admin-guide/C/lockdown-command-line.page
index 991a2e7d..82d7c1f7 100644
--- a/system-admin-guide/C/lockdown-command-line.page
+++ b/system-admin-guide/C/lockdown-command-line.page
@@ -6,7 +6,7 @@
<info>
<link type="guide" xref="software#management" />
<link type="guide" xref="user-settings#lockdown"/>
- <revision pkgversion="3.12" date="2014-06-18" status="review" />
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author copyright">
<name>Petr Kovar</name>
@@ -18,6 +18,11 @@
<email>kittykat3756 gmail com</email>
<years>2014</years>
</credit>
+ <credit type="author copyright">
+ <name>Jana Svarova</name>
+ <email>jana svarova gmail com</email>
+ <years>2015</years>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
@@ -26,17 +31,27 @@
<title>Disable command-line access</title>
- <p>You can prevent users from being able to access the command-line through
- virtual terminals and terminal applications by following the steps described
- below.</p>
+ <p>To disable command-line access for your desktop user, you need to make
+ configuration changes in a number of different contexts. Bear in mind that the
+ following steps do not remove the desktop user's permissions to access a
+ command line, but rather remove the ways that the desktop user could access
+ the command line.</p>
<list>
<item>
- <p>Prevent users from accessing the
- <keyseq><key>Alt</key><key>F2</key></keyseq> command prompt.</p>
+ <p>Set the <code>org.gnome.desktop.lockdown.disable-command-line</code>
+ GSettings key, which prevents the user from accessing the terminal or
+ specifying a command line to be executed (the <keyseq><key>Alt</key>
+ <key>F2</key></keyseq> command prompt).</p>
+ </item>
+ <item>
+ <p>Prevent users from accessing the <keyseq><key>Alt</key><key>F2</key>
+ </keyseq> command prompt.</p>
</item>
<item>
- <p>Disable dropping to a virtual terminal (VT).</p>
+ <p>Disable switching to virtual terminals (VTs) with the <keyseq>
+ <key>Ctrl</key><key>Alt</key><key><var>function key</var></key></keyseq>
+ shortcuts by modifying the X server configuration.</p>
</item>
<item>
<p>Remove <app>Terminal</app> and all other terminal applications from
@@ -93,21 +108,26 @@ disable-command-line=true</code>
<p>If the computer is running the <em>X Window System</em>, you can disable
access to all virtual terminals by adding a <code>DontVTSwitch</code> option
- to the <code>Serverflags</code> section in the
- <file>/etc/X11/xorg.conf.d</file> file.</p>
+ to the <code>Serverflags</code> section in an X configuration file in the
+ <file>/etc/X11/xorg.conf.d/</file> directory.</p>
<steps>
<item>
<p>Create or edit an X configuration file in
- <file>/etc/X11/xorg.conf.d</file>:</p>
- <code>Section "Serverflags"
+ <file>/etc/X11/xorg.conf.d/</file>. For example,
+ <file>/etc/X11/xorg.conf.d/10-xorg.conf</file>:</p>
+ <listing>
+ <title><file>/etc/X11/xorg.conf.d/10-xorg.conf</file></title>
+<code>Section "Serverflags"
Option "DontVTSwitch" "yes"
-EndSection</code>
+EndSection
+</code>
+ </listing>
</item>
<item>
- <p>Restart GDM for the change to take effect.</p>
+ <p>Restart the X server for the changes to take effect.</p>
</item>
</steps>
diff --git a/system-admin-guide/C/lockdown-logout.page b/system-admin-guide/C/lockdown-logout.page
new file mode 100644
index 00000000..a4c6e675
--- /dev/null
+++ b/system-admin-guide/C/lockdown-logout.page
@@ -0,0 +1,77 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
+ type="topic" style="task"
+ id="lockdown-logout">
+
+ <info>
+ <link type="guide" xref="user-settings#lockdown"/>
+ <link type="seealso" xref="dconf-lockdown" />
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
+
+ <credit type="author copyright">
+ <name>Jana Svarova</name>
+ <email>jana svarova gmail com</email>
+ <years>2015</years>
+ </credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
+
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+
+ <desc>Prevent the user from logging out and from switching a user.</desc>
+ </info>
+
+ <title>Disable user logout and user switching</title>
+
+ <p>Preventing the user from logging out is useful for special kind of GNOME
+ deployments (unmanned kiosks, public internet access terminals, and so on).</p>
+
+ <note style="important">
+ <p>Users can evade the logout lockdown by switching to a different user. That
+ is the reason why it is recommended to also disable <em>user switching</em>
+ when configuring the system.</p>
+ </note>
+
+ <steps>
+ <title>Disable user logout and user switching</title>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-profile-user'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-profile-user-dir'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
+ <item>
+ <p>Create the key file <file>/etc/dconf/db/local.d/00-logout</file> to provide
+ information for the <sys>local</sys> database:</p>
+<screen>
+[org/gnome/desktop/lockdown]
+# Prevent the user from logging out
+disable-log-out=true
+
+# Prevent the user from user switching
+disable-user-switching=true
+</screen>
+ </item>
+ <item>
+ <p>Override the user's setting and prevent the user from changing it in
+ <file>/etc/dconf/db/local.d/locks/lockdown</file>:</p>
+<screen>
+# Lock user logout
+/org/gnome/desktop/lockdown/disable-log-out
+
+# Lock user switching
+/org/gnome/desktop/lockdown/disable-user-switching
+</screen>
+ </item>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-update'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
+ <item>
+ <p>Restart the system for the system-wide settings to take effect.</p>
+ </item>
+ </steps>
+
+</page>
diff --git a/system-admin-guide/C/lockdown-online-accounts.page
b/system-admin-guide/C/lockdown-online-accounts.page
index 5b7a80b5..23511473 100644
--- a/system-admin-guide/C/lockdown-online-accounts.page
+++ b/system-admin-guide/C/lockdown-online-accounts.page
@@ -5,14 +5,19 @@
<info>
<link type="guide" xref="user-settings#lockdown"/>
- <revision pkgversion="3.14" date="2015-05-04" status="draft"/>
<link type="seealso" xref="dconf-lockdown" />
-
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
+
<credit type="author copyright">
<name>Jana Svarova</name>
<email>jana svarova gmail com</email>
<years>2015</years>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
@@ -21,10 +26,9 @@
<title>Allow or disallow online accounts</title>
<p>The <app>GNOME Online Accounts</app> (GOA) are used for
- setting personal network accounts which are then automatically integrated with
- the GNOME Desktop and applications. The user can add their online accounts,
- such as Google, Facebook, Flickr, ownCloud, etc. via the
- <app>Online Accounts</app> application.</p>
+ integrating personal network accounts with the GNOME Desktop and applications.
+ The user can add their online accounts, such as Google, Facebook, Flickr,
+ ownCloud, and others using the <app>Online Accounts</app> application.</p>
<p>As a system administrator, you can:</p>
<list>
@@ -33,9 +37,8 @@
<item><p>disable all online accounts.</p></item>
</list>
- <section id="whitelist-goa">
- <title>Configure online accounts</title>
<steps>
+ <title>Configure online accounts</title>
<item><p>Make sure that you have the <sys>gnome-online-accounts</sys> package
installed on your system.</p>
</item>
@@ -47,39 +50,52 @@
xmlns="http://www.w3.org/2001/XInclude"/>
<item>
<p>Create the key file <file>/etc/dconf/db/local.d/00-goa</file> to provide
- information for the <sys>local</sys> database containing the following configuration:</p>
+ information for the <sys>local</sys> database containing the following
+ configuration.</p>
<list>
- <item><p>For selectively enabling a few providers only:</p>
- <screen>[org/gnome/online-accounts]
-whitelisted-providers= ['google', 'facebook']</screen>
+ <item><p>To enable specific providers:</p>
+<code>
+[org/gnome/online-accounts]
+whitelisted-providers= ['google', 'facebook']
+</code>
+ <comment>
+ <cite date="2015-05-18">Kat</cite>
+ <p>Explain where these come from. For example, why "google" instead of
+ "Google"? Where can I find a full list?</p>
+ </comment>
</item>
- <item><p>For disabling all providers:</p>
- <screen>[org/gnome/online-accounts]
-whitelisted-providers= []</screen></item>
- <item><p>For allowing all available providers:</p>
- <screen>[org/gnome/online-accounts]
-whitelisted-providers= ['all']</screen></item>
- </list>
- </item>
- <item>
- <p>To prevent the user from overriding these settings, create the file
- <file>/etc/dconf/db/local.d/locks/goa</file> with the following
- content:</p>
- <listing>
- <title><file>/etc/dconf/db/local.db/locks/goa</file></title>
+ <item><p>To disable all providers:</p>
+<code>
+[org/gnome/online-accounts]
+whitelisted-providers= ['']
+</code>
+ </item>
+ <item><p>To allow all available providers:</p>
+<code>
+[org/gnome/online-accounts]
+whitelisted-providers= ['all']
+</code>
+ <p>This is the default setting.</p></item>
+ </list>
+ </item>
+ <item>
+ <p>To prevent the user from overriding these settings, create the file
+ <file>/etc/dconf/db/local.d/locks/goa</file> with the following
+ content:</p>
+ <listing>
+ <title><file>/etc/dconf/db/local.db/locks/goa</file></title>
<code>
# Lock the list of providers that are allowed to be loaded
/org/gnome/online-accounts/whitelisted-providers
</code>
- </listing>
- </item>
-
- <include href="dconf-snippets.xml"
- xpointer="xpointer(/*/*[@xml:id='dconf-update'])"
- xmlns="http://www.w3.org/2001/XInclude"/>
- <include href="dconf-snippets.xml"
- xpointer="xpointer(/*/*[@xml:id='dconf-logoutin'])"
- xmlns="http://www.w3.org/2001/XInclude"/>
+ </listing>
+ </item>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-update'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
+ <include href="dconf-snippets.xml"
+ xpointer="xpointer(/*/*[@xml:id='dconf-logoutin'])"
+ xmlns="http://www.w3.org/2001/XInclude"/>
</steps>
-</section>
+
</page>
diff --git a/system-admin-guide/C/lockdown-single-app-mode.page
b/system-admin-guide/C/lockdown-single-app-mode.page
new file mode 100644
index 00000000..ae370b0a
--- /dev/null
+++ b/system-admin-guide/C/lockdown-single-app-mode.page
@@ -0,0 +1,116 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
+ type="topic" style="task"
+ id="lockdown-single-app-mode">
+
+ <info>
+ <link type="guide" xref="user-settings#lockdown"/>
+ <link type="seealso" xref="lockdown-printing" />
+ <link type="seealso" xref="lockdown-file-saving" />
+ <link type="seealso" xref="lockdown-repartitioning" />
+ <link type="seealso" xref="lockdown-command-line" />
+ <link type="seealso" xref="login-automatic" />
+
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
+
+ <credit type="author copyright">
+ <name>Matthias Clasen</name>
+ <email>mclasen redhat com</email>
+ <years>2014</years>
+ </credit>
+ <credit type="editor">
+ <name>Jana Svarova</name>
+ <email>jana svarova gmail com</email>
+ <years>2014</years>
+ </credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
+
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+
+ <desc>Set up a kiosk-like, single-application system.</desc>
+ </info>
+
+ <title>Configure single-application mode</title>
+
+ <p>Single-application mode is a modified GNOME Shell which configures the
+ Shell as an interactive kiosk. The administrator locks down some behavior to
+ make the standard desktop more restrictive for users, letting them focus on
+ selected features.</p>
+
+ <p>Set up single-application mode for a wide range of functions in a number
+ of fields (from communication to entertainment or education), and use it as a
+ self-serve machine, event manager, registration point, and so on.</p>
+
+ <steps>
+ <title>Set up single-application mode</title>
+ <item>
+ <p>Lock down settings to prevent printing, terminal access, and so on.</p>
+ <list type="disc">
+ <item><p><link xref="lockdown-command-line" /></p></item>
+ <item><p><link xref="lockdown-printing" /></p></item>
+ <item><p><link xref="lockdown-file-saving" /></p></item>
+ <item><p><link xref="lockdown-repartitioning" /></p></item>
+ </list>
+ </item>
+ <item>
+ <p>Configure automatic login in the <file>/etc/gdm/custom.conf</file>
+ file for the user.</p>
+ <p>See <link xref="login-automatic" /> for more information.</p>
+ </item>
+ <item>
+ <p>Create a new user with a name, which follows typical naming conventions
+ (no space or special characters, do not start with a digit or a dash).
+ Also, make sure the user name matches with the related names, such as when
+ referring to a session. A good example is <em>kiosk-user</em>.</p>
+ </item>
+ <item>
+ <p>Create a session with a name matching the user name (for example, for
+ the <em>kiosk-user</em> mentioned above, <em>kiosk</em> is a good match).
+ To do so, create a <file>/usr/share/xsessions/<var>kiosk</var>.desktop</file>
+ file and set the <code>Exec</code> line as follows:</p>
+<code>
+Exec=gnome-session --session kiosk
+</code>
+ </item>
+ <item>
+ <p>Set the default session for <em>kiosk-user</em> by adding the following
+ line to the <file>/var/lib/AccountsService/users/<var>kiosk-user</var>
+ </file> file:</p>
+<code>
+XSession=kiosk
+</code>
+ </item>
+ <item>
+ <p>Define the <em>kiosk</em> session by writing a custom session
+ definition, containing the following line:</p>
+<code>
+RequiredComponents=kiosk-app;gnome-settings-daemon;kiosk-shell;
+</code>
+ <p>This creates a session that runs three programs: <sys>kiosk-app</sys>
+ (a sample application), <sys>gnome-settings-daemon</sys> (a standard
+ component in the GNOME session), and <sys>kiosk-shell</sys> (which is a
+ customized version of GNOME Shell).</p>
+ </item>
+ <item>
+ <p>Create a desktop file for <sys>kiosk-shell</sys> in
+ <file>/usr/share/applications/kiosk-shell.desktop</file>, containing the
+ following line:</p>
+<code>
+Exec=gnome-shell --mode=kiosk
+</code>
+ </item>
+ <item>
+ <p>Create a mode definition <file>/usr/share/gnome-shell/modes/kiosk.json</file>.
+ This is a simple json file defining the available <sys>gnome-shell</sys>
+ user interface.</p>
+ <p>As the starting point, look at <file>/usr/share/gnome-shell/modes/classic.json</file>
+ and <file>/usr/share/gnome-shell/modes/initial-setup.json</file> for
+ examples.</p>
+ </item>
+ </steps>
+
+</page>
diff --git a/system-admin-guide/C/login-banner.page b/system-admin-guide/C/login-banner.page
index 589ab41e..2801d522 100644
--- a/system-admin-guide/C/login-banner.page
+++ b/system-admin-guide/C/login-banner.page
@@ -6,8 +6,7 @@
<info>
<link type="guide" xref="login#appearance"/>
<!--<link type="seealso" xref="gdm-restart"/>-->
- <revision pkgversion="3.8" date="2013-04-19" status="review"/>
- <revision pkgversion="3.14" date="2014-06-17" status="review"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author copyright">
<name>Matthias Clasen</name>
@@ -70,9 +69,9 @@ banner-message-text='<input its:translate="yes">Type the banner message here.</i
</steps>
<note>
- <p>You should keep the banner message short, as longer messages do
- not fit on the screen. The banner message cannot be read from
- an external file.</p>
+ <p>There is no character limit for the banner message. <sys>gnome-shell</sys>
+ autodetects longer stretches of text and enters two column mode.</p>
+ <p>The banner message cannot be read from an external file.</p>
</note>
</page>
diff --git a/system-admin-guide/C/login-fingerprint.page b/system-admin-guide/C/login-fingerprint.page
index af78ab9f..e321cf2e 100644
--- a/system-admin-guide/C/login-fingerprint.page
+++ b/system-admin-guide/C/login-fingerprint.page
@@ -5,7 +5,7 @@
<info>
<link type="guide" xref="login#management" />
- <link type="seealso" xref="dconf" />
+ <link type="guide" xref="user-settings#lockdown"/>
<revision pkgversion="3.12" date="2014-06-17" status="candidate" />
<credit type="author copyright">
diff --git a/system-admin-guide/C/mime-types-application-user.page
b/system-admin-guide/C/mime-types-application-user.page
index 4cddf705..a17fc983 100644
--- a/system-admin-guide/C/mime-types-application-user.page
+++ b/system-admin-guide/C/mime-types-application-user.page
@@ -6,7 +6,7 @@
<link type="guide" xref="software#management" />
<link type="seealso" xref="mime-types-custom-user" />
<link type="seealso" xref="mime-types-custom" />
- <revision pkgversion="3.12" date="2014-06-17" status="review"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author">
<name>Petr Kovar</name>
@@ -18,22 +18,26 @@
</info>
<title>Override the default registered application for individual users</title>
+
+ <p>
+ The <file>/usr/share/applications/mimeapps.list</file> and
+ <file>/usr/share/applications/gnome-mimeapps.list</file> files
+ specify which application is registered to open specific MIME types by
+ default. These files are provided by the distribution.
+ </p>
<p>
- The <file>/usr/share/applications/defaults.list</file> file
- specifies which application is registered to open specific MIME types by
- default. To override the system defaults for individual users, you need to
- create a <file>~/.local/share/applications/mimeapps.list</file>
- file with a list of MIME types for which you want to override the default
- registered application.
+ To override the system defaults for individual users, you need to
+ create a <file>~/.config/mimeapps.list</file> file with a list of MIME
+ types for which you want to override the default registered application.
</p>
<steps>
<title>Override the default registered application for individual users</title>
<item>
<p>
- Consult the <file>/usr/share/applications/defaults.list</file>
+ Consult the <file>/usr/share/applications/mimeapps.list</file>
file to determine the MIME types for which you want to change the
default registered application. For example, the following sample of
- the <file>defaults.list</file> file specifies the default
+ the <file>mimeapps.list</file> file specifies the default
registered application for the <code>text/html</code> and
<code>application/xhtml+xml</code> MIME types:
</p>
@@ -52,9 +56,9 @@ application/xhtml+xml=epiphany.desktop</code>
</item>
<item>
<p>
- Create the <file>~/.local/share/applications/mimeapps.list</file>
- file. In the file, specify the MIME types and their corresponding
- default registered applications:
+ Create the <file>~/.config/mimeapps.list</file> file. In the file,
+ specify the MIME types and their corresponding default registered
+ applications:
</p>
<code>[Default Applications]
text/html=<var>myapplication1.desktop</var>
@@ -73,7 +77,9 @@ application/xhtml+xml=<var>myapplication2.desktop</var>;</code>
<p>For these settings to function properly, ensure that both the
<file>myapplication1.desktop</file> and
<file>myapplication2.desktop</file> files are placed in the
- <file>/usr/share/applications/</file> directory.
+ <file>/usr/share/applications/</file> directory. Individual users’
+ <file>.desktop</file> files can be stored in
+ <file>~/.local/share/applications/</file>.
</p>
</item>
<item>
diff --git a/system-admin-guide/C/mime-types-application.page
b/system-admin-guide/C/mime-types-application.page
index 4cf8855d..ce10b28f 100644
--- a/system-admin-guide/C/mime-types-application.page
+++ b/system-admin-guide/C/mime-types-application.page
@@ -7,7 +7,7 @@
<link type="seealso" xref="mime-types-application-user" />
<link type="seealso" xref="mime-types-custom-user" />
<link type="seealso" xref="mime-types-custom" />
- <revision pkgversion="3.12" date="2014-06-17" status="review"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author">
<name>Petr Kovar</name>
@@ -20,21 +20,32 @@
<title>Override the default registered application for all users</title>
<p>
- The <file>/usr/share/applications/defaults.list</file> file
- specifies which application is registered to open specific MIME types by
- default. To override the system defaults for all users on the system, you
- need to create a <file>/usr/share/applications/mimeapps.list</file>
- file with a list of MIME types for which you want to override the default
- registered application.
- </p>
+ The <file>/usr/share/applications/mimeapps.list</file> and
+ <file>/usr/share/applications/gnome-mimeapps.list</file> files
+ specify which application is registered to open specific MIME types by
+ default. These files are provided by the distribution.</p>
+
+ <p>To override the system defaults for all users on the system, you
+ need to create a <file>/etc/xdg/mimeapps.list</file> or
+ <file>/etc/xdg/gnome-mimeapps.list</file> file with a list of MIME types
+ for which you want to override the default registered application.</p>
+
+ <note>
+ <p>Files located in <file>/etc/xdg/</file> take precedence over files
+ found in <file>/usr/share/applications/</file>. Additionally,
+ <file>/etc/xdg/gnome-mimeapps.list</file> takes precedence over
+ <file>/etc/xdg/mimeapps.list</file>, but can be overridden by the user's
+ configuration in <file>~/.config/mimeapps.list</file>.</p>
+ </note>
+
<steps>
<title>Override the default registered application for all users</title>
<item>
<p>
- Consult the <file>/usr/share/applications/defaults.list</file>
+ Consult the <file>/usr/share/applications/mimeapps.list</file>
file to determine the MIME types for which you want to change the
default registered application. For example, the following sample of
- the <file>defaults.list</file> file specifies the default
+ the <file>mimeapps.list</file> file specifies the default
registered application for the <code>text/html</code> and
<code>application/xhtml+xml</code> MIME types:
</p>
@@ -51,7 +62,7 @@ application/xhtml+xml=epiphany.desktop</code>
</item>
<item>
<p>
- Create the <file>/usr/share/applications/mimeapps.list</file>
+ Create the <file>/etc/xdg/mimeapps.list</file>
file. In the file, specify the MIME types and their corresponding
default registered applications:
</p>
diff --git a/system-admin-guide/C/network-printer-config.page
b/system-admin-guide/C/network-printer-config.page
index f6a10474..ef1e04ee 100644
--- a/system-admin-guide/C/network-printer-config.page
+++ b/system-admin-guide/C/network-printer-config.page
@@ -35,11 +35,11 @@
<steps>
<title>Configure your printer</title>
<item>
- <p>Click <em>your name</em> at the top-right corner and from the
- drop-down menu, choose <gui>Settings</gui>.</p>
+ <p>Open <gui>Activities overview</gui> and start typing
+ <gui>Printers</gui>.</p>
</item>
<item>
- <p>Click on the <gui>Printers</gui> icon.</p>
+ <p>Click <gui>Printers</gui>.</p>
</item>
<item>
<p>Unlock the <gui>Printers</gui> panel by clicking on the
diff --git a/system-admin-guide/C/overrides.page b/system-admin-guide/C/overrides.page
index 9775bff1..f30e4ae9 100644
--- a/system-admin-guide/C/overrides.page
+++ b/system-admin-guide/C/overrides.page
@@ -1,16 +1,22 @@
<page xmlns="http://projectmallard.org/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
type="topic" style="task"
id="overrides">
<info>
<link type="guide" xref="setup" />
- <revision pkgversion="3.6" date="2012-05-21" status="stub"/>
+ <revision pkgversion="3.30" date="2019-02-08" status="review"/>
<credit type="author copyright">
<name>Michael Hill</name>
<email>mdhillca gmail com</email>
<years>2012</years>
</credit>
+ <credit type="editor">
+ <name>Petr Kovar</name>
+ <email>pknbe volny cz</email>
+ <years>2019</years>
+ </credit>
<desc>GSettings overrides are used by distributions to adjust default
settings.</desc>
@@ -28,24 +34,19 @@
administrators to adjust default settings and set mandatory settings for the
GNOME desktop and apps.</p>
-<comment>
- <p>GNOME developers are working towards allowing or even requiring <file>/usr/</file>
- to be mounted read-only with the exception of <file>/usr/local/</file>.</p>
+ <section id="what-are-vendor-overrides">
+ <title>What are vendor overrides?</title>
- <p>Default values are defined in the schemas that get installed by an
+ <p>Default values are defined in the schemas that are installed by an
application. Sometimes, it is necessary for a vendor or distributor to adjust
- these defaults. Since patching the XML source for the schema is inconvenient
- and error-prone, glib-compile-schemas reads so-called
- <em>"vendor override"</em> files. These are keyfiles in the same directory
- as the XML schema sources which can override default values. The schema id
- serves as the group name in the key file, and the values are expected in
- serialized GVariant form, as in the following example:</p>
-
-<code>
-[org.gtk.Example]
-key1='string'
-key2=1.5
-</code>
-</comment>
+ these defaults.</p>
+
+ <p>Since patching the XML source for the schema is inconvenient and
+ error-prone, <link its:translate="no" href="man:glib-compile-schemas">
+ <sys>glib-compile-schemas</sys></link> reads so-called <em>vendor override</em>
+ files. These are keyfiles in the same directory as the XML schema sources,
+ which can override default values.</p>
+
+ </section>
</page>
diff --git a/system-admin-guide/C/processes.page b/system-admin-guide/C/processes.page
index 85085512..d29d1bdc 100644
--- a/system-admin-guide/C/processes.page
+++ b/system-admin-guide/C/processes.page
@@ -1,5 +1,6 @@
<page xmlns="http://projectmallard.org/1.0/";
xmlns:ui="http://projectmallard.org/ui/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
type="topic" style="task"
id="processes">
@@ -31,10 +32,9 @@
<title>Typical processes</title>
- <p>In a stock <app>GNOME</app> session, programs called
- <link href="man:daemon"><app>daemons</app></link> run on the system as
- background processes. You should find the following daemons running by
- default:</p>
+ <p>In a stock <app>GNOME</app> session, programs called daemons or services
+ run on the system as background processes. You should find the following
+ daemons running by default:</p>
<terms>
<item>
@@ -43,7 +43,7 @@
programs can use to exchange messages with one another.
<app>dbus-daemon</app> is implemented with the D-Bus library which
provides one-to-one communication between any two applications.</p>
- <p>For extended information, see the manual page for
+ <p>For extended information, see the man page for
<link href="man:dbus-daemon">dbus-daemon</link>.</p>
</item>
<item>
@@ -52,8 +52,9 @@
websites are stored securely using the <app>gnome-keyring-daemon</app>.
This information is written into an encrypted file called the keyring
file and saved in the user's home directory.</p>
- <p>For extended information, see the manual page for
- <link href="man:gnome-keyring-daemon">gnome-keyring-daemon</link>.</p>
+ <p>For extended information, see the man page for
+ <link its:translate="no" href="man:gnome-keyring-daemon">gnome-keyring-daemon</link>.
+ </p>
</item>
<item>
<title>gnome-session</title>
@@ -63,16 +64,18 @@
default session for the user is set at the time of system installation
by the system administrator. <app>gnome-session</app> typically loads
the last session that ran successfully on the system.</p>
- <p>For extended information, see the manual page for
- <link href="man:gnome-session">gnome-session</link>.</p>
+ <p>For extended information, see the man page for
+ <link its:translate="no" href="man:gnome-session">gnome-session</link>.
+ </p>
</item>
<item>
<title>gnome-settings-daemon</title>
<p>The <app>gnome-settings-daemon</app> handles settings for a
GNOME session and for all programs that are run within the
session.</p>
- <p>For extended information, see the manual page for
- <link href="man:gnome-settings-daemon">gnome-settings-daemon</link>.</p>
+ <p>For extended information, see the man page for
+ <link its:translate="no" href="man:gnome-settings-daemon">gnome-settings-daemon</link>.
+ </p>
</item>
<item>
<title>gnome-shell</title>
@@ -80,15 +83,16 @@
for GNOME such as launching programs, browsing directories,
viewing files and so on.</p>
<p>For extended information, see the
- manual page for <link href="man:gnome-shell">gnome-shell</link>.</p>
+ man page for <link its:translate="no" href="man:gnome-shell">gnome-shell</link>.
+ </p>
</item>
<item>
<title>pulseaudio</title>
<p><app>PulseAudio</app> is a sound server for Linux, POSIX and Windows
systems that lets programs output audio via the <app>Pulseaudio</app>
daemon.</p>
- <p>For extended information, see the manual page for
- <link href="man:pulseaudio">pulseaudio</link>.</p>
+ <p>For extended information, see the man page for
+ <link its:translate="no" href="man:pulseaudio">pulseaudio</link>.</p>
</item>
</terms>
diff --git a/system-admin-guide/C/session-custom.page b/system-admin-guide/C/session-custom.page
index 7ec05b2a..535f168d 100644
--- a/system-admin-guide/C/session-custom.page
+++ b/system-admin-guide/C/session-custom.page
@@ -1,4 +1,5 @@
<page xmlns="http://projectmallard.org/1.0/";
+ xmlns:its="http://www.w3.org/2005/11/its";
type="topic" style="task"
id="session-custom">
@@ -57,8 +58,9 @@ Exec=<input>gnome-session --session=new-session</input></code>
<cmd>gnome-session --session=<var>new-session</var></cmd>
command.</p>
<p>For more information on the parameters that you can use with
- <cmd>gnome-session</cmd>, see the <link href="man:gnome-session">gnome-session</link>
- man page.</p>
+ <cmd>gnome-session</cmd>, see the
+ <link its:translate="no" href="man:gnome-session">gnome-session</link> man
+ page.</p>
</item>
<item><p>Create a custom session file in
<file>/usr/share/gnome-session/sessions/<var>new-session</var>.session</file>
diff --git a/system-admin-guide/C/session-debug.page b/system-admin-guide/C/session-debug.page
index 84ce4f80..d9bcd6b3 100644
--- a/system-admin-guide/C/session-debug.page
+++ b/system-admin-guide/C/session-debug.page
@@ -59,7 +59,9 @@
</steps>
<p>For more information on the systemd journal, see the
- <link href="man:journalctl"><cmd>journalctl</cmd></link>(1) man page.</p>
+ <link its:translate="no" href="man:journalctl"><cmd>journalctl</cmd>(1)</link>
+ man page.</p>
+
</section>
</page>
diff --git a/system-admin-guide/Makefile.am b/system-admin-guide/Makefile.am
index e90b6ebf..a55fb7da 100644
--- a/system-admin-guide/Makefile.am
+++ b/system-admin-guide/Makefile.am
@@ -4,6 +4,8 @@ HELP_ID = system-admin-guide
HELP_FILES = \
appearance.page \
+ autostart-applications.page \
+ backgrounds-extra.page \
dconf-custom-defaults.page \
dconf-keyfiles.page \
dconf-lockdown.page \
@@ -20,14 +22,18 @@ HELP_FILES = \
extensions.page \
fonts.page \
fonts-user.page \
+ gsettings-browse.page \
index.page \
+ keyboard-compose-key.page \
keyboard-layout.page \
legal.xml \
lockdown-command-line.page \
lockdown-file-saving.page \
+ lockdown-logout.page \
lockdown-online-accounts.page \
lockdown-printing.page \
lockdown-repartitioning.page \
+ lockdown-single-app-mode.page \
login-automatic.page \
login-banner.page \
login-enterprise.page \
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
