Wayland - Revision history

WhyNotHugo: /* error: XDG_RUNTIME_DIR is invalid or not set in the environment */ Update link to XDG_RUNTIME_DIR

2026-02-11T20:33:11Z

error: XDG_RUNTIME_DIR is invalid or not set in the environment: Update link to XDG_RUNTIME_DIR

← Older revision		Revision as of 20:33, 11 February 2026
Line 35:		Line 35:
	=== error: XDG_RUNTIME_DIR is invalid or not set in the environment ===		=== error: XDG_RUNTIME_DIR is invalid or not set in the environment ===

	The above error message appears when starting services/applications that require the environment variable [[~~#XDG_RUNTIME_DIR\|~~XDG_RUNTIME_DIR]] to be set. Fix it using one of the above methods before proceeding.		The above error message appears when starting services/applications that require the environment variable [[XDG_RUNTIME_DIR]] to be set. Fix it using one of the above methods before proceeding.

	== See also ==		== See also ==

WhyNotHugo: /* XDG_RUNTIME_DIR */ move into standalone article

2026-02-11T20:29:42Z

XDG_RUNTIME_DIR: move into standalone article

@@ Line 27: / Line 27: @@
 As per the protocol specifications, Wayland compositors require the <code>XDG_RUNTIME_DIR</code> variable to be set. When setting paths for {{ic|XDG_RUNTIME_DIR}}, at all times they should follow [https://specifications.freedesktop.org/basedir/latest/#variables '''XDG specifications'''].
-{{Note|If <code>XDG_RUNTIME_DIR</code> variable is set inside startup script/file, it MUST be initialised before the Wayland compositor and the D-Bus session instances are started.}}
+{{Note|<code>XDG_RUNTIME_DIR</code> MUST be initialised before the Wayland compositor and the D-Bus session instances are started.}}
-=== With elogind ===
+For techniques on properly initialising this variable, see [[XDG_RUNTIME_DIR]].
 == Troubleshooting ==

Cubi: fixing it, previous one i edited in threw xdg missing errors for pipewire, THIS should be fine now as i just tested as it works in pipewire.

2026-02-07T08:54:31Z

fixing it, previous one i edited in threw xdg missing errors for pipewire, THIS should be fine now as i just tested as it works in pipewire.

← Older revision		Revision as of 08:54, 7 February 2026
Line 52:		Line 52:

	{{Cat\|~/.profile\|<nowiki>if test -z "${XDG_RUNTIME_DIR}"; then		{{Cat\|~/.profile\|<nowiki>if test -z "${XDG_RUNTIME_DIR}"; then
	export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir		export XDG_RUNTIME_DIR=/tmp/xdg/"${UID}"-xdg-runtime-dir
	if ! test -d "${XDG_RUNTIME_DIR}"; then		if ! test -d "${XDG_RUNTIME_DIR}"; then
	mkdir "${XDG_RUNTIME_DIR}"		mkdir -p "${XDG_RUNTIME_DIR}"
	chmod 0700 "${XDG_RUNTIME_DIR}"		chmod 0700 "${XDG_RUNTIME_DIR}"
	fi		fi
	fi		fi
	</nowiki>}}		</nowiki>}}

Cubi: Current method that's listed on the page will throw a lack of permission error, this method actually works as I just tested on a fresh system just now.

2026-02-07T06:40:02Z

Current method that's listed on the page will throw a lack of permission error, this method actually works as I just tested on a fresh system just now.

← Older revision		Revision as of 06:40, 7 February 2026
Line 51:		Line 51:
	The <code>XDG_RUNTIME_DIR</code> can be initialised manually by adding below snippet to shell init scripts (e.g.: {{Path\|~/.profile}}):		The <code>XDG_RUNTIME_DIR</code> can be initialised manually by adding below snippet to shell init scripts (e.g.: {{Path\|~/.profile}}):

	{{Cat\|~/.profile\|<nowiki>if [ -z "$XDG_RUNTIME_DIR" ]; then		{{Cat\|~/.profile\|<nowiki>if test -z "${XDG_RUNTIME_DIR}"; then
	XDG_RUNTIME_DIR="/~~run/user~~/$~~(id~~ -u)"		export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
			if ! test -d "${XDG_RUNTIME_DIR}"; then
	~~mkdir -pm~~ 0700 "$XDG_RUNTIME_DIR"		mkdir "${XDG_RUNTIME_DIR}"
	~~export XDG_RUNTIME_DIR~~		chmod 0700 "${XDG_RUNTIME_DIR}"
			fi
	fi		fi
	</nowiki>}}		</nowiki>}}

John3-16: 1. Elaborated on XWayland: security risks, testing performance without it, removing XWayland; 2. Style/grammar amendments.

2025-12-30T07:05:27Z

1. Elaborated on XWayland: security risks, testing performance without it, removing XWayland; 2. Style/grammar amendments.

← Older revision		Revision as of 07:05, 30 December 2025
Line 11:		Line 11:
	== XWayland ==		== XWayland ==

	~~Xwayland~~ is an X server that can be instructed to run under Wayland so as to enable ~~various~~ native X11 applications ~~to run during a Wayland session~~ that have not been fully upgraded for Wayland. However, XWayland Is a compatibility layer that is still not sufficiently effective to run native X11 graphical applications that still require running as root without advanced configuration, such as '''gparted''', as XWayland does not have root permissions as per Wayland protocols and for the sake of enhanced security.		XWayland is an X server that can be instructed to run under Wayland so as to enable certain native X11 applications that have not been fully upgraded for Wayland. However, XWayland is a compatibility layer that is still not sufficiently effective to run native X11 graphical applications that still require running as root without advanced configuration, such as '''gparted''', as XWayland does not have root permissions as per Wayland protocols and for the sake of enhanced security.

	{{Pkg\|xwayland}} is typically bundled with compositors, ~~but if~~ it ~~is not required~~, it could be attempted to be removed ~~and configured~~ not to ~~launch with the compositor~~:		Although the X11 protocol design seeks to include flexibility and network transparency, consider that the use of XWayland reintroduces certain [https://biggo.com/news/202511040138_X11-Wayland-Security-Debate X11 design vulnerabilities] into a Wayland session that was originally designed to avoid them, potentially including ''keylogging'' (capturing keystrokes)/taking screenshots/moving/resizing of other windows, although patches are applied where possible.

			{{Pkg\|xwayland}} is typically bundled with compositors. To check performance without XWayland, attempt to disable it on the compositor first (this can be achieved, for example, in [[Sway]], by adding the line {{ic\|xwayland disable}}, say, near the top of the {{Path\|~/.config/sway/config}} file). If performance for your packages appears satisfactory, the package could be attempted to be removed in various compositors, including '''Sway''', but it is a dependency on others, such as '''Labwc''', '''river-classic''', '''Cagebreak'''; ensure that '''apk''' does not indicate that it is a dependency to a given package when removing it:
	{{Cmd\|$ doas apk del xwayland}}		{{Cmd\|$ doas apk del xwayland}}

Line 19:		Line 21:
	{{Main\|Wayback}}		{{Main\|Wayback}}

	Wayback is another X11 compatibility layer, but unlike XWayland, it enables hosting a full X11 desktop environment on Wayland by enabling ~~Xwayland~~ to run in rootful mode (future plans include enabling Wayback ~~rooless~~ mode). This enables [[Xfce]] and [[MATE]] to run fully under Wayland. However, as of December 2025, Wayback is still in alpha quality and thus not recommended for production.		Wayback is another X11 compatibility layer, but unlike XWayland, it enables hosting a full X11 desktop environment on Wayland by enabling XWayland to run in rootful mode (future plans include enabling Wayback rootless mode). This enables [[Xfce]] and [[MATE]] to run fully under Wayland. However, as of December 2025, Wayback is still in alpha quality and thus not recommended for production.

	== XDG_RUNTIME_DIR ==		== XDG_RUNTIME_DIR ==

John3-16: Added stubs for XWayland and Wayback.

2025-12-29T02:11:35Z

Added stubs for XWayland and Wayback.

← Older revision		Revision as of 02:11, 29 December 2025
Line 8:		Line 8:

	Multiple compositor implementations exist, including [[Sway]], [https://en.wikipedia.org/wiki/Mutter%20(software) Mutter] ([[GNOME]]'s compositor) and [https://en.wikipedia.org/wiki/KWin Kwin] ([[KDE]]'s compositor). The following [[:Category:Compositor\|compositors]] are available in Alpine Linux.		Multiple compositor implementations exist, including [[Sway]], [https://en.wikipedia.org/wiki/Mutter%20(software) Mutter] ([[GNOME]]'s compositor) and [https://en.wikipedia.org/wiki/KWin Kwin] ([[KDE]]'s compositor). The following [[:Category:Compositor\|compositors]] are available in Alpine Linux.

			== XWayland ==

			Xwayland is an X server that can be instructed to run under Wayland so as to enable various native X11 applications to run during a Wayland session that have not been fully upgraded for Wayland. However, XWayland Is a compatibility layer that is still not sufficiently effective to run native X11 graphical applications that still require running as root without advanced configuration, such as '''gparted''', as XWayland does not have root permissions as per Wayland protocols and for the sake of enhanced security.

			{{Pkg\|xwayland}} is typically bundled with compositors, but if it is not required, it could be attempted to be removed and configured not to launch with the compositor:
			{{Cmd\|$ doas apk del xwayland}}

			== Wayback ==
			{{Main\|Wayback}}

			Wayback is another X11 compatibility layer, but unlike XWayland, it enables hosting a full X11 desktop environment on Wayland by enabling Xwayland to run in rootful mode (future plans include enabling Wayback rooless mode). This enables [[Xfce]] and [[MATE]] to run fully under Wayland. However, as of December 2025, Wayback is still in alpha quality and thus not recommended for production.

	== XDG_RUNTIME_DIR ==		== XDG_RUNTIME_DIR ==

WhyNotHugo: /* See also */ Backlink to Kodi

2025-12-13T16:38:41Z

Prabuanand: moved the XDG_RUNTIME_DIR path information to their respective sections

2025-12-05T16:13:38Z

moved the XDG_RUNTIME_DIR path information to their respective sections

← Older revision		Revision as of 16:13, 5 December 2025
Line 11:		Line 11:
	== XDG_RUNTIME_DIR ==		== XDG_RUNTIME_DIR ==

	As per the protocol specifications, Wayland compositors require the <code>XDG_RUNTIME_DIR</code> variable to be set.		As per the protocol specifications, Wayland compositors require the <code>XDG_RUNTIME_DIR</code> variable to be set. When setting paths for {{ic\|XDG_RUNTIME_DIR}}, at all times they should follow [https://specifications.freedesktop.org/basedir/latest/#variables '''XDG specifications'''].
	[https://specifications.freedesktop.org/basedir/latest/#variables XDG specifications~~] are set by the [https://specifications.freedesktop.org/ Freedesktop project~~].

	{{Note\| ~~Although paths such as {{Path\|~~/~~tmp~~/~~$(id -u)-runtime-dir}} and similar are sometimes encountered for {{ic\|XDG_RUNTIME_DIR}}~~, ~~at all times they should follow '''XDG specifications'''. It would~~ be ~~set as {{Path\|/run/user/$(id -u)}} by '''elogind''';~~ and ~~as {{Path\|/run/user~~-~~$UID}} and should be mounted as {{ic\|tmpfs}} by [https://git.sr~~.~~ht/~whynothugo/mkrundir mkrundir]. </br>[[#With_pam_rundir\|pam_rundir]] below similarly engages {{Path\|/run/user}}, as per [https://man.sr.ht/~kennylevinsen/seatd/#using-codepam_rundircode upstream]~~}}		{{Note\|If <code>XDG_RUNTIME_DIR</code> variable is set inside startup script/file, it MUST be initialised before the Wayland compositor and the D-Bus session instances are started.}}

	=== With elogind ===		=== With elogind ===

	When using [[elogind]] as a seat manager, it exports <code>XDG_RUNTIME_DIR</code> and other XDG environment variables automatically for each session. No further configuration is required.		When using [[elogind]] as a seat manager, it exports <code>XDG_RUNTIME_DIR</code> and other XDG environment variables automatically for each session. No further configuration is required. <code>XDG_RUNTIME_DIR</code> would be set as {{Path\|/run/user/$(id -u)}} by '''elogind'''.

	=== With pam_rundir ===		=== With pam_rundir ===

	[https://github.com/jjk-jacky/pam_rundir pam_rundir] is a [[PAM]] module that provides the runtime directory variable. Installing the package {{pkg\|pam-rundir}} takes care of dependencies and no further configuration is required.		[https://github.com/jjk-jacky/pam_rundir pam_rundir] is a [[PAM]] module that provides the runtime directory variable. Installing the package {{pkg\|pam-rundir}} takes care of dependencies and no further configuration is required. <code>XDG_RUNTIME_DIR</code> would be set as {{Path\|/run/user/$(id -u)}} by pam_rundir.

	~~{{Note\|~~ <code>XDG_RUNTIME_DIR</code> ~~variable MUST~~ be ~~initialised before the Wayland compositor, and also before the D~~-~~Bus session instance is started in your startup script/file for both the methods listed below.~~}}

	=== With mkrundir ===		=== With mkrundir ===

	[https://git.sr.ht/~whynothugo/mkrundir mkrundir] is an executable that can be used to initialise the runtime directory explicitly by each user. To use <code>mkrundir</Code>, install the package {{pkg\|mkrundir}} available in [[Repositories#Testing\|testing]] repository. In your shell init script (e.g.: {{Path\|~/.profile}} include an entry as follows at the '''top''' of the file {{Cat\|~/.profile\|...		[https://git.sr.ht/~whynothugo/mkrundir mkrundir] is an executable that can be used to initialise the runtime directory explicitly by each user. To use <code>mkrundir</Code>, install the package {{pkg\|mkrundir}} available in [[Repositories#Testing\|testing]] repository. <code>XDG_RUNTIME_DIR</code> would be set as {{Path\|/run/user-$UID}} by mkrundir. In your shell init script (e.g.: {{Path\|~/.profile}} include an entry as follows at the '''top''' of the file {{Cat\|~/.profile\|...
	export XDG_RUNTIME_DIR{{=}}$(mkrundir)		export XDG_RUNTIME_DIR{{=}}$(mkrundir)
	...}}		...}}

John3-16: 1. /* XDG_RUNTIME_DIR / XDG specifications link added; also a Note that XDG_RUNTIME_DIR may be found as "/tmp/$(id -u)-runtime-dir" or similar, but "/run/user/$(id -u)" keeps more in line with other facilities, as described. 2. / Creating and exporting XDG_RUNTIME_DIR manually */ - modified XDG_RUNTIME_DIR path accordingly. See discussion.

2025-12-04T06:17:10Z

1. XDG_RUNTIME_DIR: XDG specifications link added; also a Note that XDG_RUNTIME_DIR may be found as "/tmp/$(id -u)-runtime-dir" or similar, but "/run/user/$(id -u)" keeps more in line with other facilities, as described. 2. Creating and exporting XDG_RUNTIME_DIR manually: - modified XDG_RUNTIME_DIR path accordingly. See discussion.

← Older revision		Revision as of 06:17, 4 December 2025
Line 11:		Line 11:
	== XDG_RUNTIME_DIR ==		== XDG_RUNTIME_DIR ==

	As per the protocol ~~spec~~, Wayland compositors require the <code>XDG_RUNTIME_DIR</code> variable to be set.		As per the protocol specifications, Wayland compositors require the <code>XDG_RUNTIME_DIR</code> variable to be set.
			[https://specifications.freedesktop.org/basedir/latest/#variables XDG specifications] are set by the [https://specifications.freedesktop.org/ Freedesktop project].

			{{Note\| Although paths such as {{Path\|/tmp/$(id -u)-runtime-dir}} and similar are sometimes encountered for {{ic\|XDG_RUNTIME_DIR}}, at all times they should follow '''XDG specifications'''. It would be set as {{Path\|/run/user/$(id -u)}} by '''elogind'''; and as {{Path\|/run/user-$UID}} and should be mounted as {{ic\|tmpfs}} by [https://git.sr.ht/~whynothugo/mkrundir mkrundir]. </br>[[#With_pam_rundir\|pam_rundir]] below similarly engages {{Path\|/run/user}}, as per [https://man.sr.ht/~kennylevinsen/seatd/#using-codepam_rundircode upstream]}}

	=== With elogind ===		=== With elogind ===
Line 38:		Line 41:

	{{Cat\|~/.profile\|<nowiki>if [ -z "$XDG_RUNTIME_DIR" ]; then		{{Cat\|~/.profile\|<nowiki>if [ -z "$XDG_RUNTIME_DIR" ]; then
	XDG_RUNTIME_DIR="/~~tmp~~/$(id -u)~~-runtime-dir~~"		XDG_RUNTIME_DIR="/run/user/$(id -u)"

	mkdir -pm 0700 "$XDG_RUNTIME_DIR"		mkdir -pm 0700 "$XDG_RUNTIME_DIR"

Bezzumnbiu: Fix mistake

2025-11-06T09:18:22Z

Fix mistake

← Older revision		Revision as of 09:18, 6 November 2025
Line 25:		Line 25:
	=== With mkrundir ===		=== With mkrundir ===

	[https://git.sr.ht/~whynothugo/mkrundir mkrundir] is an executable that can be used to initialise the runtime directory explicitly by each user. To use <code>mkrundir</Code>, install the package {{pkg\|mkrundir}} available in [[Repositories#Testing\|testing]] repository. In your shell init script (e.g.: {{Path\|~/.profile}} include an entry as follows at the '''top''' of the file {{Cat\|~.profile\|...		[https://git.sr.ht/~whynothugo/mkrundir mkrundir] is an executable that can be used to initialise the runtime directory explicitly by each user. To use <code>mkrundir</Code>, install the package {{pkg\|mkrundir}} available in [[Repositories#Testing\|testing]] repository. In your shell init script (e.g.: {{Path\|~/.profile}} include an entry as follows at the '''top''' of the file {{Cat\|~/.profile\|...
	export XDG_RUNTIME_DIR{{=}}$(mkrundir)		export XDG_RUNTIME_DIR{{=}}$(mkrundir)
	...}}		...}}

← Older revision		Revision as of 16:38, 13 December 2025
Line 53:		Line 53:
	== See also ==		== See also ==

			* [[Kodi]]
	* [https://wiki.archlinux.org/title/Wayland Wayland - Arch Wiki]		* [https://wiki.archlinux.org/title/Wayland Wayland - Arch Wiki]
	* [https://wiki.gentoo.org/wiki/Wayland Wayland - Gentoo Wiki]		* [https://wiki.gentoo.org/wiki/Wayland Wayland - Gentoo Wiki]