Wayland: Difference between revisions
WhyNotHugo (talk | contribs) (Mention pam_rundir and reword things a bit) |
WhyNotHugo (talk | contribs) m (Fix mangling done by editor.) |
||
Line 10: | Line 10: | ||
* A login manager such as [[Elogind]] can configure this and other XDG environment variables automatically. | * A login manager such as [[Elogind]] can configure this and other XDG environment variables automatically. | ||
* [https://github.com/jjk-jacky/ | * [https://github.com/jjk-jacky/pam_rundir pam_rundir] can enable this for logins. | ||
* Setting it up manually | * Setting it up manually | ||
Revision as of 12:47, 28 January 2023
This material needs expanding ... A more thorough guide to installing, configuring, and running wayland on Alpine would be better. |
Wayland is a new display protocol that aims to replace X11.
XDG_RUNTIME_DIR
As per the protocol spec, Wayland compositors require the XDG_RUNTIME_DIR
variable to be set. There are a few ways to configure this variable:
- A login manager such as Elogind can configure this and other XDG environment variables automatically.
- pam_rundir can enable this for logins.
- Setting it up manually
Configuring XDG_RUNTIME_DIR manually
Generally, care should be taken when configuring the XDG_*
variables manually as this configuration may have errors or conflict with other utilities that do this automatically.
On a system that's not using elogind nor any pam module that handles this, it's often necessary to set up XDG_RUNTIME_DIR
manually. This can be done by adding a snippet like this one to shell init scripts (e.g.: ~/.profile
):
if test -z "${XDG_RUNTIME_DIR}"; then export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir if ! test -d "${XDG_RUNTIME_DIR}"; then mkdir "${XDG_RUNTIME_DIR}" chmod 0700 "${XDG_RUNTIME_DIR}" fi fi