Comment 2 for bug 2033964

Also per https://github.com/johannesjo/super-productivity/issues/2744
I transfer my observations over here as the issue seems to be related to Snap itself rather than the specific app.

I do intermittently observe the same (mis-)behavior where different Snaps do not start when called by their .desktop-file from the application launcher, notably SuperProductivity and Teams-for-Linux. I captured some details from syslog for an unsuccessful launching of Teams-for-Linux.

```
2023-09-09T10:31:49.949393+02:00 sp5n systemd[2015]: Started snap.teams-for-linux.teams-for-linux-d05508f8-8073-43b7-bbd2-f2ae5e62561c.scope.
2023-09-09T10:31:49.951299+02:00 sp5n systemd[2015]: Started app-teams\x2dfor\x2dlinux_teams\x2dfor\x2dlinux-40665406bd9c42769fddbba89a1f69bd.scope - Teams for Linux.
2023-09-09T10:31:49.955755+02:00 sp5n plasmashell[237762]: /user.slice/user-1000.slice/user@1000.service/app.slice/app-teams\x2dfor\x2dlinux_teams\x2dfor\x2dlinux-40665406bd9c42769fddbba89a1f69bd.scope is not a snap cgroup
```

Furthermore I noticed that at least some successful tries show the following peculiarity about (un-)mounting some Snap-related rootfs. However I cannot tell how far this does relate to the problem.

```
2023-09-12T06:33:52.331068+02:00 sp5n systemd[1989]: Started app-superproductivity_superproductivity-3e3d8a4f11d14bb8a903947f3ea91a0f.scope - superProductivity.
2023-09-12T06:33:52.333211+02:00 sp5n systemd[1989]: Started snap.superproductivity.superproductivity-74ab88d1-3709-4209-920b-75767b550cc7.scope.
2023-09-12T06:33:52.381853+02:00 sp5n systemd[1]: tmp-snap.rootfs_vpoxiM.mount: Deactivated successfully.
```