From 1c1d9729b82a096dd35e6c36317b0b8731feeff6 Mon Sep 17 00:00:00 2001 From: William Jon McCann Date: Tue, 11 Sep 2007 16:48:02 +0000 Subject: Fix distcheck svn path=/branches/mccann-gobject/; revision=5241 --- ChangeLog | 5 + configure.ac | 8 - docs/ChangeLog | 5 + docs/fr/gdm.xml | 8380 ++++++++++++++++++++++++++++++++++++++++++++++++++++--- po/ChangeLog | 5 + po/POTFILES.in | 8 +- 6 files changed, 8014 insertions(+), 397 deletions(-) diff --git a/ChangeLog b/ChangeLog index 80c3ca2d..00ef4426 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2007-09-11 William Jon McCann + + * configure.ac: + Fix distcheck. + 2007-09-10 William Jon McCann * daemon/INTERNALS: diff --git a/configure.ac b/configure.ac index ced3ea57..b683d07f 100644 --- a/configure.ac +++ b/configure.ac @@ -1319,14 +1319,6 @@ config/Makefile common/Makefile po/Makefile.in docs/Makefile -docs/de/Makefile -docs/es/Makefile -docs/fr/Makefile -docs/it/Makefile -docs/ja/Makefile -docs/zh_CN/Makefile -docs/zh_HK/Makefile -docs/zh_TW/Makefile config/Init config/PreSession config/PostSession diff --git a/docs/ChangeLog b/docs/ChangeLog index 72c7f741..f3a62dd9 100644 --- a/docs/ChangeLog +++ b/docs/ChangeLog @@ -1,3 +1,8 @@ +2007-09-11 William Jon McCann + + * fr/gdm.xml: + Fix distcheck. + 2007-08-31 William Jon McCann * Makefile.am: diff --git a/docs/fr/gdm.xml b/docs/fr/gdm.xml index 5321903e..43ef856a 100644 --- a/docs/fr/gdm.xml +++ b/docs/fr/gdm.xml @@ -1,387 +1,7997 @@ - - - - - - - + + + + ]> - + + + GDM Commands + + + GDM User Commands + + + The GDM package provides the following different commands in + bindir intended to be used by the end-user: + + + + <command>gdmXnestchooser</command> and + <command>gdmXnest</command> Command Line Options + + + The gdmXnestchooser command automatically gets + the correct display number, sets up access, and runs the nested + X server command with the "-indirect localhost" argument. + This provides an XDMCP chooser program. You can also supply as an + argument the hostname whose chooser should be displayed, so + gdmXnestchooser somehost will run the XDMCP + chooser from host somehost inside a nested + X server session. You can make this command do a direct query + instead by passing the -d option as well. In + addition to the following options, this command also supports + standard GNOME options. + + + + <command>gdmXnestchooser</command> Command Line Options + + + -x, --xnest=STRING + + + Nested X server command line, default is defined by the + Xnest configuration option. + + + + + + -o, --xnest-extra-options=OPTIONS + + + Extra options for nested X server, default is no options. + + + + + + -n, --no-query + + + Just run nested X server, no query (no chooser) + + + + + + -d, --direct + + + Do direct query instead of indirect (chooser) + + + + + + -B, --broadcast + + + Run broadcast instead of indirect (chooser) + + + + + + -b, --background + + + Run in background + + + + + + --no-gdm-check + + + Don't check for running GDM + + + + + + + + <command>gdmflexichooser</command> Command Line Options + + + The gdmflexiserver command provides three + features. It can be used to run flexible (on demand) X displays, + to run a flexible display via nested X server, and to send commands to + the GDM daemon process. + + + + Starting a flexible X display will normally lock the current session + with a screensaver and will redisplay the GDM login screen so a second + user can log in. This feature is only available on systems that + support virtual terminals and have them enabled. This feature is + useful if you are logged in as user A, and user B wants to log in + quickly but user A does not wish to log out. The X server takes + care of the virtual terminal switching so it works transparently. + If there is more than one running display defined with flexible=true, + then the user is shown a dialog that displays the currently running + sessions. The user can then pick which session to continue and will + normally have to enter the password to unlock the screen. + + + + Nested displays works on systems that do not support virtual + terminals. This option starts a flexible display in a window in the + current session. This does not lock the current session, so is not + as secure as a flexible server started via virtual terminals. + + + + The gdmflexiserver --command option provides a way + to send commands to the GDM daemon and can be used to debug problems + or to change the GDM configuration. + + + + In addition to the following options, + gdmflexiserver also supports standard GNOME + options. + + + + <command>gdmflexichooser</command> Command Line Options + + + -c, --command=COMMAND + + + Send the specified protocol command to GDM + + + + + + -n, --xnest + + + Start a flexible X display in Nested mode + + + + + + -l, --no-lock + + + Do not lock current screen + + + + + + -d, --debug + + + Turns on debugging output which gets sent to syslog. Same as + turning on debug in the configuration file. + + + + + + -a, --authenticate + + + Authenticate before running --command + + + + + + -s, --startnew + + + Starts a new flexible display without displaying a dialog + asking the user if they wish to continue any existing + sessions. + + + + + + + + <command>gdmdynamic</command> Command Line Options + + + The gdmdynamic command which creates, runs, and + removes displays (X servers) on demand. + + + + gdmdynamic allows the management of displays in a + dynamic fashion. It is typically used in environments where it is not + possible to list the possible displays in the GDM configuration files. + The gdmdynamic command can be used to create a new + display on a particular display number, run all newly created displays, + or remove a display. The gdmdynamic command can also + be used to list all attached displays, or only attached displays that + match a pattern. + + + + This program is designed to manage multiple simultaneous requests and + works to avoid flooding the daemon with requests. If the sockets + connection is busy, it will sleep and retry a certain number of times + that can be tuned with the -s and -t options. + + + + <command>gdmdynamic</command> Command Line Options + + + + + + One of the following options can be used per instance: + + + + + + -a display=server + + + Add a new display configuration, leaving it in the DISPLAY_CONFIG + state. For example, + "-a 2=StandardServerTwo" + "-a 3=/usr/X11R6/bin/X -dev /dev/fb2" + + + The display will not actually be started until the display is released + by calling gdmdynamic again with the -r option. + + + + + + -r + + + Release (run) all displays waiting in the DISPLAY_CONFIG state. + + + + + + -d display + + + Delete a display, killing the X server and purging the + display configuration. For example, "-d 3". + + + + + + -l [pattern] + + + List displays via the ATTACHED_SERVERS gdmflexiserver + command. Without a pattern lists all attached displays. With a pattern + will match using glob characters '*', '?', and '[]'. For example: + "-l Standard*" + "-l *Xorg*" + + + + + + + + + These options can be added to the above: + + + + + + -v + + + Verbose mode. Prinr diagnostic messages about each message sent + to GDM. + + + + + + -b + + + Background mode. Fork child to do the work and return immediately. + + + + + + -t RETRY + + + If the daemon socket is busy, gdmdynamic will + retry to open the connection the specified RETRY number of times. + Default value is 15. + + + + + + -s SLEEP + + + If the daemon socket is busy, gdmdynamic will + sleep an amount of time between retries. A random number of + seconds 0-5 is added to the SLEEP value to help ensure that + multiple calls to gdmdynamic do not all try to restart at the + same time. A SLEEP value of zero causes the sleep time to be + 1 second. Default value is 8 seconds. + + + + + + + + + <command>gdmphotosetup</command> Command Line Options + + + Allows the user to select an image that will be used as the user's + photo by GDM's face browser, if enabled by GDM. The selected file + is stored as ~/.face. This command accepts + standard GNOME options. + + + + + <command>gdmthemetester</command> Command Line Options + + + gdmthemetester takes two parameters. The first + parameter specifies the environment and the second parameter + specifies the path name or the name of a theme to view. + + This is a tool for viewing a theme outside of GDM. It is useful for + testing or viewing themes. gdmthemetester requires + that the system support gdmXnest. + + Note that themes can display differently depending on the theme's + "Show mode". gdmthemetester allows + viewing the themes in different modes via the environment option. + Valid environment values and their meanings follow: + + +console - In console mode. +console-timed - In console non-flexi mode. +flexi - In flexi mode. +xdmcp - In remote (XDMCP) mode. +remote-flexi - In remote (XDMCP) & flexi mode. + + + + + + + GDM Root User Commands + + + The GDM package provides the following different commands in + sbindir intended to be used by the root user: + + + + <command>gdm</command> and <command>gdm-binary</command> + Command Line Options + + + The gdm command is really just a script which + runs the gdm-binary, passing along any options. + Before launching gdm-binary, the gdm wrapper script + will source the <etc>/profile file to set + the standard system environment variables. In order to better support + internationalization, it will also set the LC_MESSAGES environment + variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you + really need to set some additional environment before launching GDM, + you can do so in this script. + + + + <command>gdm</command> and <command>gdm-binary</command> + Command Line Options + + + --help + + + Gives a brief overview of the command line options. + + + + + + --nodaemon + + + If this option is specified, then GDM does not fork into the + background when run. You can also use a single-dash version, + "-nodaemon" for compatibility with other display + managers. + + + + + + --no-console + + + Tell the daemon that it should not run anything on the console. + This means that none of the local servers from the + [servers] section will be run, and the + console will not be used for communicating errors to the user. + An empty [servers] section automatically + implies this option. + + + + + + --config=CONFIGFILE + + + Specify an alternative configuration file. + + + + + + --preserve-ld-vars + + + When clearing the environment internally, preserve all variables + starting with LD_. This is mostly for debugging purposes. + + + + + + --version + + + Print the version of the GDM daemon. + + + + + + --wait-for-go + + + If started with this option, gdm will init, but only start the + first local display and then wait for a GO message in the fifo + protocol. No greeter will be shown until the GO message is + sent. Also flexiserver requests will be denied and XDMCP will + not be started until GO is given. This is useful for + initialization scripts which wish to start X early, but where + you don't yet want the user to start logging in. So the script + would send the GO to the fifo once it is ready and GDM will + then continue. This functionality was added in version + 2.5.90.0. + + + + + + + + <command>gdmsetup</command> Command Line Options + + + gdmsetup runs a graphical application for modifying + the GDM configuration file. Normally on systems that support + the PAM userhelper, this is setup such that when you run + gdmsetup as an ordinary user, it will first + ask you for your root password before starting. Otherwise, this + application may only be run as root. This application supports + standard GNOME options. + + + + + <command>gdm-restart</command> Command Line Options + + + gdm-restart stops and restarts GDM by sending + the GDM daemon a HUP signal. This command will immediately terminate + all sessions and log out users currently logged in with GDM. + + + + + <command>gdm-safe-restart</command> Command Line Options ---> - -
- - - - - - Manuel de configuration de l'écran de connexion V&manrevision; - - 2004 Sun Microsystems - - - Projet de documentation GNOME &legal; - Sun Équipe de documentation GNOME Sun Microsystems - - - - - - Manuel de configuration de l'écran de connexion V&manrevision; &date; - Équipe de documentation Sun GNOME - Projet de documentation GNOME - - - Le présent manuel décrit la version &appversion; de l'&app;. - Votre avis - Pour signaler un problème ou émettre une suggestion concernant l'application &app; ou le présent manuel, procédez comme indiqué à la GNOME Feedback Page. - - - Configuration de l'écran de connexion -Introduction -Pour démarrer une session du bureau GNOME, les utilisateurs doivent se connecter pour authentifier leur identité. L'écran de connexion constitue, pour l'utilisateur, une passerelle vers le bureau GNOME. L'application &app; permet de paramétrer la connexion des utilisateurs au système. - - - - - - Démarrage - - - Démarrage de &app; - - Vous pouvez démarrer &app; en recourant à l'une des méthodes suivantes : - - - Menu - Pour de plus amples informations sur le démarrage de &app; à partir d'un menu, reportez-vous à la dernière version du &ug; correspondant à votre plate-forme. - - - Ligne de commande - Exécutez la commande suivante : gdmsetup - - - -Vous devez disposer de privilèges d'administrateur système ou d'accès root pour configurer l'écran de connexion. - - - - Lancement de &app; - - Lorsque vous lancez &app;, la boîte de dialogue suivante apparaît. - -
- Boîte de dialogue &app; - - - - - Affiche la boîte de dialogue Configuration de l'écran de connexion. Le contexte décrit le graphique. - - -
- -La boîte de dialogue &app; contient les onglets suivants : - -Général ; -Bannière standard ; -Bannière graphique ; -Sécurité ; -XDMCP. - - - - - - - - - - -Préférences - - -Général -L'onglet Général vous permet de définir vos préférences générales concernant l'écran de connexion. - - - Locale - Sélectionnez le type d'interface à utiliser pour l'écran de connexion lorsque les utilisateurs se connectent à partir d'un système local. Sélectionnez une des options proposées dans la liste déroulante : - -Bannière graphique : sélectionnez cette option pour utiliser un écran de connexion graphique lorsque les utilisateurs se connectent à partir d'un système local. - -Bannière standard : sélectionnez cette option pour utiliser l'écran de connexion GNOME standard lorsque les utilisateurs se connectent à partir d'un système local. - - - - Distante - Sélectionnez le type d'interface à utiliser pour l'écran de connexion lorsque les utilisateurs se connectent à partir d'un système distant. Sélectionnez une des options proposées dans la liste déroulante : -Bannière graphique : sélectionnez cette option pour utiliser un écran de connexion graphique lorsque les utilisateurs se connectent à partir d'un système distant. - -Bannière standard : sélectionnez cette option pour utiliser l'écran de connexion GNOME standard lorsque les utilisateurs se connectent à partir d'un système distant. - - - - - Utiliser le format 24 heures pour l'horloge -Sélectionnez cette option pour afficher l'heure au format 00.00 - 24.00 dans l'écran de connexion. - - - - Chaîne de bienvenue -Entrez un message de bienvenue à afficher sur l'écran de connexion GNOME standard lorsque les utilisateurs se connectent à partir d'un système local. Si vous souhaitez que s'affiche le nom du système dans le message de bienvenue, entrez %ndans cette zone de texte. - - - - Chaîne de bienvenue distante -Entrez un message de bienvenue à afficher sur l'écran de connexion GNOME standard lorsque les utilisateurs se connectent à partir d'un système distant. - - - - Connecter un utilisateur automatiquement au premier démarrage -Sélectionnez cette option pour connecter un utilisateur automatiquement lorsqu'il démarre le système pour la première fois. - - - - Nom d'utilisateur de connexion automatique -La zone de liste déroulante modifiable vous permet d'entrer le nom d'utilisateur utilisé par le système pour une connexion automatique. - - - - Connecter un utilisateur automatiquement après un nombre de secondes défini -Sélectionnez cette option pour connecter un utilisateur automatiquement après l'intervalle de temps de votre choix. - - - - Nom d'utilisateur de connexion différée -Utilisez la zone de liste déroulante modifiable pour entrer le nom d'utilisateur utilisé par le système pour une connexion automatique après un intervalle de temps déterminé. - - - Secondes avant la connexion -Utilisez la zone de sélection numérique pour spécifier l'intervalle de temps devant s'écouler avant de connecter l'utilisateur automatiquement. - - - - - - - -Bannière standard -L'onglet Bannière standard vous permet de définir vos préférences concernant l'écran de configuration standard de GNOME. - - - - - Logo -Choisissez une image à afficher comme logo dans l'écran de configuration standard de GNOME. Pour choisir une image, entrez le nom de fichier correspondant dans la zone de liste déroulante modifiable. Vous pouvez également cliquer sur le bouton Parcourir pour afficher une boîte de dialogue vous permettant de choisir une image. - - - - Afficher des images d'utilisateur sélectionnables (navigateur de figures) -Sélectionnez cette option pour afficher des images d'utilisateurs dans l'écran de configuration standard de GNOME. Si cette option est activée, les utilisateurs peuvent sélectionner une image au lieu d'entrer un nom d'utilisateur. - - - - Pas d'arrière-plan -Sélectionnez cette option si vous ne souhaitez pas afficher d'image ou de couleur dans l'arrière-plan de l'écran de configuration standard de GNOME. - - - - Image -Sélectionnez cette option pour afficher une image dans l'arrière-plan de l'écran de configuration standard de GNOME. Pour choisir une image, entrez le nom de fichier correspondant dans la zone de liste déroulante modifiable située à droite de la boîte de dialogue. Vous pouvez également cliquer sur le bouton Parcourir situé tout à fait à droite de la boîte de dialogue pour afficher une boîte de dialogue permettant de choisir une image. - - - - Couleur -Sélectionnez cette option pour afficher une couleur dans l'arrière-plan de l'écran de configuration standard de GNOME. Utilisez le bouton Couleur d'arrière-plan pour la spécifier. - - - - Ajuster l'image d'arrière-plan pour remplir l'écran -Si vous sélectionnez l'option Image, activez cette option pour ajuster l'image d'arrière-plan à l'écran de configuration standard de GNOME. Les proportions de l'image sont respectées. - - - - Couleur uniquement pour les affichages distants -Sélectionnez cette option pour afficher une couleur en arrière-plan de l'écran de configuration standard de GNOME lorsque les utilisateurs se connectent à partir d'un système distant. - - - - - Couleur d'arrière-plan -Si vous sélectionnez l'option Couleur ou Couleur uniquement pour les affichages distants pour l'arrière-plan, utilisez ce bouton pour spécifier la couleur. Cliquez sur le bouton Couleur d'arrière-plan pour afficher la boîte de dialogue de sélection de couleur. Choisissez la couleur requise. - - - - - - - -Bannière graphique -L'onglet Bannière graphique vous permet de définir vos préférences pour l'écran de configuration graphique de GNOME. - - - - Liste de thèmes -Sélectionnez un thème à afficher dans l'écran de configuration graphique. La partie droite de la boîte de dialogue fournit un aperçu du thème sélectionné. - - - - Installer un nouveau thème -Vous pouvez ajouter un thème à la liste disponible. Le nouveau thème doit être un fichier d'archive tar zippé, c'est-à-dire qu'il doit s'agir d'un fichier .tar.gz.Pour créer un nouveau thème, procédez comme suit : - -Cliquez sur le bouton Installer un nouveau thème. -Utilisez la boîte de dialogue pour sélectionner le fichier d'archive. -Cliquez sur OK. - - - - - Supprimer le thème -Pour supprimer un thème, sélectionnez-le puis cliquez sur le bouton Supprimer le thème. - - - - - - - -Sécurité -L'onglet Sécurité vous permet de définir vos préférences concernant l'écran de connexion. - - - Autoriser root à se connecter en local avec GDM -Sélectionnez cette option pour autoriser les utilisateurs disposant de privilèges d'administrateurs ou d'accès root à utiliser GDM (GNOME Display Manager) pour se connecter à partir d'un système local. -Les systèmes prenant en charge les modules d'authentification enfichables (PAM) ignorent cette option. Les bibliothèques PAM déterminent si l'utilisateur est présent sur le système local. - - - - - Autoriser root à se connecter à distance avec GDM -Sélectionnez cette option pour autoriser les utilisateurs disposant de privilèges d'administrateurs ou d'accès root à utiliser GDM pour se connecter à partir d'un système distant. - - - - Autoriser les connexions différées à distance -Sélectionnez cette option pour autoriser GDM à connecter automatiquement l'utilisateur après un intervalle de temps determiné, à partir d'un système distant. - - - - Afficher le menu actions -Sélectionnez cette option pour permettre aux utilisateurs d'utiliser le menu Actions dans l'écran de connexion. - - - - Autoriser la configuration à partir de l'écran de connexion -Sélectionnez cette option pour pouvoir utiliser l'élément Configurer le gestionnaire de connexion du menu Actions dans l'écran de connexion. - - - - Autoriser l'exécution du sélecteur XDMCP à partir de l'écran de connexion -Sélectionnez cette option pour pouvoir utiliser l'élément Exécuter le sélecteur _XDMCP du menu Actions dans l'écran de connexion.L'élément Exécuter le sélecteur _XDMCP affiche une liste d'hôtes proposant des services de gestion d'affichage. Les utilisateurs peuvent se servir cette liste pour charger un hôte de gérer une session. - - - - Toujours interdire les connexions TCP au serveur _X (désactive toutes les connexions distantes) -Sélectionnez cette option si vous ne souhaitez pas que les utilisateurs puissent se connecter au serveur X Window System à partir de systèmes distants. - - - - Délai entre chaque tentative (secondes) -Utilisez la zone de sélection numérique pour spécifier l'intervalle de temps devant s'écouler entre un échec de connexion et la réactivation du champ Nom d'utilisateur de l'écran de connexion. -Les systèmes prenant en charge les modules d'authentification enfichables (PAM) ignorent cette option. - - - - - - - - -XDMCP -L'onglet XDMCP vous permet de définir vos préférences concernant le protocole XDMCP (X Display Manager Control Protocol). - - - - Activer XDMCP -Sélectionnez cette option pour permettre à un affichage X Windows System distant de solliciter une session X Windows System à partir du système. - - - - Accepter les requêtes indirectes -Sélectionnez cette option pour permettre aux affichages X Windows System distants ne disposant pas d'un gestionnaire d'affichage de solliciter des services de gestion d'affichage XDMCP à partir de ce système. - - - - Écouter sur le port UDP -Utilisez la zone de sélection numérique pour spécifier le numéro de port sur lequel rechercher les requêtes UDP (User Datagram Protocol). - - - - Nombre maximal de requêtes en attente -Utilisez la zone de sélection numérique pour spécifier le nombre maximal de requêtes en attente émises par le système. Cette option aide à éviter les attaques par déni de service. Elle permet de spécifier le nombre d'affichages pouvant être sollicités par session, mais pas le nombre total de sessions distantes autorisées par GDM. - - - - - Nombre maximal de requêtes indirectes en attente -GDM crée une file d'attente des requêtes de sessions émises par le système. Utilisez la zone de sélection numérique pour spécifier le nombre maximal de requêtes de session en attente émises par des affichages ne disposant pas de gestionnaire d'affichage. - - - - Nombre maximal de sessions distantes -Utilisez la zone de sélection numérique pour spécifier le nombre total de sessions distantes autorisées par GDM. - - - - Délai d'attente maximal -Utilisez la zone de sélection numérique pour spécifier l'intervalle de temps devant s'écouler avant que GDM ne supprime une requête de la file d'attente. - - - - Délai d'attente indirecte maximale -Utilisez la zone de sélection numérique pour spécifier l'intervalle de temps devant s'écouler avant que GDM ne supprime les affichages ne disposant pas d'un gestionnaire d'affichage de la file d'attente des affichages sollicitant une session. - - - - Nombre d'affichages par hôte -Utilisez la zone de sélection numérique pour spécifier le nombre total de sessions distantes autorisées par GDM à partir d'un hôte. - - - - Intervalle de ping (secondes) -GDM effectue des pings sur les sessions pour vérifier si celles-ci sont toujours actives. Utilisez la zone de sélection numérique pour spécifier l'intervalle de temps devant s'écouler entre chaque ping de GDM. - - - - - - - -
\ No newline at end of file + + gdm-safe-restart stops and restarts GDM by + sending the GDM daemon a USR1 signal. GDM will be restarted as soon + as all users log out. + + + + + <command>gdm-stop</command> Command Line Options + + + gdm-stop stops GDM by sending the GDM daemon + a TERM signal. + + + + + + GDM Internal Commands + + + The GDM package provides the following different commands in + libexecdir intended to be used by the gdm + daemon process. + + + + <command>gdmchooser</command> and <command>gdmlogin</command> + Command Line Options + + + The gdmgreeter and gdmlogin + are two different login applications, either can be used by GDM. + gdmgreeter is themeable with GDM themes while + gdmlogin is themable with GTK+ themes. These + applications are normally executed by the GDM daemon. Both commands + support standard GNOME options. + + + + + <command>gdmchooser</command> Command Line Options + + + The gdmchooser is the XDMCP chooser application. + The gdmchooser is normally executed by the GDM + daemon. It supports the following options for XDM compatibility. + This command supports standard GNOME options and is found in + support standard GNOME options. + + + + <command>gdmchooser</command> Command Line Options + + + --xdmaddress=SOCKET + + + Socket for XDM communication. + + + + + + --clientaddress=ADDRESS + + + Client address to return in response to XDM. This option is for + running gdmchooser with XDM, and is not used within GDM. + + + + + + --connectionType=TYPE + + + Connection type to return in response to XDM. This option is for + running gdmchooser with XDM, and is not used within GDM. + + + + + + + + <command>gdm-ssh-session</command> + + + The gdm-ssh-session is normally executed by the + GDM daemon when starting a secure remote connection through ssh. + It does not take any options. + + + + + + + + + Themed Greeter + + + This section describes the creation of themes for the Themed + Greeter. For examples including screenshots, see the standard installed + themes and the themes from + + the theme website. + + + + Theme Overview + + + GDM Themes can be created by creating an XML file that follows the + specification in gui/greeter/greeter.dtd. Theme files are stored + in the directory + <share>/gdm/themes/<theme_name>. + Usually this would be under /usr/share. The theme + directory should contain a file called + GdmGreeterTheme.desktop which has similar format + to other .desktop files and looks like: + + + +[GdmGreeterTheme] +Encoding=UTF-8 +Greeter=circles.xml +Name=Circles +Description=Theme with blue circles +Author=Bond, James Bond +Copyright=(c) 2002 Bond, James Bond +Screenshot=screenshot.png + + + + The Name, Description, Author and Copyright fields can be translated + just like the other .desktopfiles. All the files + that are mentioned should be in the theme directory itself. The + Screenshot field points to a file which should be a 200x150 screenshot + of the theme in action (it is OK not to have one, but it makes it nicer + for user). The Greeter field points to an XML file that contains the + description of the theme. The description will be given later. + + + + Once you have theme ready and installed you can test it with the + installed gdmthemetester script. This script + assumes that the X server supports a nested server command. This + command takes two arguments, first the environment that should be used. + This is one of console, console-timed, flexi, remote-flexi, xdmcp. + Where console is a standard console login, console-timed is a console + login with a timed login going on, flexi is for any local flexible + display, remote-flexi is for flexi displays that are not local (such + as an Xnest flexiserver run from a remote display) and xdmcp is for + remote XDMCP connections. The second argument is the theme name. So + for example to test how things look in the XDMCP mode with the circles + theme you would run: + + + +gdmthemetester xdmcp circles + + + + Be sure to test all the environments with your theme, and make sure to + test how the caps lock warning looks by pressing caps lock. This is + also a good way to take screenshots, just take a screenshot of the + nested display window. This can be done in GNOME by focusing the + nested login window and pressing Alt-PrintScreen. + + + + Once you have all this done, then make a tarball that contains the + directory name (so that you could just untar it in the + <share>/gdm/themes directory). And this is + the tarball you distribute and people can install from the graphical + configuration application. You can do this with the commands: + +cd <share>/gdm/themes +tar czvf <theme_name>.tar.gz <theme_name>/ + + + + + + Detailed Description of Theme XML format + + + greeter tag + + + The GDM theme format is specified in XML format contained + within a <greeter> tag. You may specify a GTK+ theme to + be used with this theme by using the gtk-theme element in the + greeter tag as in the following example. + + + +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE greeter SYSTEM "greeter.dtd"> +<greeter gtk-theme="Crux"> +[...] +</greeter> + + + + Contained within the greeter tag can be the nodes described + in the next sections of this document. Some of these nodes are + containers (box nodes, rect item nodes) which can be used to + organize how to display the nodes that the user sees and interacts + with (such as button, pixmap and entry item nodes). + + + + + Box Nodes + + + Box nodes are container nodes for item nodes. Box nodes are + specified as follows: + +<box orientation="alignment" min-width="num" +xpadding="num" ypadding="num" spacing="num" +homogeneous="bool"> + + Where "num" means number and bool means either + "true" or "false" The alignment value can be + either "horizontal" or "vertical". If you leave + any property off it will default to zero or "false" in + case of "homogeneous" and "vertical" for the + orientation. + + + + If the box is homogeneous then the children are allocated equal + amount of space. + + + + The "min-width" must be specified in pixels. Obviously + there is also a corresponding "min-height" property as + well. + + + + + Fixed Nodes + + + Fixed is a container that has its children scattered about + laid out with precise coordinates. The size of this container + is the biggest rectangle that contains all the children. Fixed + has no extra properties and so you just use: + +<fixed> + + Then you put other items with proper position nodes inside this. + + + + The "toplevel" node is really just like a fixed node. + + + + + Item Nodes + + + A GDM Theme is created by specifying a hierarchy of item and box + nodes. Item nodes can have the following value for + "type": + + + + + button + + + A button field. This field uses a GTK+ button. It is also + possible to make a "rect" item act like a button by setting + its button element to true. However it is better to use + GTK+ buttons in GDM themes since these are accessible to + users with disabilities. Also, GTK+ buttons can be + themed. This feature is supported in GDM 2.14.6 and later. + + + + + + entry + + + Text entry field. + + + + + + label + + + A text label. Must have a "text" node to specify the + text. + + + + + + list + + + A face browser widget. Only useful if the face browser is + enabled via the configuration. + + + + + + pixmap + + + An pixmap image in a format that gdk-pixbuf supports like + PNG, JPEG, Tiff, etc...) + + + + + + rect + + + Rectangle. + + + + + + svg + + + Scaled Vector Graphic image. + + + + + + + For example: + +<item type="label"> + + Items can specify ID values which gives them a specific look and feel + or formatting. Furthermore you can customize the login process by + adding custom widgets with custom id's for some items (currently only + the list item) + + + + Entry items can have id values as follows: + + + + + user-pw-entry + + + Entry field for userid and password entry. This is the field + used for responses for the PAM/GDM questions (Username, + Password, etc..). + + + + + + + List items by default display as lists, but the + combo="true" attribute can be used to specify combo box + style (combo style supported since GDM 2.16.2). Some predefined + lists may be included in a theme by using the following id values. + Customized lists may also be defined, which are explained below. + + + + + session + + + A list of available sessions, which allows the user to pick + the session to use. Supported since GDM 2.16.2. + + + + + + + + language + + + A list of available languages, which allows the user to pick + the language to use. Supported since GDM 2.16.2. + + + + + + + + userlist + + + A Face Browser list, so that users can pick their username + by clicking on this instead of typing. This obviously exposes + the usernames to viewers of the login screen, and is not + recommended for users who feel that this reduces security. + The face browser does not support combo box style. + + + + + + + + userlist-rect + + + This id can be specified for the <rect> object containing + the userlist and if the userlist is empty then this rectangle + will not be shown. This allows the theme to define something + like an area with a different color and/or alpha to surround + the userlist, but only if there are users to display. + Supported since 2.16.2. + + + + + + + Furthermore, you can have an arbitrary id (I'd recommend starting + the id with 'custom' not to conflict with future additions to this + spec) and ask extra information of the user. See the section + 'Custom Widgetry' + + + + Label items can have id values as follows: + + + + + clock + + + Label that displays the date and time. + + + + + + pam-prompt + + + Label that displays the PAM prompt. This is the prompt that PAM + uses to ask for username, password, etc... + + + + + + pam-error + + + Label that displayst PAM/GDM error messages. Such as when user + can't log in. + + + + + + pam-error-logo + + + An image that will be displayed only when a pam-error message + is being displayed. This is useful for displaying an + "Attention" icon, for example. This feature is + supported in GDM 2.14.6 and later. + + + + + + pam-message + + + Label that displays the PAM message. These are messages that + PAM/GDM gives about state of the account, help about the + prompts and other information. + + + + + + timed-label + + + Label that displays timed login information. + + + + + + + Rectangles can have id values as follows: + + + + + caps-lock-warning + + + Displays an icon that shows if the + CAPS LOCK key is depressed. This rectangle + will be hidden/shown appropriately + + + + + + + If an item is of type rect, the item can be a button. Buttons + must also include a "button" value as follows: + +<item type="rect" id="disconnect_button" button="true">. + + + + + Possible values for button ids are as follows. + + + + + chooser_button + + + Runs the XDMCP chooser. + + + + + + config_button + + + Runs the GDM configuration application. + + + + + + custom_cmd_button[0-9] + + + Runs the n-th custom command. + + + + + + disconnect_button + + + Disconnect from remote session. + + + + + + language_button + + + Displays the language selection dialog. + + + + + + halt_button + + + Halt (shuts down) the system. + + + + + + reboot_button + + + Restart the system. + + + + + + session_button + + + List and select from available sessions. + + + + + + suspend_button + + + Suspend the system. + + + + + + system_button + + + Perform halt/restart/suspend/etc. options (if allowed by GDM + configuration). Also allows user to run configurator if user + enters root password (again if allowed by GDM configuration). + This is usually now labeled Actions, and referred to as the + Actions menu. + + + + + + + By default, the GDM login screen will disappear after authentication. + This can result in flicker between the login screen and the session. + The "background" property allows users to specify what + elements of the theme are the background image. When used, this + will cause GDM to remove all non-background items from the display + and render the remaining "background" items to the root + window. This can be used to create a smooth transition between the + login screen and the session. For example, if the GDM theme and the + session use the same background, then this will make the background + apear seamless. + + + + Item nodes may specify a "background" property which can be + set to "true" or "false" (not setting this + property is equivalent to "false"), as follows: + + + +<item type="rect" background="true"> + <normal file="background.svg"/> + <pos x="0" y="0" width="100%" height="-75"/> +</item> + + + + If no item node has "background" property set, then the + background is not modified when greeter exits. + + + + To use a different background for login transition than the one + used for login, insert a "item" node with "background" property set to "true" to draw login transition background before "item"e; node (without any "background" property) used for greeter background. For instance : + + +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE greeter SYSTEM "greeter.dtd"> + <greeter> + + <item type="rect" background="true"> + <normal file="background_for_login.svg"/> + <pos x="0" y="0" width="100%" height="100%"/> + </item> + <item type="rect"> + <normal file="background_for_greeter.svg"/> + <pos x="0" y="0" width="100%" height="100%"/> + </item> +[...] +</greeter> + + + + + Position Node + + + Each item can specify its position and size via the "pos" + node. For example: + +<pos x="0" y="4" width="100%" height="100%"/> + + + + + Both position and size can be given in percent and it will be taken + as the percentage of the size of the current container. For toplevel + items it's the percentage of the whole screen. + + + + For x and y, you can also specify a negative position which means + position from the right or bottom edge. But this only applies with + absolute coordinates. With percentage you can specify negative + position and it will be still from the same edge. + + + + The position also specifies the anchor of the item, this can be + "n" "ne" "e" "se" + "s" "sw" "w" and "nw" or + "center" which stand for the different edges/corners or + "center" for center. For example: + +<pos x="10%" y="50%" anchor="w" width="80%" height="95"/> + + + + + If the item contains a box, you can specify width and height to be + "box" to mean that they are supposed to be the width and + height of the box, that is the items in the box plus the padding. + + + + If the item contains an SVG image, you can specify width and height + to be "scale" to mean that the SVG image should be scaled + to fit the requested area. + + + + You can also specify an "expand" property to either be + "true" or false. If true then the child will be expanded + in the box as much as possible (that is it will be given more space + if available). + + + + There are two extra properties you can specify (as of 2.4.4.3) for + labels (and labels only). The first is "max-width" which + will specify the maximum width of the label in pixels. And the + second is "max-screen-percent-width" which specifies the + maximum percentage of the screen width that the label can occupy. + By default no label will occupy more then 90% of the screen by width. + An example may be: + +<item type="label"> +<pos x="10%" max-screen-percent-width="50%"/> + + + + + + Show Node + + + Some items may only display in certain modes, like when doing a + remote display. Multiple values can be specified and must be + separated with commas. The following values are possible: + + + + console - In console mode. + + + console-fixed - In console non-flexi mode. + + + console-flexi - In console & flexi mode. + + + flexi - In flexi mode. + + + remote - In remote mode. + + + remote-flexi - In remote & flexi mode. + + + + For example: + +<show modes="flexi,remote"/> + + + + + You can also specify the "type" value to indicate that + certain items should only be displayed if the type is true. Valid + values include the following: + + + + chooser, if ChooserButton is set to + "true" in the GDM configuration. + + + config, if ConfigAvailable is set to + "true" in the GDM configuration. + + + custom_cmd[0-9], if n-th + CustomCommand is specified in the GDM configuration. + + + halt, if HaltDaemon is specified in + the GDM configuration. + + + reboot, if RebootCommand is specified in + the GDM configuration. + + + suspend, if SuspendCommand is specified in + the GDM configuration. + + + system, if SystemMenu is specified in + the GDM configuration. + + + timed, if TimedLoginEnabled is set to + "true" in the GDM configuration. + + + + For example: + +<show modes="console" type="system"/> + + + + + Alternatively, you can specify a "min-screen-width" or + "min-screen-height" value to indicate that certain + items should only be displayed if the screen resolution is the + at least the given required size. + + + + For example: + +<show min-screen-height="768"/> + + + + + Note that if SystemMenu is off then the halt, restart, suspend, + chooser and config choices will not be shown, so this is a global + toggle for them all. See some of the standard themes for how the + show modes are used. + + + + + Normal/Active/Prelight Nodes + + + Depending on the item type (except for userlist - refer to Color node + below), it can specify its color, font, or image via the following + tags: + + + + normal - normal state. + + + active - when the item has active focus. + + + prelight - when the mouse is hovering over the + item. + + + + When item is "rect" (alpha can be omitted and defaults to + 0.0): + +<normal color="#ffffff" alpha="0.0"> + + + + + When item is "label" + +<normal color="#ffffff" font="Sans 14"/> + + + + + When the item type is "pixmap" or "SVG", then the + normal, active, and prelight tags specify the images to use as + follows: + +<normal file="picture.png" tint="#dddddd"/> + + + + + Note that relative pathnames are assumed to be in the same + directory as the theme .xml file in + <share>/gdm/themes/<theme_name>. + + + + Note that alternative image file can be specified using the altfile[n] + property. GDM will use the last valid image filename specified. + For example: + +<normal file="picture.png" altfile1="distribution-blah-image.png" altfile2="distribution-foo-image.png"/> + + If distribution-foo-image.png is a valid image + filename it will be used. Otherwise distribution-blah-image.png will + be used if valid. This feature supported since 2.16.3. + + + + + + Face Browser Icon/Label Color Nodes + + + If the item type is of userlist, then the background color for the + icon and label can be set separately via the the following tag: + + + + +<color iconcolor="#dddddd" labelcolor="#ffffff"/> + + + + + + Text Node + + + Text tags are used by labels. They can be used to display + localized text as follows (if the "xml:lang" attribute is + omitted, the C locale is assumed): + +<text xml:lang="fr">Option</text> + + + + + You can include pango markup in the text nodes for labels, however + you must encode it. So for example to have the label of + "foo<sup>bar</sup>", you must type: + +<text>"foo<sup>bar</sup>"</text> + + + + + Text nodes can contain the following special character sequences + which will be translated as follows: + + + + %% - A literal % character + + + %c - Clock time. Only labels with the "clock" id will + update automatically every second. Other labels will contain a + static timestamp. + + + %d - Display name (DISPLAY environment variable) + + + %h - Hostname (gethostname output) + + + %m - Machine name (uname.machine output) + + + %n - Node name (uname.nodename output) + + + %o - Domain name (getdomainname output) + + + %r - Release name (uname.release output) + + + %s - System name (uname.sysname output) + + + %t - Current timed delay value from configuration file (0 if off) + followed by the word "seconds" if value is greater than 1 + or the word "second" if the value is 1. This character + sequence is intended to be only used internally to display the + "timed-label" message, which is automatically updated every + second. + + + %u - Timed username value from configuration file (empty if off) + This character sequence is intended to be only used internally to + display the "timed-label" message, which is automatically + updated every second. + + + \n - Carriage return + + + _ - An underscore causes the following character to be underlined. + If it precedes a % character sequence, the string that replaces the + character sequence is underlined. + + + + + Stock + + + Certain common localized labels can be specified via the stock + tags. The "text" tag is ignored if the "stock" + tag is used. You should really use the stock labels rather then + just putting all the translations into the themes. This gives + faster load times and likely better translations. The following + values are valid: + + + + cancel, _("_Cancel" + + + caps-lock-warning, + _("Caps Lock key is on." + + + chooser, _("Remote Login via _XDMCP" + + + config, _("_Configure" + + + custom_cmd[0-9], _("Custom_[0-9]" + + + disconnect, _("D_isconnect" + + + halt, _("Shut _Down" + + + language, _("_Language" + + + ok, _("_OK" + + + quit, _("_Quit" + + + reboot, _("_Restart" + + + session, _("_Session" + + + startover, _("_Start Over" + + + suspend, _("Sus_pend" + + + system, _("_Actions" + (Formerly "S_ystem" + + + timed-label, + _("User %u will login in %t" + + + username-label, _("Username:" + + + welcome-label, _("Welcome to %n" + + + + For example: + +<stock type="welcome-label"> + + + + + + Custom Widgetry + + + Currently there is one item which is customizable and this is + the list item. If you need to ask the user extra things, such as + to pick from a list of places to log into, or set of custom login + sessions you can setup the list item and add listitem children that + describe the choices. Each listitem must have an id and a text + child. The choice will be recorded in the file + <ServAuthDir>/<display>.GreeterInfo + as <list id>=<listitem id>. + + + + For example suppose we are on display :0, + ServAuthDir is + <var>/lib/gdm and we have the following in the + theme: + + + +<item type="list" id="custom-config"> +<pos anchor="nw" x="1" y="1" height="200" width="100"> +<listitem id="foo"> +<text>Foo</text> +</listitem> +<listitem id="bar"> +<text>Bar</text> +</listitem> +</item> + + + + Then if the user chooses 'Foo' then + <var>/lib/gdm/:0.GreeterInfo will contain: + +custom-config=foo + + + + + + + + Accessibility + + GDM supports "Accessible Login", allowing users to log into + their desktop session even if they cannot easily use the screen, mouse, + or keyboard in the usual way. Accessible Technology (AT) programs + such as GOK (on-screen keyboard) and + orca (magnifier and text-to-speech) are supported. + The "GTK+ Greeter" best supports accessibility, so it is + recommended for accessibility support. The "Themed Greeter" + supports some accessibility features and may be usable by some users. + But some AT programs, such as GOK, do not yet work + with the "Themed Greeter". + + + + Accessibility is enabled by specifying the "GTK+ Greeter" + in the "Local" tab for the console display and specifying + the "GTK+ Greeter" in the "Remote" tab for + remote displays. Or you can modify the Greeter + and RemoteGreeter configuration options by hand + to be /usr/lib/gdmlogin. + + + + The GDM greeter programs support the ability to launch AT's at login + time via configurable "gestures". These gestures can be + defined to be standard keyboard hotkeys, switch device event, or + mouse motion events. When using the "GTK+ Greeter", the + user may also change the visual appearance of the login UI. For + example, to use a higher-contrast color scheme for better visibility. + + + + Note that gdmsetup does not yet work with + accessibility, so that users who require AT programs should only + configure GDM by editing the ASCII files directly. + + + + Accessibility Configuration + + + In order to enable Accessible Login, the system administrator must + make some changes to the default login configuration by manually + modifying three human-readable configuration files, stored in + the GDM Custom Configuration File, AccessKeyMouseEvents File, and + AccessDwellMouseEvents File. The AccessKeyMouseEvents and + AccessDwellMouseEvents contain reasonable default gestures for + launching GOK and orca, but + some users may require these gestures to be configured to best + meet their needs. For example, shorter or longer duration for + holding down a button or hotkey might make the login experience + more usable for some users. Also, additional AT programs may be + added to the configuration file if needed. + + + + Accessibile Theming + + + If using the "GTK+ Greeter" users can easily + switch the color and contrast scheme of the dialog. To do this, + ensure the AllowGtkThemeChange parameter in + the GDM configuration is set to "true". This should + be the default value. When true, the "Standard + Greeter" contains a menu allowing the user to change to a + different GTK+ theme. The GtkThemesToAllow + configuration choice can also be used to limit the choices + available as desired. For example: + + + +GtkThemesToAllow=HighContrast,HighContrastInverse + + + + If using the "Themed Greeter" there may be suitable + GDM themes available that provide needed color and contrast + schemes, but these are not yet shipped with the GDM program. + Some distributions may ship such themes. There is not yet any + mechanism to switch between themes in the "Themed + Greeter", so if an accessible theme is required by one + user, then all users would need to use the same theme. + + + + + AT Program Support + + + To enable user to launch AT such as the GOK + or orca, the + AddGtkModules parameter in the GDM + configuration must be set to "true". + Also the GtkModulesList parameter must be + uncommented and set as follows: + + + +GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener + + + + This causes all GDM GUI programs to be run with the appropriate + GTK modules for launching AT programs. The use of assistive + technologies and the atk-bridge module requires the registry + daemon, at-spi-registryd, to be running. + This is handled by the GDM GUI starting with version 2.17. + + + + System administrators may wish to load only the minimum subset + of these modules which is required to support their user base. + The "libkeymouselistener" provides hotkey and switch + gesture support while the "libdwellmouselistener" + provides mouse motion gesture support. If your user base only + requires one or the other, it is only necessary to include the + gesture listener that is needed. Also, some AT programs may not + require gail or atk-bridge. If you find the AT programs you + need works fine without including these, then they may be + omitted. Note that some AT programs work with a reduced feature + set if gail and/or atk-bridge are not present. However, for + general accessibility use, including all four is suitable. + + + + Once "keymouselistener" and/or + "dwellmouselistener" have been added to the + AddGtkModules loaded by GDM, then you may + need to modiify the gesture configurations to meet your user's + needs. Default gestures are provided for launching + GOK and orca, but it is + recommended to modify these gestures so they work best for your + user base. These gesture associations are contained in files + AccessKeyMouseEvents and + AccessDwellMouseEvents, respectively. Both + files are located in the + <etc>/gdm/modules directory. The + gesture configuration format is described in the comment section + of the two configuration files. + + + + The AccessKeyMouseEvents file controls the keymouselistener + Gesture Listener and is used to define key-press, mouse button, + or XInput device sequences that can be used to launch + applications needed for accessibility. In order to reduce the + likelihood of unintentional launch, these "gestures" + may be associated with multiple switch presses and/or minimum + durations. Note that the XKB extension is needed for key + gestures to work, so you may need to add +xkb to your X server + command line for gestures to work properly. The X server command + line is specified in the GDM configuration file in the + "server-foo" sections. + + + + The DwellKeyMouseEvents file controls the dwellmouselistner and + supports gestures that involve the motion of a pointing device + such as the system mouse of an alternative pointing device such + as a head pointer or trackball may also be defined. Motion + gestures are defined as "crossing events" into and out + of the login dialog window. If the + "dwellmouselistener" gesture listener is loaded, then + alternative pointing devices are temporarily "latched" + to the core pointer, such that motion from alternative devices + results in movement of the onscreen pointer. All gestures are + specified by the same syntax; that is, there is no distinction + between a "core mouse" gesture and motion from an + alternate input device. + + + + On some operating systems, it is necessary to make sure that the + GDM user is a member of the "audio" group for AT + programs that require audio output (such as text-to-speech) to + be functional. + + + + Currently GDM does not remember what accessible technology + programs have been started when switching applications. So if + the user switches between the login program and the chooser, for + example, then it is necessary for the user to redo the gesture. + Users may need to also set up their default session so that the + assistive technologies required are started automatically (or + have appropriate key-bindings defined to start them) after the + user session has started. + + + + + AT Troubleshooting + + + There are some common issues that cause users to have problems + getting the gesture listeners to work. It is recommended that + people use GDM version 2.18.0 or later for best results. + + + + Some older X servers have a bug which causes detectable + autorepeat to fail when XEVIE is enabled (which happens when + atk-bridge is included as a GTK Module). This bug causes key + gestures with a duration greater than 0 to always fail. A + workaround is to simply redefine all key gestures so they have + zero length duration, or upgrade your X server. + + + + Some versions of GOK and + orca will not launch unless the + "gdm" user has a writable home directory. This has + been fixed in GNOME 2.18, but if using an older version of + GNOME, then making sure that the GDM user has a writable home + directory should make these programs functional. + + + + If you see an hourglass cursor when you complete a gesture but + the program does not start, then this indicates that the gesture + was received, but that there was a problem starting the program. + Most likely the issue may be the lack of a writable gdm home + directory. + + + + Also note that some input devices require X server configuration + before GDM will recognize them. + + + + + Accessibility Login Sound Configuration + + + By default, GDM requires a media application such as + "play" to be present to play sounds for successful or + failed login. GDM defaults + the location of this application to + <bin>/play (or + <bin>/audioplay on Solaris. This can + be changed via the SoundProgram GDM + configuration option. Typically most text-to-speech programs + (such as orca) use a separate mechanism to + play audio, so this configuration setting is not needed for + them to work. + + + + + + + Solaris Specific Features + + + Using GDM on Solaris + + + GDM is not yet the default login program on Solaris. If you wish + to switch to using GDM, then you need to turn off CDE login and + start the GDM service. Note that turning off or disabiling CDE + login will cause any running sessions to immediately exit, and any + unsaved data will be lost. Only run these commands if you are + sure there is no unsaved data in your running sessions. It would + be best to run these commands from console login, or a Failsafe + Terminal rather than from a running GUI session. The first step + is to run the following command to see if CDE login is running as + an SMF service. + + + +svcs cde-login + + + + If the svcs command responds that this + service is enabled, then run this command to disable CDE login: + + + +svcadm disable cde-login + + + + If the svcs command responds that this pattern + doesn't match any instances, then run these commands to stop + CDE login: + + + +/usr/dt/config/dtconfig -d +Either reboot, or kill any running dtlogin processes. + + + + At this point you will be presented with a console login. Login + as root, and run the following command. If on Solaris 10 the + servicename is "gdm2-login", if on Solaris Nevada the + servicename is "gdm". + + + +svcadm enable servicename + + + + + Solaris Configuration + + On Solaris, the following configuration is recommended. + This turns on IPv6 and also turns on PreFetch for + performance benefit. + + +./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var + --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin + --with-prefetch --with-post-path=/usr/openwin/bin --with-pam-prefix=/etc + --with-lang-file=/etc/default/init + + + + + Configuring GDM with the + "--with-post-path=/usr/openwin/bin" on Solaris is + recommended for accessing X server programs. + + + + + Solaris /etc/logindevperm + + GDM supports /etc/logindevperm, but only on Solaris 10 and + higher. Refer to the logindevperm.4 man page for more + information. + + + + To make /etc/logindevperm functionality work on Solaris 9 or + earlier you would have to hack the GDM PreSession and + PostSession script to chmod the device permissions directly. In + other words, if /etc/logindevperm had a listing like this: + + + +/dev/console 0600 /dev/sound/* # audio devices + + + + Then the PreSession script would need to be modified to chown + /dev/console to the user:group who is logging into the console + and ensure whatever permissions is specified in /etc/logindevperm + (0600 for the line above). Then in the PostSession script chmod + the device back to root:root and ensure 0600 this time (do not + use the value in the /etc/logindevperm file). Linux uses a + different mechanism for managing device permissions, so this + extra scripting is not needed. + + + + + Solaris Automatic Login + + Automatic login does not work on Solaris 10 and earlier because + PAM is not configured to support this feature by default. + Automatic login is a GDM feature that is not enabled by default, + so you would only notice this problem if you try to make use of + it. Turning this feature on causes your computer to login to a + specified username on startup without asking for username + and password. This is an insecure way to set up your + computer. + + + + If using Solaris 10 or lower, then you need to compile the + pam_allow.c code provided with the GDM release and install it + to /usr/lib/security (or provide the full path in /etc/pam.conf) + and ensure it is owned by uid 0 and not group or world writable. + + + + The following are reasonable pam.conf values for turning on + automatic login in GDM. Make sure to read the PAM documentation + (e.g. pam.d/pam.conf man page) and be comfortable with the + security implications of any changes you intend to make to + your configuration. + + + + gdm-autologin auth required pam_unix_cred.so.1 + gdm-autologin auth sufficient pam_allow.so.1 + gdm-autologin account sufficient pam_allow.so.1 + gdm-autologin session sufficient pam_allow.so.1 + gdm-autologin password sufficient pam_allow.so.1 + + + + The above setup will cause no lastlog entry to be generated. If + a lastlog entry is desired, then use the following for session: + + + + gdm-autologin session required pam_unix_session.so.1 + + + + + Solaris RBAC support for Shutdown, Reboot, and Suspend + + + Starting with GDM 2.19, GDM supports RBAC (Role Based + Access Control) for enabling the system commands (Shutdown, + Reboot, Suspend, etc.) that appear in the greeter system + menu and via the gdmflexiserver + QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and + SET_SAFE_LOGOUT_ACTION commands. + + + + On Solaris GDM has the following value specified for the + RBACSystemCommandKeys configuration + option. + + + +HALT:solaris.system.shutdown;REBOOT:solaris.system.shutdown + + + + This will cause the SHUTDOWN and REBOOT features to only be + enabled for users who have RBAC authority. In other words, + those users who have the "solaris.system.shutdown" + authorization name specified. The GDM greeter will only + display these options if the gdm user (specified in the + User configuration option, "gdm" by + default) has such RBAC permissions. + + + + Therefore, add the "solaris.system.shutdown" + authorization name to the /etc/user_attr + for all users who should have authority to shutdown and + reboot the system. If you want these options to appear in + the greeter program, also add this authorization name to + the gdm user. If you don't want to use RBAC, then you may + unset the RBACSystemCommandKeys GDM + configuration key, and this will make the system commands + available for all users. Refer to the + user_attr man page for more information + about setting RBAC privileges. + + + + Note that on Solaris there are two programs that can be used + to shutdown the system. These are GDM and + gnome-sys-suspend. + gnome-sys-suspend is a GUI front-end for + the sys-suspend. + + + + If GDM is being used as the login program and the user has + RBAC permissions to shutdown the machine (or RBAC support + is disabled in GDM), then the GNOME panel + "Shut Down.." option will use GDM to shutdown, reboot, + and suspend the machine. This is a bit nicer than using + gnome-sys-suspend since GDM will wait until + the user session has finished (including running the + PostSession script, etc.) before running the + shutdown/reboot/suspend command. Also the + gnome-sys-suspend command is less functional + since it does not support a reboot option, only shutdown and + suspend. + + + + If GDM is not being used to manage shutdown, reboot, and + suspend; then the GNOME panel uses + gnome-sys-suspend when you select the + "Shut Down..." option from the application menu. + If the pop-up that appears when you select this only + shows the suspend and shutdown options, then you are + likely using gnome-sys-suspend. If + you are using this, then refer to the + sys-suspend man page for information + about how to configure it. Or consider using GDM and + configuring it to provide these options. + + + + + Other Solaris Features + + GDM supports a few features specific to Solaris, as follows: + + + + GDM supports Solaris Auditing if running on Solaris 10 or + higher. GDM should not be used if auditing is needed and + running Solaris 9 or older. + + + + GDM supports a security feature which causes the X server to + run as the user instead of as the root user. GDM must be using + PAM for this feature to be enabled, which is the normal case + for Solaris. This second feature has the side-effect of + causing the X server to always restart between sessions, which + disables the AlwaysRestartServer configuration option. + + + + Solaris supports the /etc/default/login + interface, which affects the DefaultPath, + RootPath, + PasswordRequired, and + AllowRemoteRoot options as described in the + "Configuration" section. + + + + + + Example Configurations + + + This section has some example configurations that are useful for + various setups. + + + + Terminal Lab With One Server + + + Suppose you want to make a lab full of X terminals that all connect + to one server machine. So let's call one X terminal + xterminal and let's call the server machine + appserver. You install GDM on both. + + + + On appserver you enable XDMCP, so you have + +[xdmcp] +Enable=true + + If you want no local screens here, you can then + make the [servers] section empty. + + + + On the xterminal you disable XDMCP (you don't + want anyone to connect to the xterminal really). You will add a + server type perhaps called Terminal as follows: + +[server-Terminal] +name=Terminal server +command=/path/to/X -terminate +flexible=false +handled=false + + This definition should in fact be included in the standard + configuration file. Notice that we made the + handled key false since we don't want GDM to + handle this server localy. Also note that we have not yet added the + -query argument, you can add that here, or in the + [servers] section. We'll define our local + servers as follows: + +[servers] +0=Terminal -query appserver + + This will run a direct XDMCP query to the server named + appserver. + + + + + Terminal Lab With Two Or More Servers + + + Suppose you want to make a lab full of X terminals that all connect + to some choice of servers. For now let's make it + appserverone and + appservertwo. Again we'll call our example X + terminal server xterminal. The setup on both + servers is the same as with the case of one server in the previous + section. You do not need to explicitly enable indirect queries on the + server since we'll run the choosers locally on the X terminals. + + + + So on the xterminal you again disable XDMCP. + You will add a server type perhaps called Chooser + as follows: + +[server-Chooser] +name=Chooser server +command=/path/to/X +flexible=false +chooser=true + + And again this definition should in fact be included in the standard + configuration file. Notice that we made the + chooser key true here. This will run the XDMCP + chooser for this server, and when the user chooses a host GDM will run + a query for that host. Then we will define our local servers as + follows: + +[servers] +0=Chooser + + + + + The XDMCP chooser on the X terminal will normally give a broadcast + query to see which servers exist on the network. If the two servers + are not reachable by a broadcast query, you must add them by hand to + the configuration file. So in the [chooser] + section you would have: + +Hosts=appserverone,appservertwo + + and any other servers you wish the users to be able to connect to. + + + + Sometimes you may want to run the chooser on the server side however. + Then what you want to do is to run a configuration similar to the + previous section about the one server configuration with XDMCP + indirect queries enabled on appserver and on the + X terminals you'd have + +[servers] +0=Terminal -indirect appserver + + This way for example you only have to maintain one + Hosts entry. However as a disadvantage then, + the appserver must then always be available. So + it's not good for situations where you want to have several servers + and not all of them have to be on all the time. You could also have + one of the X terminals handle indirect XDMCP queries and serve up the + chooser to the other X terminals. + + + + + Defining Custom Commands + + + Suppose you want to add a custom command to the GDM menu that will give + you the oportunity to boot into other operating system such as Windoze. + Jsut add the following options into the + [customcommand] section of the GDM configuration + file. + + + [customcommand] + CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze + CustomCommandLabel0=_Windoze + CustomCommandLRLabel0=Reboot into _Windoze + CustomCommandText0=Are you sure you want to restart the computer into Windoze? + CustomCommandTooltip0=Restarts the computer into Windoze + CustomCommandIsPersistent0=true + + + CustomCommand0 specifies two commands separated by a semicolon: + /sbin/rebootwindoze and + /usr/local/sbin/rebootwindoze. GDM will use + the first valid command in the list. This allows different + commands for different operating systems to be included. + + + Note, that besides being able to customise this option to reboot into + different operating systems you can also use it to define your own + custom behaviours that you wish to run from the GDM menu. Suppose you + want to give users the oportunity to run system update scripts from the + login screen. Add the following options into the + [customcommand] section of your GDM configuration + file. + + + [customcommand] + CustomCommand0=/sbin/updatesystem;/usr/local/sbin/updatesystem + CustomCommandLabel0=_Update Me + CustomCommandLRLabel0=Update the system + CustomCommandText0=Are you sure you want to update the system software? + CustomCommandTooltip0=Updates the system + CustomCommandNoRestart0=true + + + + + Both custom commands could be defined as follows. + + + [customcommand] + CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze + CustomCommandLabel0=_Windoze + CustomCommandLRLabel0=Reboot into _Windoze + CustomCommandText0=Are you sure you want to restart the computer into Windoze? + CustomCommandTooltip0=Restarts the computer into Windoze + CustomCommandIsPersistent0=true + + CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem + CustomCommandLabel1=_Update Me + CustomCommandLRLabel1=Update the system + CustomCommandText1=Are you sure you want to update the system software? + CustomCommandTooltip1=Updates the system + CustomCommandNoRestart1=true + + + + + There can be up to 10 custom commands numbered 0-9. + + + [customcommand] + CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/rebootwindoze + CustomCommandLabel0=_Windoze + CustomCommandLRLabel0=Reboot into _Windoze + CustomCommandText0=Are you sure you want to restart the computer into Windoze? + CustomCommandTooltip0=Restarts the computer into Windoze + CustomCommandIsPersistent0=true + + CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem + CustomCommandLabel1=_Update Me + CustomCommandLRLabel1=Update the system + CustomCommandText1=Are you sure you want to update the system software? + CustomCommandTooltip1=Updates the system + CustomCommandNoRestart1=true + + CustomCommand3=/sbin/do_something + . + . + . + + CustomCommand4=/sbin/do_something_else + . + . + . + + + + + + + Troubleshooting + + + This section discusses helpful tips for getting GDM working. In general, + if you have a problem using GDM, you can submit a bug to the + "gdm" category in + bugzilla.gnome.org + or send an email to the +
gdm-list@gnome.org
mail list. + + + + If GDM is failing to work properly, it is always a good idea to include + debug information. Use the gdmsetup command to turn + on debug ("Enable debug messages to system log" checkbox in the + "Security" tab), then use GDM to the point where it fails, and + include the GDM output sent to your system log + (<var>/log/messages or + <var>/adm/messages depending on your operating + system). Since the system log can be large, please only include the GDM + debug information and do not sent the entire file. If you do not see any + GDM syslog output, you may need to configure syslog (see syslog.3c man + page). + + + + You should not leave debug on after collecting data. It will clutter your + syslog and slow system performance. + + + + GDM Will Not Start + + + There are a many problems that can cause GDM to fail to start, but + this section will discuss a few common problems and how to approach + tracking down a problem with GDM starting. Some problems will + cause GDM to respond with an error message or dialog when it tries + to start, but it can be difficult to track down problems when GDM + fails silently. + + + + First make sure that the X server is configured properly. The + GDM configuration file contains a command in the [server-Standard] + section that is used for starting the X server. Verify that this + command works on your system. Running this command from the + console should start the X server. If it fails, then the problem + is likely with your X server configuration. Refer to your X server + error log for an idea of what the problem may be. The problem may + also be that your X server requires different command-line options. + If so, then modify the X server command in the GDM configuration file + so that it is correct for your system. + + + + Another common problem is that the GDM greeter program is having + trouble starting. This can happen, for example, if GDM cannot find + a needed library or other resource. Try starting the X server and + a terminal program, set the shell environment variable + DOING_GDM_DEVELOPMENT=1 and run + <lib>/gdmlogin + or <lib>/gdmgreeter. Any error messages + echoed to the terminal will likely highlight the problem. Also, + turning on debug and checking the output sent to the system log + will often highlight the problem. + + + + Also make sure that the /tmp directory has + reasonable ownership and permissions, and that the machine's file + system is not full. These problems will cause GDM to fail to start. + + + + + GDM Will Not Access User Settings + + + GDM saves user settings, such as your default session and default + language, in the ~/.dmrc. Other files, such + as the user's ~/.Xauthority file will also + affect login. GDM, by default, is strict about how it tries to + access files in the user's home directory, and will ignore the file if + they do not conform to certain rules. You can use the + RelaxPermissions configuration option to + make GDM less strict about how it accesses files in the user's + home directory, or correct the permissions issues that cause GDM + to ignore the file. This is discussed in detail described in the + "File Access" section of the "Overview". + + + + + + + + License + + This program is free software; you can redistribute it and/or + modify it under the terms of the + GNU General Public License as + published by the Free Software Foundation; + either version 2 of the License, or (at your option) any later + version. + + + This program is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + + A copy of the GNU General Public License is + included as an appendix to the GNOME Users + Guide. You may also obtain a copy of the + GNU General Public License from the Free + Software Foundation by visiting their Web site or by writing to +
+ Free Software Foundation, Inc. + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 + USA +
+ + + + diff --git a/po/ChangeLog b/po/ChangeLog index 1d2c2bfa..12463eca 100644 --- a/po/ChangeLog +++ b/po/ChangeLog @@ -1,3 +1,8 @@ +2007-09-11 William Jon McCann + + * POTFILES.in: + Fix distcheck + 2007-04-25 Christophe Merlet * oc.po: Added Occitan translation from diff --git a/po/POTFILES.in b/po/POTFILES.in index 0a26a78d..dc4b81c8 100644 --- a/po/POTFILES.in +++ b/po/POTFILES.in @@ -1,6 +1,5 @@ # Files with translatable strings. # Please keep this file in alphabetical order. -common/gdm-address.c common/gdm-common.c common/gdm-log.c common/gdm-md5.c @@ -23,12 +22,12 @@ daemon/choose.c daemon/factory-slave-main.c daemon/filecheck.c daemon/fstype.c -daemon/gdm-ck-session.c daemon/gdm-display.c daemon/gdm-display-store.c daemon/gdm-factory-slave.c -daemon/gdm-greeter-proxy.c +daemon/gdm-greeter-session.c daemon/gdm-greeter-server.c +daemon/gdm-local-display-factory.c daemon/gdm-manager.c daemon/gdm-product-display.c daemon/gdm-product-slave.c @@ -43,7 +42,7 @@ daemon/gdm-slave-proxy.c daemon/gdm-static-display.c daemon/gdm-static-factory-display.c daemon/gdm-xdmcp-display.c -daemon/gdm-xdmcp-manager.c +daemon/gdm-xdmcp-display-factory.c daemon/main.c daemon/product-slave-main.c daemon/session-worker-main.c @@ -52,6 +51,7 @@ daemon/test-session.c data/gdm.schemas.in.in gui/modules/dwellmouselistener.c gui/modules/keymouselistener.c +gui/simple-chooser/gdm-host-chooser-widget.c gui/simple-greeter/gdm-simple-greeter.c gui/simple-greeter/gdm-simple-greeter.glade gui/simple-greeter/greeter-main.c -- cgit v1.2.1