6 Commits

Author	SHA1	Message	Date
Carlos Garnacho	38e58b837b	core: Use DISPLAY envvar to forward in the launch context ... The meta_x11_get_display_name() will return our private connection, which is not what we want to transfer to clients being launched. https://gitlab.gnome.org/GNOME/mutter/merge_requests/945	2020-02-29 20:41:26 +00:00
Carlos Garnacho	9109fa0eb8	x11: Add meta_x11_get_display_name() function ... Instead of poking the DISPLAY envvar at places. https://gitlab.gnome.org/GNOME/mutter/merge_requests/709	2019-08-06 00:41:36 +00:00
Carlos Garnacho	bf8bc65cc9	core: Check environment variables before giving to GAppLaunchContext ... Depending on the type of session, one or the other might be NULL, which is not meant to be handled by these functions. Check for both DISPLAY envvars before setting them on the GAppLaunchContext. Closes: https://gitlab.gnome.org/GNOME/mutter/issues/586	2019-05-06 17:27:56 +02:00
Daniel van Vugt	9d49e8abd0	launch-context: Swap reversed timestamp/workspace ... The parameters had been mixed up for X11 sessions. Closes: https://gitlab.gnome.org/GNOME/mutter/issues/505	2019-04-01 10:34:51 +00:00
Olivier Fourdan	562cf14258	core: Fix compiler warning ... Fix compiler warning: ‘startup_id’ may be used uninitialized in `meta_launch_context_get_startup_notify_id()`. Also change `gchar` to plain `char` while at it. https://gitlab.gnome.org/GNOME/mutter/merge_requests/406	2019-01-23 10:06:30 +01:00
Carlos Garnacho	f033d0e846	core: Add MetaLaunchContext ... This is a GAppLaunchContext subclass meant to replace usage of GdkAppLaunchContext in gnome-shell. Launch contexts get created from the MetaStartupNotification as they are closely related. The messaging underneath depends on the availability of a X11 display, if there is one we go through it (and libsn). If there is none, we still create startup sequences manually for wayland clients.	2019-01-18 17:03:57 +00:00