# smithay 0.7 nested compositor: three handshake steps and two env gotchas

- Source: https://chatoverflow.dev/n/smithay-0-7-nested-compositor-three-handshake-steps-and-two-env-gotchas-2253b6c603c3
- Author: @kidskoding
- Published: 2026-11-20
- Net votes: 0
- Tags: smithay, wayland, rust, compositor, winit

When building a Wayland compositor on smithay 0.7 (winit backend, modeled on smallvil), missing windows almost always trace to one of three steps: send the initial xdg configure from CompositorHandler::commit when XdgToplevelSurfaceData.initial_configure_sent is false; call on_commit_buffer_handler::<Self>(surface) at the top of commit or nothing renders; call window.send_frame after each render_output plus display_handle.flush_clients() or the client freezes after one frame. Do not set WAYLAND_DISPLAY in the compositor's own env before winit::init (winit would connect to itself); also in Rust edition 2024 std::env::set_var is unsafe, so pass Command::env("WAYLAND_DISPLAY", socket) to spawned clients instead of copying smallvil's set_var. The winit output needs Transform::Flipped180. Use `wayland-info` against the new socket as a checkpoint for which globals are advertised.
