I know kubicle is right this time, GG. (I know he's burning to say he's always right. :P )
I also thought I had uninstalled, not purged, all snap related stuff (including everything related to Discover) and I was still able to find snapd services.
Only after I purged snapd as kubicle suggested in the post above, I stopped finding them while running the systemctl list-unit-files | grep snapd command.
-
To my knowledge flatpak was never installed, and it is currently not on my system.Originally posted by kubicle View Post
I have uninstalled snapd & Chromium and unmounted all the loops related to them, as you can see from my "mount" command:
which shows NO loop devices, no tmp-snap.rootfs mount, and I had previously disabled or masked all units, services & timers that relate to snap or flatpak. (I did notice "pstore on /sys/fs/pstore " and it will be disposed of shortly)Code:jerry@Aspire-V3-771:~$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=8066244k,nr_inodes=2016561,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1623420k,mode=755) /dev/sda1 on / type btrfs (rw,relatime,ssd,space_cache,subvolid=485,subvol=/@) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) [B]pstore on /sys/fs/pstore[/B] type pstore (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=20086) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) /dev/sda1 on /home type btrfs (rw,relatime,ssd,space_cache,subvolid=486,subvol=/@home) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1623416k,mode=700,uid=1000,gid=1000)
Having done that I am at loss to explain how
the above services are even starting.Code:Starting flatpak document portal service... Starting sandboxed app permission store... tmp-snap.rootfs_hGokQt.mount: Succeeded. Successfully activated service 'io.snapcraft.Settings' io.snapcraft.Settings[2639]: userd.go:98: Starting snap userd
"snap userd"?
"io.snapcraft.Settings"?
"tmp-snap.rootfs_hGokQt.mount"? (how can it NOT show in the mount command unless it is deliberately hidden?)
It smells of telemetry that can't be easily detected (or removed?).Last edited by GreyGeek; May 11, 2020, 03:39 PM.Leave a comment:
-
-
If someone, like GreyGeek and others, has already purged snapd, why would the service even start at all? There shouldn't be any triggers to start the service, unless there's a timer or an external trigger.
I, for one, am deeply concerned because when I return to 20.04 LTS, I wish very much to avoid snaps and flatpaks, even inadvertent occurrences.Leave a comment:
-
These services are probably started by xdg-desktop-portal (https://launchpad.net/ubuntu/bionic/...desktop-portal)Originally posted by GreyGeek View Post
See: /usr/lib/systemd/user/xdg-*.service
Randomly disabling systemd services is not a good idea, if you have snaps (or flatpaks) you should let them run.
If you don't want snap services (or apps), purge snapd.Leave a comment:
-
Unblockable units or services?
I have NO flatpak services running:
Or snap services:$ systemctl list-unit-files | grep flat
jerry@Aspire-V3-771:~$
YET,journalctl shows:Code:proc-sys-fs-binfmt_misc.mount disabled enabled snap-chromium-1100.mount disabled enabled snap-chromium-1105.mount disabled enabled snap-core-8689.mount disabled enabled snap-core-8935.mount disabled enabled snap-core18-1668.mount disabled enabled snap-core18-1705.mount disabled enabled snap-gnome\x2d3\x2d28\x2d1804-116.mount disabled enabled snap-gtk\x2dcommon\x2dthemes-1474.mount disabled enabled snap-gtk\x2dcommon\x2dthemes-1502.mount disabled enabled snap-snap\x2dstore-209.mount disabled enabled snap-snapd-6434.mount disabled enabled snap-snapd-6953.mount disabled enabled ... snapd.apparmor.service masked enabled snapd.autoimport.service masked enabled snapd.core-fixup.service masked enabled snapd.recovery-chooser-trigger.service masked enabled snapd.seeded.service masked enabled snapd.service masked enabled snapd.system-shutdown.service masked enabled sudo.service masked enabled ... snapd.socket masked enabled snapd.snap-repair.timer masked enabled
Code:Feb 10 13:16:59 Aspire-V3-771 systemd[1685]: Starting flatpak document portal service... ... Feb 10 13:16:59 Aspire-V3-771 systemd[1685]: Starting sandboxed app permission store... Feb 10 13:16:59 Aspire-V3-771 dbus-daemon[1718]: [session uid=1000 pid=1718] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Feb 10 13:16:59 Aspire-V3-771 systemd[1685]: Started sandboxed app permission store. ... Feb 10 13:16:59 Aspire-V3-771 systemd[1685]: Started flatpak document portal service. Feb 10 13:16:59 Aspire-V3-771 systemd[1685]: tmp-snap.rootfs_hGokQt.mount: Succeeded. ... Feb 10 13:17:13 Aspire-V3-771 dbus-daemon[1718]: [session uid=1000 pid=1718] Successfully activated service 'io.snapcraft.Settings' Feb 10 13:17:13 Aspire-V3-771 io.snapcraft.Settings[2639]: userd.go:98: Starting snap userd Later... Feb 10 22:05:01 Aspire-V3-771 systemd[1685]: Stopped flatpak document portal service. ... Feb 11 11:48:08 Aspire-V3-771 systemd[1795]: Listening on REST API socket for snapd user session agent.
io.snapcraft.Settings and flatpak services can be started and stopped at will? (Not my will)
Leave a comment: