Commit 8632e2a5 authored by Brian Cameron's avatar Brian Cameron Committed by Brian Cameron

Fix calls to zenity so they work. Fixes bug #330892. Last minute updates

2006-02-13  Brian Cameron  <brian.cameron@sun.com>

        * config/Xsession.in: Fix calls to zenity so they work.  Fixes
          bug #330892.
        * README, README.install, docs/C/gdm.xml: Last minute updates
          before string freeze.
parent 90113edc
2006-02-13 Brian Cameron <brian.cameron@sun.com>
* config/Xsession.in: Fix calls to zenity so they work. Fixes
bug #330892.
* README, README.install, docs/C/gdm.xml: Last minute updates
before string freeze.
2006-02-10 Brian Cameron <brian.cameron@sun.com>
* gui/greeter/greeter.c, gui/greeter/greeter_action_language.[ch],
......
......@@ -6,39 +6,41 @@
-----------------------------------------------------------
| For documentation see the website:
| http://www.gnome.org/projects/gdm/
| Or use the gnome help browser under GNOME|System.
| Or use the GNOME help browser under GNOME|System.
| The XML documentation is in docs/ and is in DocBook/XML
| format so you can use docbook2html or docbook2pdf to
| convert it.
-----------------------------------------------------------
The Gnome Display Manager is a re-implementation of the well known xdm
program. GDM implements all significant features required for managing
local and remote displays.
The Gnome Display Manager (GDM) is a display manager that
implements all significant features required for managing
local and remote displays. For full information about
GDM features, refer to the documentation.
gdm daemon:
GDM daemon:
o X Authentication
o XDMCP (Remote login) including TCP Wrappers for access
control
o machine-specific and system-wide configuration support.
o XDMCP (Remote Login) including TCP Wrappers for access
control and improved security.
o Machine-specific and system-wide configuration support.
o Default and per-display initialization scripts.
o PreSession, PostSession, Init, and PostLogin scripts.
o Pluggable Authentication Modules (PAM)
o IPv6 support (optional, use --enable-ipv6=yes to get this)
o IPv6 support (optional, use --enable-ipv6=yes to enable)
o Autologin for single user workstations (off by default)
o Timed login for kiosks and public terminals (off by
default)
o On demand local servers (gdmflexiserver)
o On-demand local servers (gdmflexiserver)
o SunRay (SRSS) support via gdmdynamic.
o Can manage X servers without a login window
(Such as for XDMCP terminal client machines)
o Can manage X servers without a login window (Such as
for XDMCP terminal client machines)
o Many other features ...
gdmlogin and gdmgreeter:
o Can launch the XDMCP chooser program (remote login)
o Can launch the XDMCP chooser program (Remote Login)
o Can launch the Setup program (off by default)
o Can Halt, reboot, or suspend the machine (off by
o Can halt, reboot, or suspend the machine (off by
default)
o Session selection support
o Language selection support
......@@ -53,9 +55,9 @@ gdmlogin:
gdmgreeter:
o Fully themable
o Themable with many themes at http://art.gnome.org/
o Xinerama support
o Face browser (if in the theme)
o Face browser (if supported by the theme)
gdmchooser:
......@@ -75,14 +77,20 @@ Availability:
Reporting Bugs:
When reporting bugs you should first turn on debugging in
gdm.conf. This causes debug messages to be sent to the system
log (/var/log/messages or /var/adm/messages) and include the
output sent to syslog.
Please submit bug reports, enhancement requests, and patches to
the "gdm" category at:
http://bugzilla.gnome.org/
When reporting bugs you should first turn on debugging on the
"Security" tab of gdmsetup or editing gdm.conf-custom as
described in the documentation. This causes debug messages to
be sent to the system log (/var/log/messages or /var/adm/messages)
and include the GDM output sent to syslog.
You should not have to configure syslog for this to work, but if
you don't see GDM messages in your syslog you may need to
configure it.
you do not see GDM messages in your syslog it may require
configuration.
You should not leave "debug" on after collecting data. It will
clutter your syslog and slow system performance.
......@@ -90,7 +98,7 @@ Reporting Bugs:
Installation:
Please consult README.install for instructions on how to
configure and install gdm.
configure and install GDM.
Contact:
......@@ -103,18 +111,17 @@ Martin, George, and then Brian
-------------------------------------------------------------------------
Note:
Originally I started maintaining gdm2 because martin didn't yet finish gdm3 and
was in general busy and we needed a working gdm for 1.4. The move to gdm3 is
Originally I started maintaining gdm2 because Martin didn't yet finish gdm3 and
was in general busy and we needed a working GDM for 1.4. The move to gdm3 is
very unlikely to happen now that gdm3 has been pretty dead for quite
a while. Do not send gdm2 patches to martin (well you can but he'll likely
ignore them:), send them to me instead and I'll integrate them for you.
a while.
-George <jirka@5z.com>
-------------------------------------------------------------------------
Note:
Starting January, 2005 I have been acting as maintainer. Send patches to
me and I will work with you to get them integrated.
Starting January, 2005 I have been acting as maintainer.
-Brian Cameron <Brian.Cameron@Sun.Com>
-------------------------------------------------------------------------
QUICK NOTES ON INSTALLATION/USE:
I try to keep this document updated with issues that are brought
up on gdm-list@gnome.org. GDM can be sometimes challanging to setup
and get working. GDM does things like start up your Xserver, so it
is sometimes necessary to tweak the GDM configuration to work with
any given setup.
This document tries to capture the most common problems. Also
refer to the "Troubleshooting" section of the GDM dcumentation:
http://www.gnome.org/projects/gdm/docs.html
You can also look in docs/C/gdm.xml for the raw XML version of the
docs.
General
=======
Make sure you are familiar with the "Overview" and "Security"
sections of the GDM documentation:
GDM sometimes requires some configuration work for a given setup.
Make sure you are familiar with the "Overview", "Security",
"Configuration", and "Troubleshooting" sections of the GDM
documentation:
http://www.gnome.org/projects/gdm/docs.html
You can also look in the docs subdirectory for the XML version of
the documentation.
WARNING: "gdm-binary" is a *daemon* -- not a common user application.
It requires extensive knowledge about your system setup to install and
configure. gdm does not intend to be Plug and Play.
configure. GDM does not intend to be Plug and Play.
(i.e. ./configure ; make install).
Building GDM
......@@ -33,10 +25,10 @@ Building GDM
You may need to update your build tools if the autogen.sh command
complains that it requires a newer version of the build tool.
If you did not compile GNOME yourself, make sure you have the appropriate
-devel packages installed.
If you did not compile GNOME yourself, make sure you have the
appropriate -devel packages installed.
Here's a good configure for GDM:
Here is a recommended configure for GDM:
./autogen.sh --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin
--with-prefetch --with-post-path=/usr/openwin/bin
......@@ -48,8 +40,9 @@ DefaultPath and RootDefaultPath, then use the --with-post-path
configure option. Argument value should be a list of directories
separated by ":" characters (no spaces).
Make sure the --with-pam-prefix points to the prefix where the pam.conf
file is located (default is sysconfdir or /etc).
Make sure the --with-pam-prefix points to the prefix where the
pam.conf file is located if it is not in the default directory
(sysconfdir or /etc).
If you want accessibility to work and have AT programs like gok and
gnopernicus installed to a different directory than EXPANDED_BINDIR,
......@@ -81,8 +74,8 @@ clutter your syslog and slow system performance.
Configuration
=============
Make sure you are familiar with the "Configuring GDM" section of
the GDM documentation:
Gain, refer to the "Configuring GDM" section of the GDM
documentation for full information:
http://www.gnome.org/projects/gdm/docs.html
......@@ -91,11 +84,11 @@ GDM Default Configuration File
The GDM configuration file /etc/gdm/gdm.conf may be replaced by
you distribution on upgrade, so if a user wants to ensure that
configuration changes persist on upgrade, edit the /etc/gdm/gdm.conf-custom
file. You can specify a different location for the file via
the "--with-configdir=/dir" option. This can be useful if you
want to put the default file on a filesystem shared by multiple
machines.
configuration changes persist on upgrade, edit the
/etc/gdm/gdm.conf-custom file. You can specify a different
location for the file via the "--with-configdir=/dir" option.
This can be useful if you want to put the default file on a
filesystem shared by multiple machines.
If you wish to change configuration by hand, edit the
/etc/X11/gdm/gdm.conf-custom file and make sure the keyname=value
......@@ -109,8 +102,8 @@ anywhere in the section.
[daemon]
Greeter=/usr/lib/gdmgreeter
The default options refer to interfaces that may need to be
customized for your distribution providor.
The following interfaces most frequently need to be customized
for a given setup, since they are OS/machine specific:
HaltCommand
RebootCommand
......@@ -149,14 +142,11 @@ not let your computer load these libraries while the user types
in their name and password?
The provided gdmprefetchlist.in was created for Solaris 11 running
GNOME 2.13 (not a particularly stable configuration but one that will
likely be what Sun ships in Solaris 11). If using another OS, then
you will probably want to modify the config/gdmprefetchlist.in file
before running configure. This makes sure the list of libraries to
preload is suitable for your setup. The GDM PreFetch will ignore
libraries it doesn't find on your system but the point with this code
is to speed up your system so you can do further tuning for your
environment.
GNOME 2.13 (not a particularly stable configuration). If using
another OS or desktop (such as KDE), then you will probably want
to modify the config/gdmprefetchlist.in file before running
configure. The GDM PreFetch will ignore libraries listed that it
does not find on your system.
Red Hat
=======
......@@ -192,3 +182,4 @@ documentation for information about specific configuration issues for
Solaris.
http://www.gnome.org/projects/gdm/docs.html
......@@ -79,7 +79,8 @@ zenity=`gdmwhich zenity`
if [ x"$command" = xfailsafe ] ; then
if [ -n "$zenity" ] ; then
"$zenity" --info --text `gettextfunc "This is the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"`
disptext=`gettextfunc "This is the failsafe xterm session. Windows now have focus only if you have your cursor above them. To get out of this mode type 'exit' in the window in the upper left corner"`
"$zenity" --info --text "$disptext"
else
echo "$0: Starting the failsafe xterm session."
fi
......@@ -239,7 +240,8 @@ eval exec $command
echo "$0: Executing $command failed, will run xterm"
if [ -n "$zenity" ] ; then
"$zenity" --info --text `gettextfunc "Failed to start the session, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window in the upper left corner"`
disptext=`gettextfunc "Failed to start the session, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window in the upper left corner"`
"$zenity" --info --text "$disptext"
fi
exec xterm -geometry 80x24+0+0
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment