Zen

Translation

English type: delimited block .
$ echo $WAYLAND_DISPLAY
wayland-0
34/340 · 34

Sign in to save the translation.

English Korean Actions
In need of other love
 
Reviews for technical accuracy are greatly appreciated. If you want to help, see the https://pagure.io/fedora-docs/quick-docs/blob/master/f/README.md[README file] in the source repository for instructions.
 
Pull requests accepted at https://pagure.io/fedora-docs/quick-docs
 
Once you've fixed this page, remove this notice.
 
https://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29[Wayland] is intended as a simpler replacement for https://en.wikipedia.org/wiki/X_Window_System[X11]. Wayland changes the design of a Linux desktop architecture considerably. Unlike X11, there is no dedicated standalone server in Wayland. What was previously done between the app, its toolkit, the Xserver and the window manager is now shared between the app, its toolkit and the Wayland compositor which manages the compositing, input, windows management, etc. The apps and toolkits are now in charge of their own rendering and decorations (client side decorations), so any issues usually sit between the toolkit (e.g. GTK+) and the Wayland compositor (e.g. mutter).
 
You can read more about Wayland on the GNOME https://wiki.gnome.org/Initiatives/Wayland[Wayland initiative] wiki page. You can read more about the current state of Wayland features on link:Wayland_features[Wayland features] page.
 
Identifying Wayland problems
 
Are you running a Wayland session?
 
In *GNOME*, there's a gear button at the login screen which can be used to either log into a Wayland session (simply called _GNOME_, it's the default option), or a legacy X11 session (called _GNOME on Xorg_). If you have a password-less user account, you won't see the gear icon, it is displayed only when the password prompt appears. Use the gear button to determine type of session you're logging into. If you want to start your session in a different way, read https://wiki.gnome.org/Initiatives/Wayland/TryingIt[the advanced techniques for trying Wayland].
 
image:gdm-pick-wayland.png[gdm-pick-wayland.png,title="gdm-pick-wayland.png",width=400]
 
In *KDE*, there is support for running a nested Wayland session inside your X11 session. You'll need to install `kwin-wayland` package and then follow up with https://community.kde.org/KWin/Wayland[this howto]. There doesn't seem to be out-of-the-box support for running a full Wayland session at the moment.
 
Other desktop environments are not currently capable of running a Wayland session.
 
Identifying the session type in runtime
 
If you want to figure out which type of session you're running right now, without logging out and in again, you can use several ways to figure it out:
 
Wayland session should have `WAYLAND_DISPLAY` variable set, X11 session should not have it:
 
$ echo $WAYLAND_DISPLAY
wayland-0
$ echo $WAYLAND_DISPLAY
wayland-0
`loginctl` can give you this information. First run `loginctl` and find your session number (if should be an integer number, with your username and seat assigned). Then look at the session type (`x11` or `wayland`):
 
$ loginctl show-session <YOUR_NUMBER> -p Type
Type=x11
 
If you're running an X11 session, not a Wayland session, your problems are not related to Wayland. It's a bug either in that particular application, or X11 itself, see link:How_to_debug_Xorg_problems[How to debug Xorg problems].
 
Does your application run on Wayland natively, or uses XWayland (X11 compatibility layer)?
 
It is important to know whether the problematic application is a native Wayland application, or runs through XWayland, which allows legacy applications to still run on top of Xorg server, but display in a Wayland session.
 
There are several ways how to identify whether an application is using Wayland or XWayland:
 
Select the window using `xwininfo` or `xprop`. Run:
 
$ xwininfo
 
Your mouse pointer should change to a cross under X11, it doesn't seem to change under Wayland. Now click anywhere inside the app window you want to test. If the `xwininfo` command finishes (it should print window properties into the terminal), the app under test is running under XWayland. If nothing happens (the `xwininfo` command is still waiting until you select a window), the app under test is running under Wayland (you can close the command with `Ctrl+C`). + You can also use `xprop` command using the same instructions.
 
XWayland applications are listed in `xlsclients` output. Run:
 
$ xlsclients
$ xlsclients
However, this list of not always entirely reliable, some apps might be missing.
 
You can try to run the app while unsetting `DISPLAY` environment variable:
 
$ DISPLAY='' command
 
If the application runs OK, it should be using Wayland natively.
 

Loading…

User avatar simmon

Suggestion accepted
$ echo $WAYLAND_DISPLAY
wayland-0
$ echo $WAYLAND_DISPLAY
wayland-0
3 months ago
User avatar mt:weblate-translation-memory

Suggestion added
$ echo $WAYLAND_DISPLAY
wayland-0
$ echo $WAYLAND_DISPLAY
wayland-0
5 months ago
User avatar None

String added in the repository
$ echo $WAYLAND_DISPLAY
wayland-0
 
5 months ago
Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Korean
No related strings found in the glossary.

String information

Source string description
type: delimited block .
Flags
no-wrap
Source string location
./pages/troubleshooting-wayland-problems.adoc:80
String age
5 months ago
Last updated
3 months ago
Source string age
11 months ago
Translation file
po/ko/master/pages/troubleshooting-wayland-problems.po, string 25