Wayland: Difference between revisions
WhyNotHugo (talk | contribs) (Mentions that this should only be done when not using PAM) |
m (minor grammar) |
||
Line 11: | Line 11: | ||
Generally it's inadvisable to configure <code>XDG_*</code> variables manually as this configuration may have errors or conflict with other utilities that do this automatically. | Generally it's inadvisable to configure <code>XDG_*</code> variables manually as this configuration may have errors or conflict with other utilities that do this automatically. | ||
That said, on a system that's not using elogind/pam, it's often necessary to set up <code>XDG_RUNTIME_DIR</code> manually. This can be done by adding snippet like this one to shell init scripts (e.g.: <code>~/.profile</code>): | That said, on a system that's not using elogind/pam, it's often necessary to set up <code>XDG_RUNTIME_DIR</code> manually. This can be done by adding a snippet like this one to shell init scripts (e.g.: <code>~/.profile</code>): | ||
<pre> | <pre> |
Revision as of 13:31, 8 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. A login manager such as Elogind can configure this and other Freedesktop.org environment variables automatically.
Generally it's inadvisable to configure XDG_*
variables manually as this configuration may have errors or conflict with other utilities that do this automatically.
That said, on a system that's not using elogind/pam, 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