https://blog.berezovskyi.dev/tags/systemd/Recent content in Systemd on berezovskyi notesHugoen-usSun, 17 May 2026 00:00:00 +0000https://blog.berezovskyi.dev/notes/linux-multi-seat-gaming-part-3/Sun, 17 May 2026 00:00:00 +0000https://blog.berezovskyi.dev/notes/linux-multi-seat-gaming-part-3/<h2 id="the-problem">The Problem</h2> <p><a href="https://blog.berezovskyi.dev/notes/linux-multi-seat-gaming-part-2">Part 2</a> ended with a gamescope TV session that could be started and stopped independently - but with an immediate new problem: moving the desk mouse moved the cursor in Steam Big Picture on the TV. Keyboard keys navigated Steam menus.</p> <p>This shouldn&rsquo;t happen. The desk mouse and keyboard are seat0 devices - they are not tagged for seat1 in udev, so seatd should not have given gamescope access to them. The gamescope log confirmed this - there were no &ldquo;Adding device&rdquo; messages from libinput. gamescope itself received no input devices through seatd.</p>https://blog.berezovskyi.dev/notes/linux-multi-seat-gaming-part-2/Sun, 17 May 2026 00:00:00 +0000https://blog.berezovskyi.dev/notes/linux-multi-seat-gaming-part-2/<h2 id="the-goal">The Goal</h2> <p><a href="https://blog.berezovskyi.dev/notes/linux-multi-seat-gaming-part-1">Part 1</a> ended with a working setup and one major limitation: the TV gaming session on seat1 was always-on. To stop it - for GPU passthrough to a Windows VM, or to run Steam on the desk instead - required restarting all of LightDM, which also killed the Sway session on seat0 and lost all open windows.</p> <p>The goal: replace LightDM&rsquo;s static seat1 management with something that can be stopped and started independently, without touching seat0.</p>