diff options
| author | Frederic Crozat <fcrozat@mandriva.com> | 2007-04-30 09:13:26 +0000 |
|---|---|---|
| committer | Brian Cameron <bcameron@src.gnome.org> | 2007-04-30 09:13:26 +0000 |
| commit | 86153e833c70ab7f5f65be23c5454355e9e1bab1 (patch) | |
| tree | bd239547b998b607f8455029b971b6d3af87d099 /docs | |
| parent | 656509e03d96759e4dc5ade4fca0cae697c4805e (diff) | |
| download | gdm-86153e833c70ab7f5f65be23c5454355e9e1bab1.tar.gz | |
Add support for root background when login is accepted (bug #322056).
2007-04-30 Frederic Crozat <fcrozat@mandriva.com>
* gui/gdmcommon.c: (gdm_common_set_root_background):
* gui/gdmcommon.h:
* gui/gdmlogin.c: (setup_background):
* gui/greeter/greeter.c: (process_operation), (key_press_event),
(main):
* gui/greeter/greeter.dtd:
* gui/greeter/greeter_canvas_item.c:
(greeter_item_create_canvas_item):
* gui/greeter/greeter_item.c: (greeter_item_info_new):
* gui/greeter/greeter_item.h:
* gui/greeter/greeter_parser.c: (parse_items), (hide_item),
(greeter_show_only_background):
* gui/greeter/greeter_parser.h:
* gui/greeter/themes/circles/circles.xml:
* gui/greeter/themes/happygnome-list/happygnome.xml:
* gui/greeter/themes/happygnome/happygnome.xml:
Add support for root background when login is accepted
(bug #322056).
* gui/greeter/greeter_item_pam.c: (greeter_item_pam_error_set):
Code cleanup.
svn path=/trunk/; revision=4879
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/C/gdm.xml | 17 | ||||
| -rw-r--r-- | docs/es/gdm.xml | 103 | ||||
| -rw-r--r-- | docs/uk/gdm.xml | 109 |
3 files changed, 148 insertions, 81 deletions
diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml index 5d89d3a1..2d67f592 100644 --- a/docs/C/gdm.xml +++ b/docs/C/gdm.xml @@ -6516,6 +6516,23 @@ homogeneous="bool"> </listitem> </varlistentry> </variablelist> + + <para> + Item nodes can have a "background" property, set to "true" + or "false" (not setting this property is equivalent to "false"), as follow : + +<screen> +<item type="rect" background="true"> + <normal file="background.svg"/> + <pos x="0" y="0" width="100%" height="-75"/> +</item> +</screen> + + When this property is set on item nodes, background is applied to root window when greeter + exits after login, reducing screen flickering during login process. If no item node have "background" + property set, background is not modified when greeter exits. + </para> + </sect3> <sect3 id="positionnodes"> diff --git a/docs/es/gdm.xml b/docs/es/gdm.xml index 4283aff3..646983df 100644 --- a/docs/es/gdm.xml +++ b/docs/es/gdm.xml @@ -931,11 +931,12 @@ Greeter=/usr/lib/gdmgreeter Specify which actions are supported by the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> commands. Valid values are - HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these should be - separated by semicolons. This allows certain options to be disabled - if desired. Refer to the related + HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these + should be separated by semicolons. This allows certain + options to be disabled if desired. Refer to the related <filename>SystemCommandsInMenu</filename> and - <filename>RBACSystemCommandKeys</filename> configuration options. + <filename>RBACSystemCommandKeys</filename> configuration + options. </para> </listitem> </varlistentry> @@ -1200,22 +1201,24 @@ Greeter=/usr/lib/gdmgreeter <synopsis>RBACSystemCommandKeys</synopsis> <para> Support RBAC (Role Based Access Control) for system commands - (Shutdown, Reboot, Suspend, etc.). This feature is only functional - if GDM is compiled with RBAC support. Specify the RBAC key used - to determine if the user has permission to use the action via the - QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION - <command>gdmflexiserver</command> commands. Valid actions are - HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only - display the command if the gdm user (<filename>User</filename> - configuration key) has RBAC permissions to use the action. RBAC - keys for multiple actions can be specified by separating them with - semicolons. The format for each is "Action:RBAC key". If an - action is not specified, it is assumed that all users have - permission to use this action. For example, a valid value for - this configuration option would be - "HALT:key.for.halt;REBOOT:key.for.reboot". Refer to the - related <filename>AllowLogoutActions</filename> and - <filename>SystemCommandsInMenu</filename> configuration options. + (Shutdown, Reboot, Suspend, etc.). This feature is only + functional if GDM is compiled with RBAC support. Specify the + RBAC key used to determine if the user has permission to use + the action via the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and + SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> + commands. Valid actions are HALT, REBOOT, SUSPEND, and + CUSTOM_CMD. The greeter will only display the command if the + gdm user (<filename>User</filename> configuration key) has + RBAC permissions to use the action. RBAC keys for multiple + actions can be specified by separating them with semicolons. + The format for each is "Action:RBAC key". If an action is not + specified, it is assumed that all users have permission to use + this action. For example, a valid value for this + configuration option would be + "HALT:key.for.halt;REBOOT:key.for.reboot". Refer to + the related <filename>AllowLogoutActions</filename> and + <filename>SystemCommandsInMenu</filename> configuration + options. </para> </listitem> </varlistentry> @@ -1289,17 +1292,20 @@ Greeter=/usr/lib/gdmgreeter <synopsis>SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD</synopsis> <para> Specify which system commands are available in the greeter - menu. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD - and these should be separated by semicolons. This can be useful if you - want to disable some options in the menu, but still have them available - to authenticated users via the SET_LOGOUT_ACTION or - SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> commands. For - example, the GNOME panel uses these commands to provide Shutdown, - Reboot, and Suspend in the application menu. Therefore if you turn off - these options in the greeter, these options can still be available to - users who have authenticated via the GNOME panel. Refer to the related + menu. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and + CUSTOM_CMD and these should be separated by semicolons. This + can be useful if you want to disable some options in the menu, + but still have them available to authenticated users via the + SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION + <command>gdmflexiserver</command> commands. For example, the + GNOME panel uses these commands to provide Shutdown, Reboot, + and Suspend in the application menu. Therefore if you turn + off these options in the greeter, these options can still be + available to users who have authenticated via the GNOME panel. + Refer to the related <filename>AllowLogoutActions</filename> and - <filename>RBACSystemCommandKeys</filename> configuration options. + <filename>RBACSystemCommandKeys</filename> configuration + options. </para> </listitem> </varlistentry> @@ -2755,7 +2761,8 @@ Arguments: <pattern> (optional) Answers: OK <server>;<server>;... - <server> is <display>,<logged in user>,<vt or xnest display> + <server> is <display>,<logged in user>,<vt or xnest + display> <logged in user> can be empty in case no one logged in yet, and <vt> can be -1 if it's not known or not @@ -2864,8 +2871,8 @@ Note: The cookie should be the MIT-MAGIC-COOKIE-1, use you should generate one first. The cookie should be in hex form. Supported since: 2.17.7 -Arguments: <username> <display to run on> <uid of requesting user> - <xauth cookie for the display> <xauth file> +Arguments: <username> <display to run on> <uid of requesting + user> <xauth cookie for the display> <xauth file> Answers: OK <display> ERROR <err number> <english error description> @@ -2934,12 +2941,13 @@ Respuestas: GET_CONFIG: Get configuration value for key. Useful so that other applications can request configuration information from GDM. Any key defined as GDM_KEY_* - in gdm-daemon-config-keys.h is supported. Starting with version 2.13.0.2 - translated keys (such as "greeter/GdmWelcome[cs]" are - supported via GET_CONFIG. Also starting with version - 2.13.0.2 it is no longer necessary to include the - default value (i.e. you can use key "greeter/IncludeAll" - instead of having to use "greeter/IncludeAll=false". + in gdm-daemon-config-keys.h is supported. Starting with version + 2.13.0.2, translated keys (such as + "greeter/GdmWelcome[cs]" are supported via GET_CONFIG. + Also starting with version 2.13.0.2 it is no longer necessary to + include the default value (i.e. you can use key + "greeter/IncludeAll" instead of having to use + "greeter/IncludeAll=false". Supported since: 2.6.0.9 Arguments: <key> Answers: @@ -4283,6 +4291,23 @@ homogeneous="bool"> </listitem> </varlistentry> </variablelist> + + <para> + Item nodes can have a "background" property, set to "true" + or "false" (not setting this property is equivalent to "false"), as follow : + +<screen> +<item type="rect" background="true"> + <normal file="background.svg"/> + <pos x="0" y="0" width="100%" height="-75"/> +</item> +</screen> + + When this property is set on item nodes, background is applied to root window when greeter + exits after login, reducing screen flickering during login process. If no item node have "background" + property set, background is not modified when greeter exits. + </para> + </sect3> <sect3 id="positionnodes"> diff --git a/docs/uk/gdm.xml b/docs/uk/gdm.xml index 7dc75ad5..b8961124 100644 --- a/docs/uk/gdm.xml +++ b/docs/uk/gdm.xml @@ -1398,11 +1398,12 @@ Greeter=/usr/lib/gdmgreeter Specify which actions are supported by the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> commands. Valid values are - HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these should be - separated by semicolons. This allows certain options to be disabled - if desired. Refer to the related + HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD and these + should be separated by semicolons. This allows certain + options to be disabled if desired. Refer to the related <filename>SystemCommandsInMenu</filename> and - <filename>RBACSystemCommandKeys</filename> configuration options. + <filename>RBACSystemCommandKeys</filename> configuration + options. </para> </listitem> </varlistentry> @@ -1656,9 +1657,9 @@ Greeter=/usr/lib/gdmgreeter once only, the first time a greeter is displayed. The gdmprefetch command may be used. This utility will load any libraries passed in on the command line, or if the argument - starts with a "@" character, it will process the file assuming - it is an ASCII file containing a list of libraries, one per - line, and load each library in the file. + starts with a "@" character, it will process the file + assuming it is an ASCII file containing a list of libraries, + one per line, and load each library in the file. </para> </listitem> </varlistentry> @@ -1693,22 +1694,24 @@ Greeter=/usr/lib/gdmgreeter <synopsis>RBACSystemCommandKeys</synopsis> <para> Support RBAC (Role Based Access Control) for system commands - (Shutdown, Reboot, Suspend, etc.). This feature is only functional - if GDM is compiled with RBAC support. Specify the RBAC key used - to determine if the user has permission to use the action via the - QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and SET_SAFE_LOGOUT_ACTION - <command>gdmflexiserver</command> commands. Valid actions are - HALT, REBOOT, SUSPEND, and CUSTOM_CMD. The greeter will only - display the command if the gdm user (<filename>User</filename> - configuration key) has RBAC permissions to use the action. RBAC - keys for multiple actions can be specified by separating them with - semicolons. The format for each is "Action:RBAC key". If an - action is not specified, it is assumed that all users have - permission to use this action. For example, a valid value for - this configuration option would be - "HALT:key.for.halt;REBOOT:key.for.reboot". Refer to the - related <filename>AllowLogoutActions</filename> and - <filename>SystemCommandsInMenu</filename> configuration options. + (Shutdown, Reboot, Suspend, etc.). This feature is only + functional if GDM is compiled with RBAC support. Specify the + RBAC key used to determine if the user has permission to use + the action via the QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION, and + SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> + commands. Valid actions are HALT, REBOOT, SUSPEND, and + CUSTOM_CMD. The greeter will only display the command if the + gdm user (<filename>User</filename> configuration key) has + RBAC permissions to use the action. RBAC keys for multiple + actions can be specified by separating them with semicolons. + The format for each is "Action:RBAC key". If an action is not + specified, it is assumed that all users have permission to use + this action. For example, a valid value for this + configuration option would be + "HALT:key.for.halt;REBOOT:key.for.reboot". Refer to + the related <filename>AllowLogoutActions</filename> and + <filename>SystemCommandsInMenu</filename> configuration + options. </para> </listitem> </varlistentry> @@ -1791,17 +1794,20 @@ Greeter=/usr/lib/gdmgreeter <synopsis>SuspendCommand=HALT;REBOOT;SHUTDOWN;SUSPEND;CUSTOM_CMD</synopsis> <para> Specify which system commands are available in the greeter - menu. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and CUSTOM_CMD - and these should be separated by semicolons. This can be useful if you - want to disable some options in the menu, but still have them available - to authenticated users via the SET_LOGOUT_ACTION or - SET_SAFE_LOGOUT_ACTION <command>gdmflexiserver</command> commands. For - example, the GNOME panel uses these commands to provide Shutdown, - Reboot, and Suspend in the application menu. Therefore if you turn off - these options in the greeter, these options can still be available to - users who have authenticated via the GNOME panel. Refer to the related + menu. Valid values are HALT, REBOOT, SHUTDOWN, SUSPEND, and + CUSTOM_CMD and these should be separated by semicolons. This + can be useful if you want to disable some options in the menu, + but still have them available to authenticated users via the + SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION + <command>gdmflexiserver</command> commands. For example, the + GNOME panel uses these commands to provide Shutdown, Reboot, + and Suspend in the application menu. Therefore if you turn + off these options in the greeter, these options can still be + available to users who have authenticated via the GNOME panel. + Refer to the related <filename>AllowLogoutActions</filename> and - <filename>RBACSystemCommandKeys</filename> configuration options. + <filename>RBACSystemCommandKeys</filename> configuration + options. </para> </listitem> </varlistentry> @@ -3382,7 +3388,8 @@ Arguments: <pattern> (optional) Answers: OK <server>;<server>;... - <server> is <display>,<logged in user>,<vt or xnest display> + <server> is <display>,<logged in user>,<vt or xnest + display> <logged in user> can be empty in case no one logged in yet, and <vt> can be -1 if it's not known or not @@ -3491,8 +3498,8 @@ Note: The cookie should be the MIT-MAGIC-COOKIE-1, use you should generate one first. The cookie should be in hex form. Supported since: 2.17.7 -Arguments: <username> <display to run on> <uid of requesting user> - <xauth cookie for the display> <xauth file> +Arguments: <username> <display to run on> <uid of requesting + user> <xauth cookie for the display> <xauth file> Answers: OK <display> ERROR <err number> <english error description> @@ -3562,12 +3569,13 @@ Answers: GET_CONFIG: Get configuration value for key. Useful so that other applications can request configuration information from GDM. Any key defined as GDM_KEY_* - in gdm-daemon-config-keys.h is supported. Starting with version 2.13.0.2 - translated keys (such as "greeter/GdmWelcome[cs]" are - supported via GET_CONFIG. Also starting with version - 2.13.0.2 it is no longer necessary to include the - default value (i.e. you can use key "greeter/IncludeAll" - instead of having to use "greeter/IncludeAll=false". + in gdm-daemon-config-keys.h is supported. Starting with version + 2.13.0.2, translated keys (such as + "greeter/GdmWelcome[cs]" are supported via GET_CONFIG. + Also starting with version 2.13.0.2 it is no longer necessary to + include the default value (i.e. you can use key + "greeter/IncludeAll" instead of having to use + "greeter/IncludeAll=false". Supported since: 2.6.0.9 Arguments: <key> Answers: @@ -4986,6 +4994,23 @@ homogeneous="bool"> </listitem> </varlistentry> </variablelist> + + <para> + Item nodes can have a "background" property, set to "true" + or "false" (not setting this property is equivalent to "false"), as follow : + +<screen> +<item type="rect" background="true"> + <normal file="background.svg"/> + <pos x="0" y="0" width="100%" height="-75"/> +</item> +</screen> + + When this property is set on item nodes, background is applied to root window when greeter + exits after login, reducing screen flickering during login process. If no item node have "background" + property set, background is not modified when greeter exits. + </para> + </sect3> <sect3 id="positionnodes"> |