diff options
author | Dominique Martinet <[email protected]> | 2018-07-04 13:50:23 +0900 |
---|---|---|
committer | Dominique Martinet <[email protected]> | 2018-07-04 13:52:26 +0900 |
commit | c092f1fe6a742bc79015efe6e485c35f49cbf473 (patch) | |
tree | 55272d0cb9f32a18b671b049336841024c10c0fa /sway/server.c | |
parent | 8cc26130a66f533a5cbb8e4833a536dd8798f833 (diff) |
startup: move setenv WAYLAND_DISPLAY before config execs
We would previously run all config commands without the environment,
which would appear to work as our socket name is the default one, but
wayland clients would start up in the wrong sway session.
(This explains why 'sometimes' my swayidle processes wouldn't die with
sway, as they weren't listening to the correct socket)
Diffstat (limited to 'sway/server.c')
-rw-r--r-- | sway/server.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/sway/server.c b/sway/server.c index 8106f3c8..cd15f454 100644 --- a/sway/server.c +++ b/sway/server.c @@ -143,7 +143,6 @@ void server_fini(struct sway_server *server) { void server_run(struct sway_server *server) { wlr_log(L_INFO, "Running compositor on wayland display '%s'", server->socket); - setenv("WAYLAND_DISPLAY", server->socket, true); if (!wlr_backend_start(server->backend)) { wlr_log(L_ERROR, "Failed to start backend"); wlr_backend_destroy(server->backend); |