Not possible to spawn other instances of myappid
Metadata
Current evaluation
Asks for a flatpak-spawn equivalent so a strictly confined snap can launch more instances of itself; this is snapd/AppArmor runtime confinement, not snapcraft — no relevant code and no maintainer response in 669 days.
Suggested action: close not a bug
Reason: The report is about snap runtime confinement, not a snapcraft defect: grepping the repo finds no instance-spawn machinery at all, and the only launcher artifact, extensions/desktop/command-chain/desktop-launch, merely re-execs the app binary within the same confinement domain (`set -- "${SNAP}/gnome-platform/command-chain/desktop-launch" "$@"`), so it cannot lift the restriction. Invoking `snap run` from inside a strictly confined process is blocked by snapd's security model, which is by design and outside what snapcraft (a build tool) can change; an app can still re-exec its own binary directly or use command-chain. Confidence is moderate rather than high because the reporter gave no app name, no snapcraft.yaml, no exact error output and no repro steps ('As title.'), so whether they simply need the direct-re-exec workaround versus a genuine snapd limitation cannot be confirmed from the issue alone.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
1
Complexity:
88
Confidence:
70
Actionability:
18
|
close not a bug | Asks for a flatpak-spawn equivalent so a strictly confined snap can launch more instances of itself; this is snapd/AppArmor runtime confinement, not snapcraft — no relevant code and no maintainer response in 669 days. | |
| stealth/space-bunny-alpha |
Impact:
50
Quick Win:
9
Complexity:
60
Confidence:
84
Actionability:
45
|
needs triage | Strict-confined desktop apps reportedly cannot launch additional instances of themselves; no labels, maintainer response, exact command, or denial logs are provided for triage. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
15
Quick Win:
11
Staleness:
75
Complexity:
25
Confidence:
40
Support Request:
85
|
needs triage | User reports inability to spawn multiple instances of their app from within the app in strict mode; asks why snapcraft doesn't support this feature like flatpak-spawn does. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
90
|
close not a bug | User requests ability to spawn additional app instances from within a strict Snap, noting it works in devmode. Issue is 598 days old with no maintainer response or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
40
Confidence:
80
Support Request:
70
|
needs triage | Request to spawn sibling instances from within a strictly confined snap. Works in devmode but fails in strict. Unlabelled, zero comments, inactive for ~1.6 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
85
|
close not a bug | User requests ability to spawn sibling app instances from within a strict snap, noting it works in devmode but not strict. Issue is 585 days old with no maintainer response or labels. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.