In a Debian 12.5 Stable (bookworm) GNOME wayland VirtualBox VM the commands listed below autostart. Is there a way to identify how they started using HTOP or maybe another app based upon PID?
One approach to preventing the autostart is to remove execute permissions on the app or move the app to another directory. While trying to limit running process in KDE I moved several apps to ../maybelater folders. In those instances where the server would not boot or simply displayed a blank screen mv ../maybelater/[moved app] resolved the issue. Preventing the load failure due to a missing or non-executable file seems like a better approach.
One approach to preventing the autostart is to remove execute permissions on the app or move the app to another directory. While trying to limit running process in KDE I moved several apps to ../maybelater folders. In those instances where the server would not boot or simply displayed a blank screen mv ../maybelater/[moved app] resolved the issue. Preventing the load failure due to a missing or non-executable file seems like a better approach.
Code:
HTOP 2875 cloy 20 0 514M 48736 36288 S 0.0 1.2 0:00.10 /usr/libexec/evolution-source-registry 2891 cloy 20 0 654M 32092 24636 S 0.0 0.8 0:00.04 /usr/libexec/evolution-addressbook-factory 2882 cloy 20 0 723M 31628 20500 S 0.0 0.8 0:00.06 /usr/libexec/evolution-calendar-factory 2869 cloy 20 0 567M 19540 15080 S 0.0 0.5 0:00.04 /usr/libexec/gnome-shell-calendar-server 1654 colord 20 0 236M 15024 9328 S 0.0 0.4 0:00.13 /usr/libexec/colord 2301 cloy 20 0 376M 14256 9224 S 0.0 0.4 0:00.01 /usr/libexec/gsd-smartcard 2288 cloy 20 0 452M 11984 8748 S 0.0 0.3 0:00.02 /usr/libexec/gsd-sharing 1950 cloy 20 0 234M 11820 8776 S 0.0 0.3 0:00.05 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring 2126 cloy 20 0 305M 11000 7916 S 0.0 0.3 0:00.02 /usr/libexec/goa-identity-service 550 root 20 0 227M 10696 6048 S 0.0 0.3 0:00.03 /usr/libexec/switcheroo-control 2486 cloy 20 0 521M 9100 6364 S 0.0 0.2 0:00.01 /usr/libexec/xdg-document-portal 2147 cloy 20 0 228M 9036 6288 S 0.0 0.2 0:00.00 /usr/libexec/gvfs-gphoto2-volume-monitor 549 root 20 0 231M 8864 6156 S 0.0 0.2 0:00.04 /usr/libexec/power-profiles-daemon 542 root -2 0 224M 6544 4084 S 0.0 0.2 0:00.03 /usr/libexec/low-memory-monitor 2323 cloy 20 0 226M 6020 4996 S 0.0 0.2 0:00.00 /usr/libexec/gsd-disk-utility-notify 2072 cloy 20 0 88380 5640 5004 S 0.0 0.1 0:00.00 /usr/libexec/gcr-ssh-agent /run/user/1000/gcr 2074 cloy 20 0 7800 5088 4444 S 0.0 0.1 0:00.00 ssh-agent -D -a /run/user/1000/openssh_agent 1925 cloy 20 0 101M 3460 0 S 0.0 0.1 0:00.00 (sd-pam) 537 root 20 0 6608 1180 1040 S 0.0 0.0 0:00.00 /usr/sbin/cron -f 2491 root 20 0 2480 948 860 S 0.0 0.0 0:00.00 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/docStatistics: Posted by CloisteredNeuron — 2024-06-18 06:25 — Replies 6 — Views 108