Centos where is gdm.conf

If this script does not exist or this key is empty the default message is sent. If this script succeeds and produces some output, the first line of it's output is sent and only the first line. It runs at most once every 3 seconds to prevent possible denial of service by flooding the machine with QUERY packets. Default values are stored in GConf in the gdm-simple-greeter. These values can be edited using the gconftool-2 or gconf-editor programs. The following configuration options are supported:.

Specifies the text banner message to show on the greeter window. Controls whether to show the restart buttons in the login window. If true, then the face browser with known users is not shown in the login window. Set to a list of languages to be shown by default in the login window. Default value is "[]". With the default setting only the system default language is shown and the option "Other Users are not intended to change this setting by hand.

Instead GDM keeps track of any languages selected in this configuration key, and will show them in the language combo box along with the "Other This way, commonly selected languages are easier to select. Set to a list of keyboard layouts to be shown by default in the login panel. With the default setting only the system default keyboard layout is shown and the option "Other Instead GDM keeps track of any keyboard layouts selected in this configuration key, and will show them in the keyboard layout combo box along with the "Other This way, commonly selected keyboard layouts are easier to select.

Controls whether compiz is used as the window manager instead of metacity. This section describes the accessibility configuration options available in GDM. The GDM greeter panel at the login screen displays an accessibility icon. In the GDM Accessibility Dialog, there is a list of checkboxes, so the user can enable or disable the associated assistive tools.

The checkboxes that correspond to the on-screen keyboard, screen magnifier and screen reader assistive tools act on the three GConf keys that are described in the next section of this document. By enabling or disabling these checkboxes, the associated GConf key is set to "true" or "false". When the GConf key is set to true, the assistive tools linked to this GConf key are launched. When the GConf key is set to "false", any running assistive tool linked to this GConf key are terminated.

These GConf keys are not automatically reset to a default state after the user has logged in. Consequently, the assistive tools that were running during the last GDM login session will automatically be launched at the next GDM login session. The other checkboxes in the GDM Accessibility Dialog do not have corresponding GConf keys because no additional program is launched to provide the accessibility features that they offer.

These other options correspond to accessibility features that are provided by the Xserver, which is always running during the GDM session. GDM offers the following GConf keys to control its accessibility features:. This is needed for many accessibility technology programs to work. By default this is a screen magnifier application. By default this is an on-screen keyboard application. By default this is a screen reader application.

So the exact AutostartCondition line in the desktop file could be one of the following:. When an accessibility key is true, then any program which is linked to that key in a GDM autostart desktop file will be launched unless the Hidden key is set to true in that desktop file. A single GConf key can even start multiple assistive tools if there are multiple desktop files with this AutostartCondition in the GDM autostart directory. To replace GOK with the on-screen keyboard application "onboard" and additionally activate the assistive tool "mousetweaks" for dwelling support, then the following configuration is needed.

Create a desktop file for onboard and a second one for mousetweaks; for example, onboard. These files must be placed in the GDM autostart directory and be in the format as explained in the "Autostart Configuration" section of this document. The following is an example onboard.

The following is an example mousetweaks. Note the line with the AutostartCondition that links both desktop files to the GConf key for the on-screen keyboard. Otherwise onboard and GOK would simultaneously be started.

This can be done by removing the gok. After making these changes, GOK will no longer be started when the user activates the on-screen keyboard in the GDM session; but onboard and mousetweaks will instead be launched. The GDM Greeter uses some of the same framework that your desktop session will use. And so, it is influenced by a number of the same GConf settings. For each of these settings the Greeter will use the default value unless it is specifically overridden by a GDM's installed mandatory policy b system mandatory policy.

GDM installs its own mandatory policy to lock down some settings for security. GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, background, sound, xsettings. These are responsible for things like the background image, font and theme settings, sound events, etc. Plugins can also be disabled using GConf. GDM sessions are specified using the FreeDesktop. If the key is not specified in a desktop file, the value defaults to "false".

If this key is specified to be "true" in a desktop file, then GDM will launch the program specified by the desktop file "Exec" key directly when starting the user session.

When a user logs in for the first time, this file is created with the user's initial choices. The user can change these default values by simply changing to a different value when logging in.

GDM will remember this change for subsequent logins. It has one section called [Desktop] which has two keys: Session and Language. The Session key specifies the basename of the session. The Language key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:. If you want to distribute this manual separately from the collection, you can do so by adding a copy of the license to the manual, as described in section 6 of the license.

Many of the names used by companies to distinguish their products and services are claimed as trademarks. Go to page content Go to main menu Go to the search field.

About Users Administrators Developers. Scripting Integration Points 5. Autostart Configuration 5. Xsession Script 5. Daemon Configuration 5. Simple Greeter Configuration 5.

Accessibility Configuration 5. General Session Settings 5. GDM Session Configuration 5. Scripting Integration Points. Autostart Configuration. Xsession Script. Daemon Configuration. Debug Options 5. Greeter Options 5. Security Options 5.

Debug Options. Greeter Options. Older systems used the X11 login manager XDM. It is still available and a valid option. The system is typically configured for a single login display manager. Multiple display managers can run simultaneously only if they are configured to manage different servers not covered in this tutorial. In order to use the Linux desktop remotely, the login manager must be configured for remote use.

You can test the GDM login screen locally: X -query localhost This may require a change to the default sshd configuration. The default can also be reset using the GUI console configuration tool: sudo dpkg-reconfigure lightdm In this example the default is being set to "lightdm".