Michael wrote: > On Tuesday, 16 September 2025 06:05:41 British Summer Time Dale wrote: >> 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 >> >> :-) :-) > Alt+Ctrl+F2 or F7 will show you what you started sddm with. Also in a > terminal you can check this output: > > ~ $ echo $XDG_SESSION_TYPE > wayland > > I'm running a wayland compositor here. If you see "x11", this means you are > running an xserver. > > In addition, top and ps axf will show what process is providing your desktop > GUI. > > If you are on wayland the xorg-session.log file will be empty, or absent, > while the wayland-session.log file will be getting fat. Perhaps just as xorg- > session.log file used to. :-)
I just did a ps aux | grep wayland. It didn't return any matches. I also couldn't remember if it was X11, Xorg or something else. I think there was a change a few years ago, maybe. Either way, I don't select Wayland but some packages are installed that have the USE flag on which means they may use Wayland. How or which ones, I dunno. LOL So far, the file still hasn't popped back up. I suspect it will when I log out and back in this coming weekend after updates. If so, I may beat it with the rm hammer again. ;-) Dale :-) :-) P. S. Gave away almost 4 gallons of okra yesterday.
