| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Nobody derives it since commit be67db1c11868ea2788cece74bbe53e76522292c.
|
| |
|
|
|
|
|
|
|
|
|
| |
While we've been using wayland by default for the login screen
for a long time, and for the user session for somewhat less time,
we never switched initial setup over.
It's still using X11 for no good reason.
This commit changes initial-setup to use wayland by default like
everything else.
|
| |
|
|
|
|
|
|
|
|
|
| |
We're connecting to a signal that isn't implemented. This
commit adds the implementation.
A slightly better fix might be to cut out some of the layers,
of middle men passing around hostname-selected, but for now this
is fine.
https://bugzilla.gnome.org/show_bug.cgi?id=780787
|
| |
|
|
|
|
|
|
|
|
| |
The session-type property is analagous to the
sd_login session type. It can be either "x11" or "wayland".
This helps us decide whether to start a wayland
session or an X session.
https://bugzilla.gnome.org/show_bug.cgi?id=744764
|
| |
|
|
|
|
|
|
|
|
|
| |
We're trying to get rid of the slave code, so we need to
move responibility for launching the greeter to the
display objects.
This commit changes the display classes to set up a
launch environment that the base class runs.
https://bugzilla.gnome.org/show_bug.cgi?id=744764
|
| |
|
|
| |
Fix bug 683383.
|
|
|
"GdmWelcomeSession" was always a sort of bad name, as it is not a
GdmSession, itself (it has-a GdmSession), and it's unnecessarily generic;
it doesn't really have anything to do with "Welcome" or "Session"
itself. It managed a non-user GdmSession, spawned the process in the
correct environment (spawning a DBus daemon if need be) and made sure to
keep track of it until it died. I think "GdmLaunchEnvironment" is an
appropriate name for this.
https://bugzilla.gnome.org/show_bug.cgi?id=678057
|
