Does anybody know what these processes represent?
applet.py agent at-spi-bus-laun
They show up in top, running as processes under my user name, PIDs are all close together in the 2600 range, but they are new visitors that I've never seen before.
I've tried to track them down to their source, so far with no luck. I've had some other issues, too, but I don't know if they are related. Just getting used to running TDE on a different and newer machine, so I expect that things will change and I need to make adjustments. But I can't imagine what I might have installed that does this.
These processes all run at near 100% CPU, although I don't really have much else running at present. In any case, since I haven't seen them ever before yesterday, I want to know. Any help or suggestions are appreciated.
Bill
On Thu February 24 2022 17:40:18 William Morder via tde-users wrote:
Does anybody know what these processes represent?
applet.py agent at-spi-bus-laun
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 Thursday 24 February 2022 17:57:25 Mike Bird wrote:
On Thu February 24 2022 17:40:18 William Morder via tde-users wrote:
Does anybody know what these processes represent?
applet.py agent at-spi-bus-laun
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
Thanks, I'll try sorting this out before I attempt yet another reinstallation. (I have a pile of Linux books in storage, and it's hard to find commands that I don't use very often.)
/proc/2666/exe -> /usr/libexec/geoclue-2.0/demos/agent /proc/2660/exe -> /usr/bin/python3.9
This is what I got back. They seem to have been dragged in when I trying to get tork-trinity working. I don't think they are actual dependencies, hard or otherwise, for that program.
Regarding the last item: /proc/2656/exe -> /usr/libexec/at-spi-bus-launcher
I don't quite know what to make of it. Never seen before, so I wonder if it's necessary.
Bill
On Thu February 24 2022 18:20:17 William Morder via tde-users wrote:
/proc/2666/exe -> /usr/libexec/geoclue-2.0/demos/agent /proc/2660/exe -> /usr/bin/python3.9
This is what I got back. They seem to have been dragged in when I trying to get tork-trinity working. I don't think they are actual dependencies, hard or otherwise, for that program.
You can always try "dpkg --purge --dry-run geoclue-2.0" to see if it would be OK to remove geoclue-2.0. A lot of Gnome uses it but if you're using TDE you might not need Gnome.
For proc 2660 you'll need to find out what command line is being passed to python with:
sed -e 's/\x00/ /g' /proc/2660/cmdline
Regarding the last item: /proc/2656/exe -> /usr/libexec/at-spi-bus-launcher
I don't quite know what to make of it. Never seen before, so I wonder if it's necessary.
Again you can try "dpkg --purge --dry-run at-spi2-core" to see if it is removable. Again a fair number of Gnome packages depend on it.
--Mike
On Thursday 24 February 2022 18:51:00 Mike Bird wrote:
A lot of Gnome uses it but if you're using TDE you might not need Gnome.
--Mike
Thanks, Mike, that's a big help. I suspect it's something Gnomish that's being dragged in. I don't really use Gnome, if possible; when I do need something, I install then uninstall it right away, and watch whatever gets installed along with those packages.
I don't know how it happened, but I can't catch everything.
We'll see how this goes.
Bill
On Thu, 24 Feb 2022 17:40:18 -0800 William Morder via tde-users users@trinitydesktop.org wrote:
Does anybody know what these processes represent? at-spi-bus-laun
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 Friday 25 February 2022 13:34:08 E. Liddell wrote:
On Thu, 24 Feb 2022 17:40:18 -0800 William Morder via tde-users users@trinitydesktop.org wrote:
Does anybody know what these processes represent? at-spi-bus-laun
These strange visitors are Mr Poutine and his soldiers :-))
(many terrible attacks on servers in UE come from Russia, confirmed by many official cyber security services).
On Thu, Feb 24, 2022 at 05:40:18PM -0800, William Morder via tde-users wrote:
Does anybody know what these processes represent?
applet.py agent at-spi-bus-laun
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
They show up in top, running as processes under my user name, PIDs are all close together in the 2600 range, but they are new visitors that I've never seen before.
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.
I've tried to track them down to their source, so far with no luck.
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.
Does anybody know what these processes represent?
applet.py agent at-spi-bus-laun
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.
Yup. :-\
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.
I took out the factory installed 250 GB hard drive, and installed my own 2 TB ssd, so nothing but Devuan Chimaera and TDE (but also occasionally some xfce and mate) have ever touched this machine. It is *almost* a virgin.
Since these processes are not part of TDE, you will probably get a better answer by asking the Linux distro community you are using.
I've tried to track them down to their source, so far with no luck.
What have you tried?
I think I already posted this information. These were the processes, as far as I could trace them at that time.
$ ls -l /proc/2666/exe 17:46 /proc/2666/exe -> /usr/libexec/geoclue-2.0/demos/agent $ ls -l /proc/2660/exe 17:46 /proc/2660/exe -> /usr/bin/python3.9 $ ls -l /proc/2656/exe 17:46 /proc/2656/exe -> /usr/libexec/at-spi-bus-launcher $ sed -e 's/\x00/ /g' /proc/2660/cmdline /usr/bin/python3 /usr/share/system-config-printer/applet.py
At any rate, none of those items show up in top or htop at the moment. I don't know if they could be related to the problem with my browsers not starting. Unless they are, I would consider this issue to be dead. Once I reinstalled and was careful not to reinstall packages using geoclue and python3.9, I didn't seem them any more. And I don't see any connection with my browsers not starting.
Bill
Hi Bill,
Am Samstag, 26. Februar 2022 schrieb William Morder via tde-users:
I've tried to track them down to their source, so far with no luck.
What have you tried?
I think I already posted this information. These were the processes, as far as I could trace them at that time.
$ ls -l /proc/2666/exe 17:46 /proc/2666/exe -> /usr/libexec/geoclue-2.0/demos/agent $ ls -l /proc/2660/exe 17:46 /proc/2660/exe -> /usr/bin/python3.9 $ ls -l /proc/2656/exe 17:46 /proc/2656/exe -> /usr/libexec/at-spi-bus-launcher $ sed -e 's/\x00/ /g' /proc/2660/cmdline /usr/bin/python3 /usr/share/system-config-printer/applet.py
If you know the name of the executable or part of it, then you could use dpkg to find out with which package it has been installed.
man dpkg: dpkg-query actions […] -S, --search filename-search-pattern... Search for a filename from installed packages.
On my system (Devuan Beowulf aka Debian Buster):
$ dpkg -S at-spi-bus-launcher at-spi2-core: /usr/lib/at-spi2-core/at-spi-bus-launcher
It says that the file "/usr/lib/at-spi2-core/at-spi-bus-launcher" is from package at-spi2-core.
Now, aptitude could tell you why it has been installed:
$ aptitude why at-spi2-core i gtk3-tqt-engine-trinity Depends libgtk-3-0 (>= 3.5.8) i A libgtk-3-0 Depends libatk-bridge2.0-0 (>= 2.5.3) i A libatk-bridge2.0-0 Depends libatspi2.0-0 (>= 2.9.90) i A libatspi2.0-0 Recommends at-spi2-core (= 2.30.0-7)
So, on this system of mine it has been installed as a recommends. Probably with the initial installation because I usually switch off recommends. I probably could also remove it without further damage but I'm not sure. Didn't RTFM.
HTH
Kind regards, Stefan
Anno domini 2022 Sat, 26 Feb 14:00:33 +0100 Stefan Krusche scripsit:
Hi Bill,
Am Samstag, 26. Februar 2022 schrieb William Morder via tde-users:
I've tried to track them down to their source, so far with no luck.
What have you tried?
I think I already posted this information. These were the processes, as far as I could trace them at that time.
$ ls -l /proc/2666/exe 17:46 /proc/2666/exe -> /usr/libexec/geoclue-2.0/demos/agent $ ls -l /proc/2660/exe 17:46 /proc/2660/exe -> /usr/bin/python3.9 $ ls -l /proc/2656/exe 17:46 /proc/2656/exe -> /usr/libexec/at-spi-bus-launcher $ sed -e 's/\x00/ /g' /proc/2660/cmdline /usr/bin/python3 /usr/share/system-config-printer/applet.py
If you know the name of the executable or part of it, then you could use dpkg to find out with which package it has been installed.
man dpkg: dpkg-query actions […] -S, --search filename-search-pattern... Search for a filename from installed packages.
On my system (Devuan Beowulf aka Debian Buster):
$ dpkg -S at-spi-bus-launcher at-spi2-core: /usr/lib/at-spi2-core/at-spi-bus-launcher
It says that the file "/usr/lib/at-spi2-core/at-spi-bus-launcher" is from package at-spi2-core.
Now, aptitude could tell you why it has been installed:
$ aptitude why at-spi2-core i gtk3-tqt-engine-trinity Depends libgtk-3-0 (>= 3.5.8) i A libgtk-3-0 Depends libatk-bridge2.0-0 (>= 2.5.3) i A libatk-bridge2.0-0 Depends libatspi2.0-0 (>= 2.9.90) i A libatspi2.0-0 Recommends at-spi2-core (= 2.30.0-7)
So, on this system of mine it has been installed as a recommends. Probably with the initial installation because I usually switch off recommends. I probably could also remove it without further damage but I'm not sure. Didn't RTFM.
You can safely remove gtk3-tqt-engine-trinity and that at-something-funny-thingy will be gone, too. Does gtk3-tqt-engine-trinity actually work?
Nik
HTH
Kind regards, Stefan ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
Am Samstag, 26. Februar 2022 schrieb Dr. Nikolaus Klepp:
Now, aptitude could tell you why it has been installed:
$ aptitude why at-spi2-core i gtk3-tqt-engine-trinity Depends libgtk-3-0 (>= 3.5.8) i A libgtk-3-0 Depends libatk-bridge2.0-0 (>= 2.5.3) i A libatk-bridge2.0-0 Depends libatspi2.0-0 (>= 2.9.90) i A libatspi2.0-0 Recommends at-spi2-core (= 2.30.0-7)
So, on this system of mine it has been installed as a recommends. Probably with the initial installation because I usually switch off recommends. I probably could also remove it without further damage but I'm not sure. Didn't RTFM.
You can safely remove gtk3-tqt-engine-trinity and that at-something-funny-thingy will be gone, too. Does gtk3-tqt-engine-trinity actually work?
:-)
I keep it having around as an old habit but indeed run into problems every now and then. I don't remember the specifics but it is probably the cause for Bill's "browser not starting" problem. See the other thread about it.
Cheers, Stefan
On Fri, Feb 25, 2022 at 04:45:50PM -0800, William Morder via tde-users wrote:
$ ls -l /proc/2666/exe 17:46 /proc/2666/exe -> /usr/libexec/geoclue-2.0/demos/agent
geoclue is a D-Bus service used for providing location services to applications.
Anything that wants to know your location, like web browsers, could be affected if you break geoclue. I guess that depends on whether the browser requires geoclue or merely uses it if available.
$ ls -l /proc/2660/exe 17:46 /proc/2660/exe -> /usr/bin/python3.9 $ ls -l /proc/2656/exe 17:46 /proc/2656/exe -> /usr/libexec/at-spi-bus-launcher
at-spi-bus-launcher is used to provide accessibility functions for GUI applications. Again, the question is whether it is a hard requirement or not.
$ sed -e 's/\x00/ /g' /proc/2660/cmdline /usr/bin/python3 /usr/share/system-config-printer/applet.py
This is the OS's preferred printing configuration GUI tool.
Unless they are, I would consider this issue to be dead. Once I reinstalled and was careful not to reinstall packages using geoclue and python3.9,
I don't know how extensively Python 3.9 is used internally by Devuan and Debian, but in other Linux distros, especially the Red Hat/Fedora/Centos distros, removing python is likely to leave you with a severely broken, or at least restricted, system missing many essential tools.