From a225036f99647055bfdac814d77a2e71798ef785 Mon Sep 17 00:00:00 2001
From: khaneliman <khaneliman@users.noreply.github.com>
Date: Tue, 26 Aug 2025 21:51:16 +0000
Subject: [PATCH] deploy: 59aabcd3db975f9ff7a5df918ad17284361723c0

---
 options.xhtml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/options.xhtml b/options.xhtml
index 9f113978c..78acd6926 100644
--- a/options.xhtml
+++ b/options.xhtml
@@ -68660,7 +68660,8 @@ authentication. The package installed through home-manager
 will <span class="emphasis"><em>not</em></span> be able to unlock the session without this
 configuration.</p><p>On NixOS, this is by default enabled with the sway module, but
 for other compositors it can currently be enabled using:</p><pre><code class="programlisting nix">security.pam.services.swaylock = {};
-</code></pre>
+</code></pre><p>On non-NixOS, it is easiest to avoid incompatibility involving PAM by</p><div class="orderedlist"><ol class="orderedlist "  type="1"><li class="listitem"><p>stopping Home Manager from installing swaylock by setting
+<code class="option">programs.swaylock.package</code> to <code class="literal">null</code>; and</p></li><li class="listitem"><p>instead installing swaylock from your distribution’s repository.</p></li></ol></div>
 
 <p><span class="emphasis"><em>Type:</em></span>
 boolean</p>