Default page

Your IP: 216.73.216.91
Server IP: 157.245.101.34
Server: Linux skvinfotech-website 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64
Server Software: Apache/2.4.41 (Ubuntu)
PHP Version: 7.4.33
Buat File | Buat Folder

Dir : ~/usr/share/help/C/system-admin-guide/

Edit File: lockdown-single-app-mode.page

<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>

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.

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.

<steps>
 <title>Set up single-application mode</title>
 <item>
 Lock down settings to prevent printing, terminal access, and so on.
 <list type="disc">
 <item><link xref="lockdown-command-line" /></item>
 <item><link xref="lockdown-printing" /></item>
 <item><link xref="lockdown-file-saving" /></item>
 <item><link xref="lockdown-repartitioning" /></item>
 </list>
 </item>
 <item>
 Configure automatic login in the <file>/etc/gdm/custom.conf</file>
 file for the user.
 See <link xref="login-automatic" /> for more information.
 </item>
 <item>
 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 kiosk-user.
 </item>
 <item>
 Create a session with a name matching the user name (for example, for
 the kiosk-user mentioned above, kiosk 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:
<code>
Exec=gnome-session --session kiosk
</code>
 </item>
 <item>
 Set the default session for kiosk-user by adding the following
 line to the <file>/var/lib/AccountsService/users/<var>kiosk-user</var>
 </file> file:
<code>
XSession=kiosk
</code>
 </item>
 <item>
 Define the kiosk session by writing a custom session
 definition, containing the following line:
<code>
RequiredComponents=kiosk-app;gnome-settings-daemon;kiosk-shell;
</code>
 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).
 </item>
 <item>
 Create a desktop file for <sys>kiosk-shell</sys> in
 <file>/usr/share/applications/kiosk-shell.desktop</file>, containing the
 following lines:
<code>
[Desktop Entry]
Exec=gnome-shell --mode=kiosk
</code>
 </item>
 <item>
 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.
 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.
 </item>
 </steps>

</page>