summaryrefslogtreecommitdiff
path: root/daemon/gdm-legacy-display.c
Commit message (Collapse)AuthorAgeFilesLines
* gdm-legacy-display: Use g_auto*Alessandro Bono2023-04-281-13/+6
|
* gdm-legacy-display: Plug a memory leakAlessandro Bono2023-04-281-7/+3
| | | | | display_name and seat_id were leaked. While at it, use g_autoptr() for launch_environment.
* legacy-display: use G_DECLARE_FINAL_TYPENiels De Graef2018-12-231-20/+15
|
* launch-environment: use wayland for initial-setupRay Strode2018-08-311-3/+4
| | | | | | | | | | | 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.
* Fix missing class castRobert Ancell2017-12-041-1/+1
|
* legacy-display: ensure X server is dead when respawningRay Strode2017-10-101-0/+21
| | | | | | | | | | | | If the user logs out we may detect the session dying before we detect the X server dying. If that happens, then we currently don't wait for the X server to exit before starting a new X server. This commit makes sure to explicitly kill the X server and wait for its death before proceeding. https://bugzilla.gnome.org/show_bug.cgi?id=788786
* legacy-display: ensure X11 display device is propagated to launch environmentRay Strode2015-04-101-0/+15
| | | | | | | | | | | | | Once the server associated with the login screen session is ready, we query its display device for ConsoleKit. This device needs to get propagated to the session to ensure ConsoleKit can track session activeness properly. This commit makes sure the display device is plumbed from the GdmServer object to the GdmLaunchEnvironment object where it gets used by the the login session (and subsequently the user session). https://bugzilla.gnome.org/show_bug.cgi?id=747351
* launch-environment: add session-type propertyRay Strode2015-02-181-0/+1
| | | | | | | | | | 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
* display: only create Xauth file for legacy code pathsRay Strode2015-02-181-0/+6
| | | | | | GdmLocalDisplay doesn't need it, so don't bother doing it then. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* session: start login screen using session wrappersRay Strode2015-02-181-0/+264
Since we have the wrappers, let's use them for the login screen, too, when we can. This commit removes GdmServer from GdmLocalDisplay, since starting the X server should be handled implicitly by gdm-x-session, now. All the old logic is now in a new GdmLegacyDisplay object, that will remain for cases where gdm-x-session doesn't work. (ConsoleKit systems, non-seat0 displays, etc) https://bugzilla.gnome.org/show_bug.cgi?id=744764
View Lorry Controller Status