Xwayland dependency -- how much?

/usr/bin/Xwayland:
file: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 3.2.0,
BuildID[sha1]=f7692a92d1689b1af8511cb22ca5dfe6522892ac, stripped

What would happen if I deleted that? Would it brick my Librem13v4?
My uname -rv:
4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28)

Is Tilix dependent on Xwayland? It seems to play nicely with the non-X
wayland client protocol apps I have been experimenting with.

How much of a system can I have without Xwayland?

To my knowledge it’s not used at all unless you install something that would need it.
You could confirm that by checking the running processes.
While it might not brick your system, I’d not recommend deleting single files that are part of a package. It’s generally bad practice.

I cannot admit that I’m trying to catch what are you about (if using PureOS GNOME) but still this might help you further:

Otherwise, if mentioned package deleted (apt somehow), you should be able to use Recovery Environment with Ethernet connection and go back with: sudo apt install xwayland.


And here is PureOS link to dependencies you are looking for: https://software.pureos.net/package/bin/amber/xwayland.

Otherwise, if mentioned package deleted ( apt somehow), you should be able to use Recovery Environment with Ethernet connection and go back with: sudo apt install xwayland .

Thanks, but I just asked about deletion as a thought-provoker, since I presume
deletion would cause whatever might be dependent on Xwayland to fail,
and thereby show itself, and thereby answer my question :slight_smile:

And here is PureOS link to dependencies you are looking for: https://software.pureos.net/package/bin/amber/xwayland.

Sorry, I wasn’t clear: I actually would like to find out – not what Xwayland itself depends on,
but the other way around – what depends on Xwayland.

E.g., how much of the Gnome GUI environment?

Without Xwayland, would booting have to go to a tty console instead of a GUI login?

BTW: how hard would it be to make the GUI login widget show CapsLock status?
Lack of latching key status indicators is really a usability bug! ;/

1 Like

As shown above you’ll lose:

The following packages will be REMOVED:
gdm3* gnome* gnome-core* gnome-session* gnome-session-bin* gnome-shell-extensions* task-gnome-desktop* xwayland*

So if you can live without gdm3 package (to start with) …

Sorry, I didn’t see small print in the image (I see now it’s clickable to magnify).
(I guess you used apt remove to kick that output off?)

Thank you for your helpful replies!
"(to start with) … "
Famous last words :wink:

I had seen from

$ ps -e f |grep -i way
 1338 tty2     Ssl+   0:00      \_ /usr/lib/gdm3/gdm-wayland-session /usr/bin/gnome-session
 1443 tty2     Sl+    3:34              |   \_ /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6
12686 pts/2    S+     0:00  |       \_ grep -i way

$ pidparents 1338
gdm-wayland-ses tty2      1338 Ssl+ /usr/lib/gdm3/gdm-wayland-session /usr/bin/gnome-session
gdm-session-wor ?         1313 Sl   gdm-session-worker [pam/gdm-password]
gdm3            ?          719 Ssl  /usr/sbin/gdm3
systemd         ?            1 Ss   /sbin/init splash
 
enough to be suspicious ;-)

Where:
$ cat ~/bin/pidparents
#!/usr/bin/bash
# ~/bin/pidparents

pid=${1:-$$}	#this process if no pid specified as $1

while [ $(($pid)) -gt 0 ]; do    
      ps h -p $pid -o comm,tt,pid,stat,args
      pid=$(ps -q $pid -o ppid=)
done
1 Like

Yes, I did! It was from Debian (sorry for quick reply) and here is particular output (not exactly the same) from PureOS with sudo apt purge xwayland: