- 1 Window managers and desktop shells
- 2 Weston - Keyboard Shortcuts
Replacing i3way with sway
- 4 dbus
- 5 Graphics driver section
- 6 Troubleshooting "Running graphical applications as root"
- 7 The RDP backend in wlroots
- 8 Move Weston section to its own page & cleanup?
- 9 GDM and NVIDIA proprietary drivers
Window managers and desktop shells
- But, I tried it out (pkg from aur) and it seems very rough. The desktop comes up but when I try launching an app, displays an error dialog and when I close the dialog, it froze my system (I could not even switch ttys)! I didn't do much testing through different compile-options, though. -- Johnchfr (talk) 11:17, 14 October 2014 (UTC)
- It seems they're working on it, so it's worth being documented here, together with any relevant note about the state of the implementation. We don't decide what's good and what's bad for users here, we just give objective information to let the users make their own decisions. -- Kynikos (talk) 00:02, 15 October 2014 (UTC)
- since it's years later now, a quick update: enlightenment is usable (like gnome) with few minor issues --Ubone (talk) 14:22, 4 February 2019 (UTC)
Weston - Keyboard Shortcuts
Replacing i3way with sway
Hi there. I've gone ahead and replaced the i3way table row with a row about sway instead. i3way is vaporware with 2 years of radio silence, and sway is actually usable today. SirCmpwn (talk) 13:29, 16 August 2015 (UTC)
On weston 1.12, application using dbus cannot be launched normally. I've added a workaround to launch on the troubleshooting section.
Graphics driver section
Troubleshooting "Running graphical applications as root"
I think that the https://wiki.archlinux.org/index.php/Wayland#Running_graphical_applications_as_root section should warn that it might be a bug in the application, not a bug in Wayland if the user needs to run a GUI app as root, see https://bugzilla.redhat.com/show_bug.cgi?id=1274451#c76. The wording in https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Graphical_applications_can.27t_be_run_as_root_from_terminal is pretty good, so maybe we should link to that. --Wikizian (talk) 09:27, 5 April 2018 (UTC)
The RDP backend in wlroots
A new paragraph is added in https://wiki.archlinux.org/index.php?title=Wayland&diff=next&oldid=573059. I think it is not enabled in Arch's wlroots? https://bugs.archlinux.org/task/62809.
Move Weston section to its own page & cleanup?
I think its a little odd that Weston is front and center on the Wayland page, and that it takes up 1/3 of the article.
The Weston section comes before the relevant discussion on/list of Wayland compositors which might mislead users into thinking they need Weston for Wayland in the same way they need X.org for X. Especially with the way the page somewhat mirrors the X.org page which starts with xorg-server installation instructions, and that Weston is not listed along with the other Wayland compositors in the compositors section.
In my opinion, the description of compositors should at least come first, and Weston should be listed among them. The Weston section should probably move to its own page. Additionally, some general and important info like XWayland is currently ensconced in the Weston section, so even users who know it is not relevant to them might miss it.
Less important, but I also find it odd that there is no mention of the wayland or wayland-protocols packages on the Wayland page, even though they're just dependencies for some compositors.
Finally, I think there should be a new section discussing application specific configuration as well, e.g. MOZ_ENABLE_WAYLAND or Wayland alternative software like xclip -> wl-clipboard.
- Splitting is done: Weston. Sections were reordered:  -- Lahwaacz (talk) 06:52, 18 October 2019 (UTC)
GDM and NVIDIA proprietary drivers
This section is a candidate for merging with https://wiki.archlinux.org/index.php/GDM#Wayland_and_the_proprietary_NVIDIA_driver
It took about an hour of digging through forum posts to answer the simple question "how do I force GDM to just use Wayland if I have an nvidia GPU?". This information wasn't anywhere on the wiki before, and without this specific action, Wayland is unusable for any desktop session launched via GDM.
The GDM page currently makes it sound like GDM just doesn't support Wayland, but that is not true any more, and in fact, it appears to be working pretty well at the time of writing. I've added the meat of this section to the GDM page, but I think it's no harm to have the info in both places. If someone is trying to find out why GDM won't launch Wayland sessions, as I was, they might just as well go looking on the Wayland page in the wiki as on the GDM page.