'xwayland disable' is not necessary to run programs natively under Wayland
I'm afraid the statement is not totally true. Under one circumstance, which is when GUI libraries env variables properly set. Maybe a bug?. I've noticed on sway log that
xwayland.c function of isn't called if and only if
xwayland disable is set.
This is a GTK+ bug. It tries to connect to Xwayland even if it only uses Wayland. I've no idea why, it would be nice to report this to the GTK+ devs and figure out how to fix it.
If you don't disable Xwayland and have it uninstalled, you'll have an invalid `DISPLAY` set.
Keeping XWayland enabled is good for programs that don't work otherwise
It depends on user choice. I think having a wiki section on how to disable xwayland may benefit those who want to avoid X.Org.
Making Kwallet access possible in KDE programs
The article contained the required information before the latest revert to date. Unlike the comment by the moderator suggests, the information is not generic for all graphical environments (unlocking via PAM is sufficient for e.g. Gnome, but not Sway). Aufkrawall (talk) 16:03, 7 December 2019 (UTC)
- In any case, the information is not specific to Sway so it does not belong to this page. Please add it to Kwallet instead. -- Lahwaacz (talk) 16:13, 7 December 2019 (UTC)
Unclear how to start 'output' command as it is not part of minimal installation?
The output command is mentioned in this wiki. It is unclear which package contains it? It was not installed when I did "sudo pacman -S sway".
- "output" is not a shell command, but sway command. You need to install Sway#Wallpaper. -- Lahwaacz (talk) 17:26, 4 January 2020 (UTC) as described in
- I did install swaybg. What do you mean with "output is a sway command"? Bronze (talk) 17:44, 4 January 2020 (UTC)