Talk:Wayland

Autostart wayland compositor as systemd service

Is it impossible to launch wayland compositor with correct dbus session without any other process(shell, getty, display manager, or uwsm) and kill every process under the compositor after the compositor ends by single systemd service file?

It is used to skip login if physical security is given by another layer (https://vincent.bernat.ch/en/blog/2021-startx-systemd).

I'm seeing /usr/lib/systemd/system/user@1000.service . oech3 (talk) 08:14, 2 April 2025 (UTC)

It has basically the same problem as Systemd/User#Automatic login into Xorg without display manager.

Note that the user@1000.service does not start a session.

— Lahwaacz (talk) 17:20, 4 April 2025 (UTC)

One of the fault is labwc runs before dbus-broker if labwc was launched as a system service.

PAMName=login;TTYPath=/dev/tty1;ExecStart=sleep Infinity and a user services to run labwc before dbus user service works.However, sleep daemon with sd-pam subprocess is bad. So I need sd-pam standalone which is not a binary.

I still hope a minimal method to start session (with shallow knwoledge). oech3 (talk) 17:55, 4 April 2025 (UTC)

Example for proprietary applications without system's Qt.

Since zoom is not one of such example, we need another example. Package in AUR is desirable. oech3 (talk) 16:04, 5 April 2025 (UTC)

Inconsistent use of the term "dynamic"

According to Window_manager#Types, "Dynamic window managers can dynamically switch between tiling or floating window layout." However, the term is also used to describe window managers or wayland compositors that use automatic tiling layouts as opposed to manual tiling. By the first definition River (and maybe others) should be moved to the tiling section and cosmic-comp to the dynamic section. Knotrocket (talk) 03:23, 22 November 2025 (UTC)

If you are sure that river does not support any form of free floating windows feel free to correct it. But good catch about the multiple definitions.

IMO every compositor that supports both (without extensions/scripts), should be in the dynamic section.

Egnrse (talk) 00:05, 28 November 2025 (UTC)

My assumption was that a compositor is only considered dynamic (by the wiki's definition) if an entire workspace/tag can be set as floating, because almost all window managers I know of have the ability to float individual windows using rules keybinds.

The inconsistent defination is also a problem even with the same package in some cases, for example on the window manager page Qtile is listed under the dynamic section but here it is under tiling. Knotrocket (talk) 02:34, 28 November 2025 (UTC)

Xwayland startup

Xwayland can also be started by xwayland-satellite now. Whenov (talk) 14:36, 29 November 2025 (UTC)

Qt5 and system tray

The article now states that "For example, KeepassXC will be unable to minimize to tray. This can be solved by installing qt5ct and setting QT_QPA_PLATFORMTHEME=qt5ct before running the application." As a comment on the page (written by someone else) already mentions, this is not accurate: I'm using this sway+keepassx+waybar inside of wayland happily and minimize to tray works just fine.

—This unsigned comment is by Iosonofabio (talk) 19:07, 7 February 2026 (UTC). Please sign your posts with ~~~~!

That was added back in 2020; since then, this was disputed mid-2024, you claim not having the problem, and I do not either with QT_QPA_PLATFORMTHEME=gtk3. Thus I've felt confident enough that it could be removed. ISSOtm (talk) 08:42, 24 March 2026 (UTC)

libva issue on NVidia GPU

So, I just moved to Wayland and many applications would not start: Chromium and Electron apps.

Some apps did not give any output (Code-oss and Antigravity)

But Chromium and element-desktop gave this output:

[75419:75419:0223/062951.102319:ERROR:content/browser/gpu/gpu_process_host.cc:996] GPU process exited unexpectedly: exit_code=139

[75419:75419:0223/062951.102344:FATAL:content/browser/gpu/gpu_data_manager_impl_private.cc:416] GPU process isn't usable. Goodbye.

I found the solution at:

https://forum.manjaro.org/t/chromium-signal-gpu-process-isnt-usable-goodbye/154140/8

That is to replace `libva-vdpau-driver` for `libva-nvidia-driver`.

I'm posting it here so maybe it help the search engines (although I don't think the talk page is indexed), or if someone find the appropriated way to add this to the article. Arthurfragoso (talk) 10:05, 23 February 2026 (UTC)