| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The comment incorrectly says to put WaylandEnable=true to
disable wayland.
This commit flips it to say WaylandEnable=false
https://bugzilla.gnome.org/show_bug.cgi?id=746523
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Right now wayland sessions register with GDM before they're
actually ready, so we quit plymouth too soon.
Until we can fix that, this commit adds a sleep 5 hack to
quit plymouth a little after registration.
https://bugzilla.gnome.org/show_bug.cgi?id=746498
|
|
|
|
|
|
|
| |
plymouth can quit in the background, the only thing we need to block
synchronously on is it deactivating.
https://bugzilla.gnome.org/show_bug.cgi?id=746498
|
|
|
|
|
|
|
|
|
|
| |
We currently only allow ConsoleKit seats if GDM is built without systemd
support, but it's possible to build GDM with systemd support and not
be running logind.
This commit fixes it to do a run time check.
https://bugzilla.gnome.org/show_bug.cgi?id=746497
|
|
|
|
|
|
|
| |
The ConsoleKit path needs to use GdmLegacyDisplay, which always
reuses the greeter display.
https://bugzilla.gnome.org/show_bug.cgi?id=746497
|
|
|
|
|
|
|
|
|
|
|
| |
After the greeter is started, we may start any pending initial-setup
login from the user. Right now we do that directly from
on_display_status_changed.
This commit moves the code off to a subroutine, since it's only going
to get more complicated in the future.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
|
|
|
|
| |
The only reason we need the display for autologin is to know if it's
running on seat0 or not. Going forward we won't necessarily have a
display up front, so drop the parameter, and just check the seat
in the caller.
For symmetry, drop the display paramater timed login, too, and do
the display related checks in the lone caller.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
|
|
|
|
| |
The function is only ever called in two distinct ways:
1) to check about timed login
2) to check about automatic login.
Since it's used in completely distinct ways and has somewhat distinct
implementations for each, split it up into two functions for clarity.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
|
| |
The function is no longer virtualized among the display types,
and it doesn't actually have a full picture of whether or not the
display should do automatic/timed login so move it up to the manager,
where all the information is.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Automatic login handling doesn't have a whole lot to do with the
greeter session, so having it in setup_greeter_session is a little
weird.
This commit splits set_up_greeter_session into two functions,
set_up_greeter_session and set_up_automatic_login_session, and then
changes the caller to call the right one depending on if the display
should do automatic login..
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
| |
It only needs to be called in one place, and that one place
already does most of the logic of that function, so we can
simplify the code a little by consolidating the two functions.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
|
| |
The file is not anymore useful than a boolean on the manager
state object now, that everything is merged into one process.
This commit gets rid of it, since a boolean is simpler.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
| |
This will let us move automatic login handling later,
which we need to fix which VT it starts on.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
| |
Neither wayland nor X11 is ready to be fully logind managed,
yet, including the login screen. This commit makes sure
we never use it.
https://bugzilla.gnome.org/show_bug.cgi?id=746492
|
|
|
|
|
|
|
|
|
|
|
| |
There are two things that are pretty useful for a user to
do when troubleshooting problems:
1) turn on debugging
2) turn of wayland support since it's so new
This commit adds comments to custom.conf to give tips on how
to do those things.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
An overzealous SELinux policy can lead to required tty ioctls
failing. Various bits of GDM, the X server and wayland expect these
ioctls to succeed, so bail early if they fail.
https://bugzilla.gnome.org/show_bug.cgi?id=745675
|
|
|
|
|
|
|
|
|
| |
<krnowak> halfline: "if (g_strcmp0 (session_type, session_type) != 0) {" ?
<halfline> ahhhhh
<halfline> thank you
<krnowak> No problem.
https://bugzilla.gnome.org/show_bug.cgi?id=746348
|
|
|
|
|
|
|
|
|
|
| |
If we read the saved selection from user data, we don't select
the right session type.
This commit makes sure any time the selection is changed, we check
if the session is wayland or X11.
https://bugzilla.gnome.org/show_bug.cgi?id=746348
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
|
|
|
|
| |
This reverts commit 4133b7f790a9ca63be4c56d6620d9dba368393bd.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gdm.service Conflicts with plymouth-quit.service, so it does not run
when it normally would (because GDM wants to handle the handover from
plymouth to X11 itself). This means that if gdm fails to start for whatever
reason, plymouth is never stopped, so plymouth-quit-wait.service
never finishes. This, in turn, means that getty@tty*.service, which is
After plymouth-wait-quit.service, never starts, and there is no way to
log in locally and fix the problem (Debian bug #780257, but not
Debian-specific).
In Debian 8, not all display managers have been migrated to
participate in managing the display-manager.service symlink yet
(in particular, kdm and wdm have not), so gdm has a transitional
ExecStartPre that stops it from running if kdm or wdm is selected
as the active DM. This has the same effect of preventing plymouth
from running (Debian-specific bug #766462).
It's easy to avoid both of those situations by scheduling
plymouth-quit.service to run if gdm fails.
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=746023
Bug-Debian: https://bugs.debian.org/766462
Bug-Debian: https://bugs.debian.org/780257
|
| |
|
|
|
|
|
|
|
| |
Right now we try to timed login into the same VT
the login screen is running on. This leads to lock ups.
https://bugzilla.gnome.org/show_bug.cgi?id=745974
|
|
|
|
|
| |
This way we aren't printing gibberish from the already
freed username.
|
|
|
|
|
|
| |
We don't want ref count leaks to lead to unkilled sessions.
https://bugzilla.gnome.org/show_bug.cgi?id=745975
|
|
|
|
|
|
|
|
|
|
| |
I guess in the past the session has implicitly gone away
when the display goes away, but now that the display is started
implicitly by the session that isn't really true anymore.
We need to explicitly kill the session when gdm is shutting down.
https://bugzilla.gnome.org/show_bug.cgi?id=745975
|
|
|
|
|
|
| |
Seems more appropriate.
https://bugzilla.gnome.org/show_bug.cgi?id=745975
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit fbb922cfcf4e389b0aa416d9a81c45f8f938f104 made sure
to source /etc/default/locale on debian so that GDM gets
started with the correct locale.
Unfortunately, now if that file doesn't exist (which is entirely
legitimate) then GDM won't start.
This commit makes sure to still start GDM, even if the file couldn't
be sourced.
https://bugzilla.gnome.org/show_bug.cgi?id=745868
|
|
|
|
|
|
|
| |
plymouth-quit-wait waits for plymouth to quit, we quit plymouth,
so putting After=plymouth-quit-wait means we'll wait forever.
https://bugs.freedesktop.org/show_bug.cgi?id=89475
|