Building snaps with `kde-neon` extension is not working
Metadata
Current evaluation
Snapcraft Docker images (ghcr.io/canonical/snapcraft:8_core22) fail to build snaps using the kde-neon extension: 'unable to determine source type of /usr/share/snapcraft/extensions/desktop/kde-neon'. Root cause is snapcraft's get_extensions_data_dir() hard-coding sys.prefix, which resolves to the wrong path in the Docker image. Confirmed still broken for core24/kde-neon-6 and GNOME in 2025.
Suggested action: keep open
Reason: A maintainer (tigarmo) acknowledged the report and confirmed extensions 'probably need to do some work to support', and the reporter traced the root cause to snapcraft's get_extensions_data_dir() hard-coding sys.prefix. The issue was re-confirmed still broken in 2025 (core24/kde-neon-6 and GNOME), so it remains a valid, open bug. It is not stale-irrelevant and not a support question, so it should stay open pending a fix.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
60
Quick Win:
27.0
Staleness:
45
Complexity:
55
Confidence:
70
Support Request:
15
|
keep open | Snapcraft Docker images (ghcr.io/canonical/snapcraft:8_core22) fail to build snaps using the kde-neon extension: 'unable to determine source type of /usr/share/snapcraft/extensions/desktop/kde-neon'. Root cause is snapcraft's get_extensions_data_dir() hard-coding sys.prefix, which resolves to the wrong path in the Docker image. Confirmed still broken for core24/kde-neon-6 and GNOME in 2025. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
75
Complexity:
30
Confidence:
85
Support Request:
10
|
needs triage | Reports kde-neon extension build failures in the snapcraft Docker image due to a hardcoded Python path mismatch. Confirmed unresolved in newer versions, awaiting maintainer investigation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
40
Confidence:
85
Support Request:
10
|
keep open | Bug in Snapcraft Docker/Rocks images where extensions fail to load due to incorrect Python sys.prefix path resolution. Validated across multiple extensions and Snapcraft versions, but remains unaddressed. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
45
Confidence:
75
Support Request:
5
|
needs triage | Snapcraft Docker images fail to locate extensions due to incorrect sys.prefix path resolution. The issue persists across versions and remains open pending a fix. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1881963 extension: kde-neon fails on arm64 | snapcraft (launchpad) | closed | Abandoned due to inactivity. The kde-neon extension fails on arm64 because the kde-frameworks-5-core18 snap lacks arm64 builds, causing snapcraft to fail during prerequisite installation. | |
| #5128 KDE Neon 6 broken on arm64 | snapcraft | open | kde-neon-6 extension fails on arm64 because the kf6-core22 content snap is missing Qt6 libraries (73MB vs 2GB amd64). Filed 682 days ago, no maintainer response, only 1 user comment. Root cause is in the external KDE content snap, not snapcraft code. |