Fix initial-setup GUI failing to start on ARM due to weston input device access - #162
Open
jgroman wants to merge 1 commit into
Open
Fix initial-setup GUI failing to start on ARM due to weston input device access#162jgroman wants to merge 1 commit into
jgroman wants to merge 1 commit into
Conversation
logind does not assign a seat to sessions created by systemd services, so weston's libseat logind backend cannot acquire input devices. This causes weston to reject all input devices and crash on shutdown. Use the noop libseat backend instead, which lets weston open devices directly as root without needing logind's device handoff. Fixes the GUI startup on ARM (RPi) where PR rhinstaller#156's VT switching alone is insufficient. Resolves: rhbz#2358688
Contributor
|
Your author is wrong and not recognized by GitHub. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #156 fixed the GUI startup on x86 by adding VT switching and multi-GPU enumeration, but the fix is insufficient on ARM (e.g., Raspberry Pi). On ARM, weston starts, gets "session control granted" from libseat's logind backend, but then rejects all input devices with "not using input device" and crashes with SIGSEGV in Mesa's teardown path.
Root cause:
initial-setup.serviceruns as a systemd service (User=root). Whenpam_systemd.socreates a logind session, it getsclass=user-early type=ttywith no seat assignment. This is by design -- logind does not assign seats to sessions created by systemd services. Without a seat, libseat's logind backend cannot hand over input devices to weston, and weston's libinput rejects them all.Fix: Set
LIBSEAT_BACKEND=noopbefore the weston invocation. The noop backend bypasses logind session management entirely. Since initial-setup runs as root, weston can open DRM and input devices directly without needing logind's device handoff.This fix is safe to apply universally alongside PR #156's VT switching and multi-GPU changes. The noop backend is appropriate here because initial-setup is a one-shot root process during first boot -- multi-seat and unprivileged access scenarios do not apply.
Tested on Raspberry Pi 4 Model B, Fedora 45 Xfce aarch64, kernel 7.2.0-rc6, weston 15.0.1, Mesa 26.2.0.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2358688
Assisted-By: Claude Opus 4.6