Change default start scripts from X11 to Wayland #4011
Merged
+2
−2
Conversation
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
Raspberry Pi OS has been using Wayland as the default display server since 2023. This change aligns the default start behavior with the current Raspberry Pi OS standard. X11 start scripts remain available via start:x11 and start:x11:dev for users who still need X11 support.
khassel
approved these changes
Jan 10, 2026
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.
This PR changes the default
startandstart:devscripts to use Wayland instead of X11. I think after three years, it's time to take this step.Background
Since Raspberry Pi OS Bookworm (2023), Wayland is the default display server. As most MagicMirror installations run on Raspberry Pi, this change aligns with what new users already have installed.
Benefits
Especially for new users (which install the OS with Wayland) it's easier - they can simply run
npm startwithout needing to understand display server differences or manually switch scripts.And for projects in general it's better to rely on modern defaults than on legacy.
Breaking Changes
None - X11 support is maintained. Users who really use and need X11 can use
node --run start:x11.