← Back to issue list

Undefined Symbol Error While trying to launch Application from a snap packaged VSCode

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2015370
Type
issue
State
open
Author
~ameya-v-singh
Labels
—
Created
Updated
Closed
—

Current evaluation

Snap-installed VS Code cannot launch host applications due to a core20 GLIBC_PRIVATE pthread-symbol mismatch; the report remains untriaged and lacks snap revision and host details.

Suggested action: needs triage

Reason: The concrete loader error makes the failure plausible, but the report provides no VS Code or snapd revision, host details, or exact launch procedure and has no maintainer response or labels. Current code classifies core20 as an ESM base, while snapcraft#5675 removed core20 lifecycle support, so this appears more likely to require routing to snapd or the VS Code snap than a Snapcraft code fix.

Evaluated by: mr-cal-bot

Impact: 58 Quick Win: 7 Complexity: 72 Confidence: 87 Actionability: 44

Issue body

Due to recent updates of snap packages. Currently I am unable launch applications from the Snap Installed VSCode. I am observing following error while trying to launch applications. gimp: symbol lookup error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE It has been captured here in both Stackoverflow and AskUbuntu: https://stackoverflow.com/questions/75921414/java-symbol-lookup-error-snap-core20-current-lib-x86-64-linux-gnu-libpthread https://askubuntu.com/questions/1462295/ubuntu-22-04-both-eye-of-gnome-and-gimp-failing-with-undefined-symbol-error

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 58
Quick Win: 7
Complexity: 72
Confidence: 87
Actionability: 44
needs triage Snap-installed VS Code cannot launch host applications due to a core20 GLIBC_PRIVATE pthread-symbol mismatch; the report remains untriaged and lacks snap revision and host details.
stealth/space-bunny-alpha
Impact: 55
Quick Win: 9
Complexity: 65
Confidence: 90
Actionability: 48
needs triage Apps such as gimp reportedly fail to launch from snap-installed VS Code with a core20 libpthread GLIBC_PRIVATE symbol error; the unlabelled report needs triage and environment details.
qwen3.6-35b-a3b-mtp-q6
Impact: 55
Quick Win: 25
Staleness: 85
Complexity: 55
Confidence: 45
Support Request: 45
close stale User reports undefined symbol error in libpthread when launching apps from snap-packaged VSCode on core20; no maintainer response in 1247 days
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 10
Confidence: 90
Support Request: 95
close not a bug Reports an undefined symbol error when launching external apps from snap-packaged VSCode. Points to a known snap core20/libpthread conflict. No maintainer response or activity in over three years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 85
Support Request: 75
close stale User reports an undefined symbol error when launching external apps from snap-packaged VSCode, linked to snap/core20 updates. Issue is over 3 years old, completely inactive, and lacks maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 10
Confidence: 90
Support Request: 90
close not a bug Reports an undefined symbol error when launching apps from snap-packaged VSCode due to core20/libpthread updates. Issue is over 3 years old, has no maintainer response, and points to external environment issues.

Update history

Date Change
created

Related work

  • Related To: snapcraft#5675 (confidence 88%)

    Core20 lifecycle support was removed, and current Snapcraft treats core20 as an ESM base; this does not directly resolve the VS Code runtime failure.

Related issues

No related issues found above the similarity threshold.