On Thu February 24 2022 17:40:18 William Morder via tde-users wrote: Two of those names are incredibly common but: # apt-file search at-spi-bus-laun at-spi2-core: /usr/lib/at-spi2-core/at-spi-bus-launcher at-spi2-core: /usr/libexec/at-spi-bus-launcher For the first two you can find the exe and the command line from the pid. Suppose the pid is 5166. Then: # ls -l /proc/5166/exe lrwxrwxrwx 1 root root 0 Feb 23 13:37 /proc/5166/exe -> /usr/lib/xorg/Xorg # sed -e 's/\x00/ /g' /proc/5166/cmdline /usr/lib/xorg/Xorg -br -deferglyphs 16 -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-TX --Mike

On Thu, 24 Feb 2022 17:40:18 -0800 William Morder via tde-users <users(a)trinitydesktop.org> wrote: If it's the same as the "/usr/libexec/at-spi-bus-launcher" that I keep running into, then it's a Gnomeish accessibility component that's a (technically optional, in practice not so much so) dependency of GTK3, and will pop up any time you launch a GTK3-based program. E. Liddell

On Thu, Feb 24, 2022 at 05:40:18PM -0800, William Morder via tde-users wrote: Ever since the Linux community, especially Gnome, has been taken over by what Jamie Zawinski famously described as the Cascade of Attention-Deficit Teenagers programming model, there has been an increase in programs and processes given utterly bland, uninformative, impossible to google names. My XFCE desktop has programs called "Videos", "Web", "Screenshot" (*two* of them, for some reason!) etc. I presume you have tried googling for "Linux agent" and "Linux applet.py". I don't have to imagine how useless that was, because I just tried it myself. You might have better luck if you copy and paste the line from ps and google that: ps aux | grep agent At least the third is easy to find: https://duckduckgo.com/?q=at-spi-bus-launcher You're running on a new machine, presumably with a new OS. So it is perfectly expected that you will see processes that you've never seen before, and nothing to be concerned about. Since these processes are not part of TDE, you will probably get a better answer by asking the Linux distro community you are using. What have you tried? Since those processes may not be running on our computers, and two of the names are so generic that googling is useless, we need to see what you can see. For example, running `ps aux | grep applet.py` will show us the full process line. `locate applet.py` will hopefully give us a single entry, and then you can run `less PATH/TO/applet.py` to read the code, which hopefully will give some information. At the very least, even the location of the file will help. -- Steve