Re: Where is the Wayland process?

On 27/08/26 at 17:14, Dan Ritter wrote:
> Franco Martelli wrote:
>> Hi,
>>
>> I've installed Debian 13 on a VirtualBox VM with the KDE desktop. At GUI
>> login sddm let me to choose if I want to start a Plasma session with X11 or
>> Wayland. Choosing Wayland, what make me wondered is that a Wayland server
>> process seems missing:
>>
>>     2166 tty1     Ssl+   0:00 /usr/bin/startplasma-wayland
>>     2184 ?        Ssl    0:00 /usr/bin/kwin_wayland_wrapper --xwayland
>>     2195 ?        Rl     1:09 /usr/bin/kwin_wayland --wayland-fd 7 --socket
>> wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1
> 
> 
> Wayland is weird.
> 
> You're expecting a "wayland" process like the Xorg process that runs the
> display, but Wayland is not implemented like that.  Instead, the window
> manager (technically, the compositor) is responsible for implementing
> the Wayland protocols and acting as the display server.
> 
> So, kwin_wayland is the KDE window manager and Wayland server.
> 
> As a direct result, there is no universal upgrade that applies to all
> Wayland desktop environments, and fixes in one (KDE Plasma) do not even
> routinely get ported over to others (GNOME, wlroots...).
> 
> -dsr-

Ah! Thanks, so the first things that comes in my mind is that if I want 
to run another server session e.g. on VT8 I have to play with 
kwin_wayland to obtain something equivalent to:

~$ startx -- :1 vt8 -bpp 16 -nolisten tcp

and looking for "wlroots" (apt search wlroots) I found many compositors 
so I can have a windows manager and then change the compositor (if I 
want) right?

Kind regards,