From a99b31e5ce865093edeff837f5c6b7a862e020d1 Mon Sep 17 00:00:00 2001
From: Sam Wilson <57262657+SamWilsn@users.noreply.github.com>
Date: Thu, 2 Nov 2023 12:21:54 -0400
Subject: [PATCH] config/graphical-session/wayland: explain running SDDM on
 wayland

---
 src/config/graphical-session/wayland.md | 34 +++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/src/config/graphical-session/wayland.md b/src/config/graphical-session/wayland.md
index 34b101935..7c5d15644 100644
--- a/src/config/graphical-session/wayland.md
+++ b/src/config/graphical-session/wayland.md
@@ -45,6 +45,40 @@ accessing input devices. In Void systems, this requires a seat manager service,
 which can be either elogind or seatd. Enabling them is explained in the
 ["Session and Seat Management"](../session-management.md) session.
 
+### Display Managers
+
+#### SDDM
+
+To run SDDM itself under wayland, create the file
+`/etc/sddm.conf.d/10-wayland.conf` (see
+[sddm.conf(5)](https://man.voidlinux.org/sddm.conf.5)), with the contents:
+
+```
+[General]
+DisplayServer=wayland
+```
+
+The above configuration requires installing the `weston` compositor.
+
+Alternatively, if SDDM is being used as part of a KDE installation, it may be
+preferable to use the `kwin` compositor:
+
+```
+[General]
+DisplayServer=wayland
+GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
+
+[Wayland]
+CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
+```
+
+In either case, to avoid a conflict, disable `agetty` on the first virtual
+terminal:
+
+```
+touch /etv/sv/agetty-tty1/down
+```
+
 ### Native applications
 
 [Qt5](https://wayland.freedesktop.org/qt5.html)-based applications require