Unable to launch .desktop file for snap app (without attaching terminal).

<blockQuote>

<!--- Your issue may already be reported!
!!! Please search the issues before creating one !!! -->

### Your Environment

<!--- Include as many relevant details about the environment you experienced the bug in -->

- Version used:

 ```sh
 snap info superproductivity
 ```

 ```log
 PS /home/rokejulianlockhart> snap info superproductivity
 name: superproductivity
 publisher: johannesjo
 store-url: https://snapcraft.io/superproductivity
 contact: https://github.com/johannesjo/super-productivity
 license: unset
 commands:
   - superproductivity
 snap-id: wZo5sef6NuUKCW6DP83fJ6zIZyd5R1sA
 tracking: latest/edge
 refresh-date: 2 days ago, at 19:22 BST
 channels:
   latest/stable: 7.13.2 2023-04-16 (1737) 89MB -
   latest/candidate: 7.14.2 2023-08-21 (1776) 89MB -
   latest/beta: ↑
   latest/edge: 7.14.2 2023-08-25 (1784) 89MB -
 installed: 7.14.2 (1784) 89MB -
 PS /home/rokejulianlockhart>
 ```

 ```sh
 snap list
 ```

 ```log
 Name Version Rev Tracking Publisher Notes
 superproductivity 7.14.2 1784 latest/edge johannesjo -
 ```

- Operating System and version: cpe:/o:opensuse:tumbleweed:20230823
- Desktop Environment: KDE Plasma
<!--
- Browser Name and version:
-->

### Expected Behavior

SuperProductivity should be invocable from the Application Launcher (Start Menu) Plasmoid (widget).

Please note that the `--edge` `thunderbird` `snap` also exhibited this behaviour until approximately last week, but this appears to have been remediated without my intervention (except `snap refresh`).

### Current Behavior

<!--- Tell us what happens instead of the expected behavior -->

### Steps to Reproduce (for bugs)

<!--- Does the error happen once or are you able to reproduce it reliably? --->
<!--- Provide a link to a live example or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->

0. ```sh
 snap install superproductivity --channel=latest/edge
 ```
0. 

### Can you reproduce this reliably?

Yes.

### Console Output

<!--- Is there any output if you press Ctrl+Shift+i (Cmd+Alt+i for mac) in the console tab? If so please post it here. -->

```log
SNAP: common directory is used
15:12:26.575 › { enabled: null, showDevTools: false, mode: 'bottom' }

(superproductivity:18377): Gtk-WARNING **: 15:12:26.765: Theme parsing error: gtk.css:3536:25: 'font-feature-settings' is not a valid property name
Gtk-Message: 15:12:26.779: Failed to load module "colorreload-gtk-module"
Gtk-Message: 15:12:26.779: Failed to load module "window-decorations-gtk-module"
Saving backups to /home/rokejulianlockhart/snap/superproductivity/common/.config/superProductivity/backups
15:12:27.535 › Saving backups to /home/rokejulianlockhart/snap/superproductivity/common/.config/superProductivity/backups
/usr/share/libdrm/amdgpu.ids: No such file or directory
15:12:29.511 › No custom styles detected at /home/rokejulianlockhart/snap/superpro...

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.
```