Alexis wrote: > Dale <[email protected]> writes: > >> While Wayland is installed here, I don't actively use it. I'm sure it >> is running since things are switching in that direction tho. > > Just to note, since this seems to be based on a common misunderstanding: > > Wayland is a protocol - and more loosely, a collection of protocols[a] > - not a server. There is no 'Wayland server' analogous to an X server. > One doesn't start 'Wayland' and then start a WM/DE; one starts a > compositor, which can be thought of as a combination of a server and a > WM/DE. So it's possible to have Wayland libraries on one's system that > aren't used / 'running' until one actively starts up a Wayland > compositor. Their mere presence doesn't indicate that there must be a > Wayland session running, or that a Wayland session is required to be > running. > > > Alexis. > > [a] Cf. the Wayland Explorer, https://wayland.app/protocols/ > >
That is true. My point was, on the login screen, I don't select Wayland. I use the old X thing, whatever it is called nowadays. That said, I wouldn't be surprised if something Wayland was in use by some software. I just checked and it shows no processes with wayland in it is running but it could be that it just isn't right now. I know some packages on here have the wayland USE flag set. I think some can't really be disabled due to it being needed by other packages. I do recall a good while back that somehow Wayland was selected on the login screen. I noticed it acting weird and logged back out. I then noticed it had Wayland selected somehow. I switched back and it worked like I expected. It was a while ago. By the way, the file still hasn't popped back up, yet. O_o Dale :-) :-)
