Running executable from /snap/bin hangs

Metadata

Project: snapcraft (launchpad)
Number: #1826005
Type: issue
State: open
Author: ~knkski
Labels: —
Created: 2019-04-23 03:30 PM UTC
Updated: 2019-08-24 04:11 PM UTC
Closed: —

Current evaluation

Bug report: store-installed strict Rust snap (juju-kubectl) hung when launched via /snap/bin. Reporter resolved it with `adapter: none` + relative `command:`; author and maintainer agreed in 2019 it can be closed.

Suggested action: close not a bug

Reason: This is a user snap-packaging/usage problem rather than a Snapcraft defect: the reporter posted the fix themselves (`apps: bin-name: adapter: none / command: ./bin/bin-name`) and later confirmed "The problem is fixed over there due to the above-mentioned fix of running it as ./bin/bin-name". The Launchpad maintainer (~i-lp-f) noted "I think this can be closed. This snap no longer exists in order to triage this", so the reproducer snap is gone and no further diagnosis or code change is possible; resolution came from configuration, not a Snapcraft fix.

Evaluated by: mr-cal-bot

Impact: 22 Quick Win: 5 Complexity: 10 Confidence: 84 Actionability: 25

Issue body

I have a snap (https://snapcraft.io/juju-kubectl) that works fine when built and installed via snap locally, but fails when installed via the snap store. It's getting pushed to the snap store by the automatic GitHub build integration, and is using the Rust plugin. When installed via the snap store, I can run the binary just fine as `/snap/juju-kubectl/current/bin/juju-kubectl`, so it appears to be an issue with snap and not the build process for the binary itself. When I run `sudo gdb /snap/bin/juju-kubectl`, I get this output repeatedly: [New LWP 13967] [New LWP 13968] [New LWP 13969] [LWP 13969 exited] [LWP 13968 exited] [LWP 13967 exited] process 12930 is executing new program: /bin/dash process 12930 is executing new program: /usr/bin/snap [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fe1f55e7700 (LWP 13971)] [New Thread 0x7fe1f4de6700 (LWP 13972)] [New Thread 0x7fe1effff700 (LWP 13973)] [New Thread 0x7fe1ef7fe700 (LWP 13974)] [New Thread 0x7fe1eeffd700 (LWP 13975)] [Thread 0x7fe1eeffd700 (LWP 13975) exited] [Thread 0x7fe1ef7fe700 (LWP 13974) exited] [Thread 0x7fe1effff700 (LWP 13973) exited] [Thread 0x7fe1f4de6700 (LWP 13972) exited] [Thread 0x7fe1f55e7700 (LWP 13971) exited] process 12930 is executing new program: /snap/core/6673/usr/bin/snap [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fc16b6e4700 (LWP 13978)] [New Thread 0x7fc16aee3700 (LWP 13979)] [New Thread 0x7fc16a6e2700 (LWP 13980)] [New Thread 0x7fc169ee1700 (LWP 13981)] [New Thread 0x7fc1696e0700 (LWP 13982)] [Thread 0x7fc1696e0700 (LWP 13982) exited] [Thread 0x7fc169ee1700 (LWP 13981) exited] [Thread 0x7fc16a6e2700 (LWP 13980) exited] [Thread 0x7fc16aee3700 (LWP 13979) exited] [Thread 0x7fc16b6e4700 (LWP 13978) exited] process 12930 is executing new program: /snap/core/6673/usr/lib/snapd/snap-confine [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". process 12930 is executing new program: /snap/core/6673/usr/lib/snapd/snap-exec

Evaluation history

Date	Model	Scores	Action	Summary
2026-10-02 07:28 PM UTC	stealth/space-bunny-alpha	Impact: 22 Quick Win: 5 Complexity: 10 Confidence: 84 Actionability: 25	close not a bug	Bug report: store-installed strict Rust snap (juju-kubectl) hung when launched via /snap/bin. Reporter resolved it with `adapter: none` + relative `command:`; author and maintainer agreed in 2019 it can be closed.
2026-10-02 07:27 PM UTC	stealth/space-bunny-alpha	Impact: 25 Quick Win: 2 Complexity: 60 Confidence: 72 Actionability: 25	close not a bug	Store-installed juju-kubectl snap hangs when run via /snap/bin though /snap/<name>/current/bin works. Reporter fixed it with `adapter: none` + relative `command: ./bin/bin-name`; maintainer and reporter both said it can be closed.
2026-09-30 09:01 PM UTC	stealth/space-bunny-alpha	Impact: 32 Quick Win: 3 Complexity: 58 Confidence: 80 Actionability: 22	close stale	Store-installed Rust snap (juju-kubectl) hung when launched via /snap/bin wrapper; reporter resolved it with `adapter: none` + `command: ./bin/...`; snap since retired and both author and maintainer agreed it can be closed.
2026-09-24 07:27 PM UTC	stealth/space-bunny-alpha	Impact: 45 Quick Win: 7 Complexity: 72 Confidence: 84 Actionability: 57	needs triage	juju-kubectl runs from its revision path but hangs through /snap/bin after a store install; the gdb exec trace does not identify where execution blocks, and the report lacks maintainer triage.
2026-09-01 08:51 AM UTC	qwen/qwen3.8-27b	Impact: 30 Quick Win: 14 Staleness: 92 Complexity: 55 Confidence: 65 Support Request: 10	close stale	2018 report: Rust-built snap hangs via /snap/bin wrapper after store install, though the direct binary works; gdb shows a re-exec loop in snapd's snap-confine/snap-exec (core 6673). No labels, comments, or maintainer activity for 7 years.
2026-07-23 11:59 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 98 Complexity: 40 Confidence: 85 Support Request: 10	close stale	Snap executable installed via store hangs when run from /snap/bin, showing infinite thread loops in gdb. Unlabelled, no maintainer response, inactive for over 7 years.
2026-07-22 12:21 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 98 Complexity: 40 Confidence: 90 Support Request: 10	close stale	Snap executable from /snap/bin hangs in an infinite execution loop when installed from the store. Issue is over 7 years old with no maintainer interaction or follow-up.
2026-07-10 02:48 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 60 Confidence: 80 Support Request: 10	close stale	Reports a hang when executing a snap binary via /snap/bin, showing GDB thread loops. Inactive for ~7 years with no maintainer response or reproducer.

Update history

Date	Change
2019-08-24 04:11 PM UTC	created

Related work

Related To: canonical/snapcraft#2853 (confidence 55%)
Commit 'meta: do not set snapcraft-runner when adapter is "none"' (9599497fb) is the code path behind the `adapter: none` workaround used here.
Related To: canonical/snapcraft#2889 (confidence 45%)
Commit 'meta: always generate snapcraft-runner to workaround classic PATH bug' (343ac2862) concerns the snapcraft-runner/command-chain behaviour implicated in this store-vs-local difference.

Related issues

No related issues found above the similarity threshold.