mirror of
https://gitlab.freedesktop.org/wayland/wayland.git
synced 2026-05-03 06:46:33 -04:00
8f518f958a
Connecting by default to wayland-0 when environment variables WAYLAND_DISPLAY/WAYLAND_SOCKET are not set can cause unexpected connections when more than one session is being used. Specifically, if you run a program from a non-Wayland context (over ssh, on a VT, in an X11 session, from a job scheduler), while some unrelated compositor is listening on wayland-0, the program may connect to the compositor and leave the user wondering what has happened. This commit adjusts the documentation to clarify that the wayland-0 fallback is kept "for compatibility reasons", implying that in typical use programs do not rely on it. The changes to the wayland-server documentation (+ publican docs) briefly explain why compositors should avoid providing wayland-0. To avoid breaking existing software, the fallback to wayland-0 has not been removed (and perhaps never will be). As part of this change, the wl_display_add_socket_auto function has been documented to describe its action as well as the recommended alternative of connecting to the first available socket in the sequence wayland-1, wayland-2, etc. Signed-off-by: Manuel Stoeckl <code@mstoeckl.com> |
||
|---|---|---|
| .. | ||
| css | ||
| images | ||
| Architecture.xml | ||
| Author_Group.xml | ||
| Book_Info.xml | ||
| Client.xml | ||
| Compositors.xml | ||
| Foreword.xml | ||
| Introduction.xml | ||
| meson.build | ||
| Preface.xml | ||
| Protocol.xml | ||
| Revision_History.xml | ||
| Server.xml | ||
| Wayland.ent | ||
| Wayland.xml | ||
| Xwayland.xml | ||