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
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
