| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
"set up" is two words when used as a verb, so the function
name "setup_session_environment" is missing an underscore.
This commit adds that underscore.
|
|
|
|
|
|
|
|
|
|
| |
Right now we set LANG based on the value of setlocale(),
and disregard all other language environment variables.
This commit just passes the environment variables through
wholesale.
http://bugzilla.gnome.org/show_bug.cgi?id=709105
|
|
|
|
|
|
|
| |
These days the greeter doesn't let you pick a language at log in time.
This commit drops the interface, since it's unused, and we don't have
any API guarantees in libgdm.
|
|
|
|
|
|
|
| |
libgdm isn't a UI, so it's weird to be in a directory
called GUI.
This commit moves it up a layer.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm open to negotiation for this, but basically...gdm is at
present second only to the kernel in the sheer amount of spew
it emits - when the version is "unstable". But it always will
be for Continuous.
Nowadays of course, I think Continuous helps act as a testing system
for GDM that obviates a lot of the need for lots of debugging info for
gdm during "unstable" cycles.
I suspect that we will over time add other informational messages at
strategic points by default; this patch is not the end of the story.
It's a new beginning.
https://bugzilla.gnome.org/show_bug.cgi?id=715037
|
| |
|
|
|
|
| |
Update the project URL and maintainers list.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reauthentication sessions need subtly different behavior than initial
login sessions with regard to pam. For instance, we want to refresh
existing kerberos credentials instead of establishing new kerberos
credentials.
GDM has all the code in place to do this properly, but lacks the actual
call to mark reauthentication sessions as such.
This commit adds the missing call.
https://bugzilla.gnome.org/show_bug.cgi?id=691269
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This was failing in Continuous after
See https://bugzilla.gnome.org/show_bug.cgi?id=711818
and rather than debug it I'm just going to change it to do
what gnome-autogen.sh does, which works.
|
|
|
|
| |
I don't know, it seems like not having one can be fatal on some systems.
|
|
|
|
|
|
|
|
|
| |
This patch add an option (xdmcp/ShowLocalGreeter) to disable the local X
console and turn GDM into a simple XDMCP server
Thanks to Patrick Monnerat and Josselin Mouette for the patch
https://bugzilla.gnome.org/show_bug.cgi?id=567522
|
|
|
|
|
|
|
|
|
| |
When using IT_PROG_INTLTOOL using the gettect automake macros isn't
necessary. To make matters worse, when mixing the marcos both try to
generate po/Makefile.in.in. Recent versions of intltool detect when
gettext won and bails when building.
https://bugzilla.gnome.org/show_bug.cgi?id=711818
|
|
|
|
|
|
|
| |
Add --with-gnome-settings-daemon-directory option to allow one to pass
location for the gnome-settings-daemon executable used by the chooser
https://bugzilla.gnome.org/show_bug.cgi?id=645918
|
|
|
|
|
|
|
|
|
| |
This function is available in GIO since 2.36
Thanks to Petr Salinger <Petr.Salinger@seznam.cz> for the patch
Debian Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692739
https://bugzilla.gnome.org/show_bug.cgi?id=687921
|
|
|
|
|
|
|
|
|
|
|
|
| |
We currently figure out which session to unlock on-the-fly based on
the username that was just reauthenticated. This doesn't work, for
XDMCP sessions, under logind, since they don't have a seat. There's
no reason to try to deduce the session, though. We already know it,
so we might as well pass it down.
This fixes unlocking for XDMCP.
https://bugzilla.gnome.org/show_bug.cgi?id=690926
|
|
|
|
|
|
|
|
|
|
| |
With systemd, XDMCP sessions don't have associated seats.
Currently, reauth channels find the session by first looking up
the seat, which means unlocking fails for XDMCP.
This commit changes the code to determine session strictly from pid.
https://bugzilla.gnome.org/show_bug.cgi?id=690926
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gnome-shell only falls back to opening a new session if the reauth
channel fails to open because of denied access. For XDMCP we currently
fail for other reasons.
This commit returns ACCESS DENIED for those cases as well, so the
intended fallback happens.
Based on a patch by Jeremy White <jwhite@codeweavers.com>
https://bugzilla.gnome.org/show_bug.cgi?id=690926
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now we stop the slave if a greeter running on a remote
X server exits. This is wrong, since the greeter will exit as
part of the login screen process. We already have mechanisms in
place to reap the slave at the appropriate time, so stopping the
slave on disconnection is totally unneeded and actively harmful.
This commit drops that code.
https://bugzilla.gnome.org/show_bug.cgi?id=690926
|
|
|
|
|
|
|
|
|
|
|
| |
GDM will run initial-setup if there are no configured user accounts
on the system. We correctly skip checking if there are configured user
accounts on remote XDMCP displays, but incorrectly, still run initial-setup.
This commit makes sure we only every do any of the initial-setup logic
in the local display code paths.
https://bugzilla.gnome.org/show_bug.cgi?id=711180
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This prevents it from breakings setups building using --without-systemd
|
| |
|
|
|
|
|
| |
While running with debug enabled, do not print that we are updating
btmp if we do not HAVE_UPDWTMPX or HAVE_UPDWTMP.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|