GNOME Shell in CLOSE_WAIT state

Support
1

I noticed that the gnome-shell has been sitting in the CLOSE_WAIT for quite some time now. It shows it was connected to 8.43.85.4:443 and when doing a reverse lookup, I see the IP maps to master2.openshift4.gnome.org.

Why is the GNOME shell making connections here? How do I prevent it this from happening?

[root@almalinux rlee]# netstat -tnp | grep CLOSE_WAIT
tcp       25      0 10.70.200.10:52646      8.43.85.4:443           CLOSE_WAIT  23702/gnome-shell
tcp       25      0 10.70.200.10:45278      8.43.85.3:443           CLOSE_WAIT  19620/gnome-shell
tcp        1      0 127.0.0.1:57060         127.0.0.1:20001         CLOSE_WAIT  29601/nxserver.bin
tcp       25      0 10.70.200.10:48436      8.43.85.5:443           CLOSE_WAIT  20923/gnome-shell
tcp       25      0 10.70.200.10:50396      8.43.85.3:443           CLOSE_WAIT  32053/gnome-shell
2

Its looking for installed gnome extensions (user scope not system scope wide). If it finds a newer one, it gets updated. Do not install extensions in user’s account to prevent this lookups:

ls -la ~/.local/share/gnome-shell/extensions/

3

The folder doesn’t exist and GNOME extension is required.

I believe GNOME extension is installed at a system wide scope as I have installed GNOME tweaks and customised for desktop icons.

Is there a way to prevent this check?

4

Found the fix for it: thjderjktyrjkt / Disable Gnome Extension Update Check · GitLab