Issue & PR triage
Loading...
Showing 57 of 57 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1617302 |
Specifying a nonexistent plug does cause any errors | ~mattyw | 3717d | close not a bug | 46 | 95 | 39 | Unknown plug typos once built silently; snapd now validates interfaces and Snapcraft has used that validation since before June 2020, leaving no Snapcraft-side fix. |
|
snapcraft (launchpad) issue #1676186 |
the build scriptlet doesn't take into account the source-subdir | ~elopio | 3505d | close not a bug | 46 | 74 | 8 | craft-parts intentionally runs override-build from the part build directory; source-subdir applies to plugin builds, and the documentation explicitly exempts override-build. |
|
snapcraft (launchpad) issue #1869544 |
snapcraft use cached packages across VMs | ~keshavnrj | 2406d | close not a bug | 45 | 75 | 17 | Shared APT caching across builds is now available through a documented package-cache proxy and http_proxy, although no native VM-wide cache is evidenced and the linked legacy trigger remains unreproduced. |
|
snapcraft (launchpad) issue #1730208 |
Snapcraft python build fails to run with `GLIBC_2.25' not found error message | ~manuvarkey-gmail | 3281d | close not a bug | 45 | 85 | 29 | GLIBC failure was caused by building on Artful for a Xenial runtime; the supported Xenial cleanbuild workaround was confirmed, leaving only a historical tutorial-documentation concern. |
|
snapcraft (launchpad) issue #1760897 |
Classic confined snap started segfaulting after 2.40 upgrade | ~kos.tsakalozos | 3132d | close not a bug | 40 | 65 | 10 | Classic snap segfaults after snapcraft 2.40 due to upstream patchelf corrupting Go binaries; maintainer pointed to the documented no-patchelf build attribute (upstream NixOS/patchelf#146). |
|
rockcraft issue #579 |
fork/exec error when building Go rock with the 24.04 build-base | gruyaume | 889d | close not a bug | 38 | 86 | 16 | Bare Go rocks on ubuntu@24.04 need base-files_lib for the usrmerged ELF-loader paths. The reporter confirmed that adding the slice fixes the fork/exec failure. |
|
craft-parts issue #427 |
Using `source-subdir` results in `No such file or directory` | sed-i | 1281d | close not a bug | 38 | 90 | 19 | Documented behavior: source-subdir sets the plugin build location, but override-build runs from the build root; callers must cd into the subdirectory themselves. |
|
snapcraft (launchpad) issue #1670749 |
classic confinement requires manually setting PATH and PYTHONPATH | ~corey.bryant | 3524d | close not a bug | 36 | 55 | 9 | Classic snaps may need explicit PATH/PYTHONPATH, but the reporter and snappy team said this was by design; current metadata handling intentionally omits injected PATH and library paths. |
|
snapcraft (launchpad) issue #1669854 |
Hidden files are not staged after "dump" | ~joeborg | 3527d | close not a bug | 35 | 92 | 23 | Hidden top-level files from dump are omitted by default during stage and prime; current fileset behavior and documentation treat this as intentional, with an explicit workaround. |
|
rockcraft issue #178 |
`rockcraft` crashes at the `update apt cache` step | gruyaume | 1382d | close not a bug | 32 | 55 | 10 | apt-get update inside LXD build instance fails on GitHub's ubuntu-22.04 runners; maintainers traced it to Docker/LXD iptables clash, not a rockcraft bug, and point to canonical/setup-lxd and canonical/craft-actions rockcraft-pack as fix (now documented). |
|
snapcraft (launchpad) issue #1820797 |
Snapcraft should allow prepending/appending additional text from description... | ~brlin | 2782d | close not a bug | 30 | 55 | 9 | Prefix/suffix composition for adopted metadata was declined; maintainers direct packagers to override the complete summary or description instead. |
|
snapcraft (launchpad) issue #1704103 |
New git commits don't mark pull step dirty | ~saviq | 3396d | close not a bug | 30 | 85 | 19 | New commits intentionally do not dirty a source-type: git pull step; maintainers redirected automatic source tracking toward source-type: local. |
|
snapcraft (launchpad) issue #1955887 |
snapcraft npm doesn't respect npm-node-version | ~nanu | 1767d | close not a bug | 30 | 94 | 24 | Legacy npm configuration was misleading: override-build bypasses the plugin-managed Node download; current craft-parts requires npm-include-node with npm-node-version. |
|
snapcraft (launchpad) issue #1899033 |
Passing --store has weird syntax/requirements and user-facing error is not... | ~roadmr | 2213d | close not a bug | 30 | 55 | 12 | A copied zero-width space in the --store value caused the 400 response; clean input succeeds. Clearer API errors and store-aware output are separable UX enhancements. |
|
snapcraft (launchpad) issue #1660302 |
foreign architecture builds doesn't work with classic snaps | ~popey | 3560d | close not a bug | 30 | 35 | 1 | The classic-snap --target-arch build is unsupported because architecture selection is plugin-specific; the sole maintainer response said general support required Debian cross-compilation, and the issue remains open. |
|
snapcraft (launchpad) issue #1809852 |
zipfile.BadZipFile: File is not a zip file raises an exception | ~timhirrel | 2864d | close not a bug | 30 | 30 | 6 | Open report that Snapcraft 2.43.1 fails during pull when a declared ZIP is malformed; current craft-parts tests still expect BadZipFile, and no source/config or desired behavior is provided. |
|
craft-parts issue #788 |
launchpad builder won't clone one of three identical repos | popey | 833d | close not a bug | 30 | 90 | 23 | Root cause identified: grype declares an SSH submodule URL that cannot authenticate on Launchpad. HTTPS submodules or omitting unused submodules provide workarounds; #788 remains open. |
|
snapcraft (launchpad) issue #1860550 |
Defining base snap breaks snapping Subiquity | ~nwessels | 2473d | close not a bug | 28 | 25 | 4 | Adding `base: core18` to Subiquity's snapcraft.yaml left the ISO's seed invalid, so snapd hung seeding with empty /snap/bin. snapd maintainers traced it to seed.yaml generation in the ISO builder, not snapcraft, and marked their task Invalid. |
|
snapcraft (launchpad) issue #1599234 |
should not remove suid/guid from binaries when confinement is devmode | ~osomon | 3769d | close not a bug | 28 | 40 | 6 | Requests that snapcraft keep suid/sgid bits on extracted binaries when building devmode snaps (oxide/chrome-sandbox aborted). Maintainers say stripping is intentional; workarounds are userns sandbox, browser-support allow-sandbox:true, or OXIDE_NO_SANDBOX. |
|
snapcraft (launchpad) issue #1804957 |
Malicious namesquatting of snaps | ~buzz-- | 2896d | close not a bug | 28 | 15 | 1 | Complaint that an unverified publisher holding the 'bitcoin' snap name pushes outdated software, calling for stronger store name/publisher vetting; out of scope for the snapcraft build tool |
|
snapcraft (launchpad) issue #1814729 |
Setting SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY doesn't take effect | ~popey | 2824d | close not a bug | 28 | 32 | 4 | Feature request: SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY/CPU are ignored when an existing Multipass VM is reused; maintainer confirmed the vars only apply at VM creation and advised purging the instance. Not implemented |
|
snapcraft (launchpad) issue #2090799 |
Not possible to spawn other instances of myappid | ~sblantipodi | 697d | close not a bug | 28 | 18 | 1 | 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. |
|
snapcraft (launchpad) issue #1858023 |
export-login is too big for env variable | ~abitrolly | 2494d | close not a bug | 25 | 25 | 1 | Reporter wants smaller export-login macaroon so it fits Travis env vars; maintainer reproduced the failure and confirmed it is a Travis limit, pointing to `travis env set`/`encrypt-file`. Idle since 2020. |
|
snapcraft (launchpad) issue #1697473 |
FLTK applications cannot start | ~msweet | 3427d | close not a bug | 25 | 90 | 18 | FLTK launch failures were configuration-related; the reporter confirmed desktop-gtk3, an after dependency, and desktop-launch $SNAP/bin/<cmd> fixed both apps. |
|
snapcraft (launchpad) issue #2007479 |
speedx doesn't launch in ubuntu 22.04.1 | ~624wtl | 1352d | close not a bug | 25 | 30 | 6 | User reports third-party 'speedx' snap aborts on Ubuntu 22.04.1 with 'could not find or load the Qt platform plugin "wayland-egl"'; app-specific packaging bug, no snapcraft code implicated, unlabelled and unanswered. |
|
snapcraft (launchpad) issue #1871660 |
create-key with no passphrase with pop-up loop | ~jamesj | 2396d | close not a bug | 25 | 55 | 7 | Usage question: snapcraft create-key over SSH on a headless VM loops on a GnuPG graphical passphrase pop-up when leaving the passphrase empty; behavior originates in snapd/gnupg, not snapcraft. |
|
snapcraft (launchpad) issue #1964418 |
firefox just circles jig 2022-03-09 | ~ac0xl | 1695d | close not a bug | 25 | 20 | 2 | User report (Mar 2022) that the Mozilla-maintained firefox snap hangs/spins on Ubuntu 21.10 on a Raspberry Pi 4B (4GB), plus a general anti-snap rant; logs hosted externally, no maintainer response |
|
snapcraft (launchpad) issue #1802385 |
[google-cloud-sdk] `gcloud container clusters get-credentials` resolves... | ~jesse-glick | 2912d | close not a bug | 25 | 10 | 1 | gcloud from the Snap writes a version-pinned /snap/google-cloud-sdk/59/bin/gcloud as cmd-path in ~/.kube/config. Filed on snapcraft, but the snap is Google-published and Google declined to fix it; no maintainer response, unlabelled. |
|
snapcraft (launchpad) issue #1638405 |
libunity not added to LD_LIBRARY_PATH | ~zyga | 3649d | close not a bug | 25 | 88 | 12 | Launchpad builds lacked libunity in LD_LIBRARY_PATH; maintainers concluded the app improperly relied on Unity private libraries, so no Snapcraft fix is warranted. |
|
snapcraft (launchpad) issue #1990166 |
Snapcraft 7 silently ignores any files ending in *.snap when the source is a folder | ~itrue | 1502d | close not a bug | 24 | 91 | 15 | Deliberate behavior: folder sources exclude *.snap files. The maintainer linked the ignore setting, and the exact build reproducer still fails when a needed snap is omitted. |
|
snapcraft (launchpad) issue #1827216 |
local source must not specify parent directories | ~tejohnso | 2739d | close not a bug | 24 | 88 | 19 | Reported local-source confinement is obsolete: current craft-parts accepts relative parent paths, and Snapcraft spread tests cover sources ../.. and ../../.. |
|
rockcraft issue #343 |
apt package is not installed in the image. | Abuelodelanada | 1175d | close not a bug | 24 | 90 | 20 | ca-certificates is omitted because the part's stage allowlist filters its files; moving the package to a nil part provides a working workaround. |
|
snapcraft (launchpad) issue #1882793 |
snapcraft doesn't remove the build.sh scripts after part cleanup | ~dmitriis | 2334d | close not a bug | 22 | 78 | 16 | A 2020 report says `snapcraft clean` leaves generated `parts/*/run/build.sh` files. Maintainers classified this as expected because every build run rewrites the script; documentation was promised. |
|
snapcraft (launchpad) issue #1826005 |
Running executable from /snap/bin hangs | ~knkski | 2747d | close not a bug | 22 | 25 | 5 | 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. |
|
snapcraft (launchpad) issue #1634803 |
snapcraft register-key doesn't use U1 SSO login credentials | ~vrruiz | 3663d | close not a bug | 22 | 32 | 4 | 2016 report that `snapcraft register-key` re-prompts for U1 SSO login even after `snapcraft login`. Discussed as by-design (fresh modify_account_key-scoped login); current keys.py still deliberately unsets credentials and re-logins. |
|
snapcraft (launchpad) issue #1943242 |
snapcraft can't build while I'm also running virtual box | ~colin-king | 1876d | close not a bug | 22 | 30 | 5 | Report: snapcraft builds fail when Multipass conflicts with a running VirtualBox ("Another virtual machine manager is currently running"); reporter calls it a fundamental Multipass limitation. No maintainer response in ~5 years. |
|
snapcraft-rocks issue #58 |
Run YAML validity/schema linters before `snapcraft` | abitrolly | 766d | close not a bug | 22 | 30 | 4 | Feature request to run YAML/schema linters before snapcraft. Maintainer tigarmo triaged: missing `base:` and stale-build-dir errors are Snapcraft/craft-parts bugs, not bugs here; author conceded reticketing elsewhere. |
|
snapcraft (launchpad) issue #1675513 |
Snap builds on arm are extremely slow causing them to fail | ~pat-mcgowan | 3507d | close not a bug | 22 | 15 | 3 | Launchpad ARM/US builds timed out at 2h from apt download latency. Root cause was infra (BIND DNS bug on builder proxy) plus snapcraft's lack of connection reuse; wgrant said it isn't a code bug and builds now finish in ~16 min. Referenced _deb.py code path is gone. |
|
craft-grammar issue #31 |
If architecture after to is an array, it is not matched corretly | dariuszd21 | 855d | close not a bug | 20 | 75 | 10 | Multiple target architectures are intentionally treated as an AND and cannot match one architecture; the remaining concern is misleading documentation about valid selector-list usage. |
|
snapcraft (launchpad) issue #2073694 |
core24 / Qt6 : libEGL fatal: DRI driver not from this Mesa build... | ~brouits | 831d | close not a bug | 20 | 35 | 4 | core24 Qt6 snap with gnome extension aborts with libEGL 'DRI driver not from this Mesa build' because mesa-2404 rev 44 was still 24.0.5; author redirected the report to canonical/mesa-2404#7; unlabelled, no maintainer reply. |
|
snapcraft (launchpad) issue #1822910 |
GitKraken fails with XAUTHORITY error (Ubuntu 18.10) | ~william-full-moon | 2767d | close not a bug | 20 | 35 | 5 | User reports GitKraken snap won't start on Ubuntu 18.10 (Electron XAUTHORITY warning, ~/snap/gitkraken/138 not a directory) and asks for a configurable snap data dir plus a store 'Report Bug' button; untriaged, no maintainer response. |
|
snapcraft (launchpad) issue #1830520 |
Sorry, an error occurred in Snapcraft: | ~linuxmanco | 2714d | close not a bug | 20 | 55 | 9 | Snapcraft 2.43.1 crashed with FileNotFoundError for /opt/StorageCraft/spx/bin/spx_service while composing snap.yaml; maintainer dev-mahara replied with a patch for the reporter's own project repo, not a Snapcraft fix. |
|
snapcraft (launchpad) issue #1760583 |
Text not being displayed in PyQt app | ~subins2000 | 3133d | close not a bug | 18 | 30 | 5 | Reporter's PyQt5 app snap (TorrentBro) shows no text; they ask whether host fonts must be bundled. A user packaging/support question with no snapcraft-side defect, no maintainer reply since 2018. |
|
snapcraft (launchpad) issue #1829819 |
Wrong package source list | ~holger-seelig | 2719d | close not a bug | 18 | 32 | 5 | User (Feb 2019, snapcraft 3.4.1) asks how to build a core18 snap using host 19.04 Disco apt sources instead of the default bionic build VM. Usage question, no maintainer reply; documented answer is --destructive-mode. |
|
snapcraft (launchpad) issue #1803235 |
signup process does not send activation email | ~lhonda | 2907d | close not a bug | 18 | 20 | 1 | Launchpad bug: forum.snapcraft.io Discourse signup didn't deliver activation email to Gmail. pjdc traced it to Gmail rejecting forum mail (infra cRT#115397); reporter later confirmed the resent link worked. Not a snapcraft codebase defect. |
|
snapcraft (launchpad) issue #1921950 |
Can't build simple snap, maybe because of missing kmod arp_tables | ~paddor | 2039d | close not a bug | 15 | 25 | 3 | New-user confusion: `snapcraft build` only runs the part build step, so no .snap appears; maintainer explained the pull/build/stage/prime + snap workflow and suggested better help text |
|
snapcraft (launchpad) issue #1853540 |
Snap package shows as registered but unable to publish | ~gabeduke | 2534d | close not a bug | 15 | 15 | 2 | User reports kubectl-iexec snap name appears registered on their account but `snapcraft push` returns the store error 'You are not the publisher or allowed to push revisions'. The pasted `list-registered` output actually omits kubectl-iexec, and no snapcraft code path produces this message. |
|
snapcraft (launchpad) issue #1983826 |
Snapcraft 7.1.1 gives vague error when it can't process package | ~koen-vervloesem | 1544d | close not a bug | 15 | 20 | 2 | Vague 'Service unavailable' on snapcraft upload. The text originates from the store's processing pipeline, not Snapcraft; Snapcraft already relays store error messages verbatim. Self-resolved for the reporter after `snapcraft clean`; root cause never diagnosed. |
|
rockcraft issue #882 |
fastapi-framework extension cannot detect 'prime' entry from rockcraft.yaml | lego37yoon | 537d | close not a bug | 15 | 30 | 4 | User's rockcraft.yaml used prime entries without the app/ prefix; fastapi-framework requires all entries start with app/. Maintainer explained the correct YAML and asked for confirmation; reporter never replied. |
|
snapcraft (launchpad) issue #1638622 |
dump plugin cannot copy a single file | ~jamesj | 3649d | close not a bug | 15 | 92 | 13 | Single-file copying is supported by dump through core organize and snap options; only a proposed dump-help documentation example remains unfulfilled. |
|
snapcraft (launchpad) issue #1673658 |
python package failed to install because of directories in the source | ~thomir-deactivatedaccount | 3514d | close not a bug | 15 | 40 | 4 | 2017 report that python plugin stopped staging scripts after 2.27.1; reporter found stale build/, dist/, egg-info/ and ve3/ in the source dir caused it. Maintainer: 'not a regression', suggested maybe warning instead. |
|
snapcraft (launchpad) issue #1826741 |
No OpenHAB-ondra Bluetooth (BlueZ) access | ~martin-hagborg | 2742d | close not a bug | 12 | 18 | 2 | openHAB snap on Ubuntu Core 18/RPi3B cannot init BlueZ (HANDLER_INITIALIZING_ERROR); reporter asks how to grant Bluetooth group/plug access. Support question about a third-party snap manifest, untriaged. |
|
fetch-service issue #282 |
ANNOUNCEMENT: SNAP CHANNELS | lengau | 732d | close not a bug | 10 | 15 | 1 | Maintainer announcement mapping branches to snap channels: main publishes to edge, while the feature/launchpad-integration branch was merged into main and retired. Informational only; no code change outstanding. |
|
snapcraft (launchpad) issue #1772885 |
dropping privs did not work: No data available | ~edo.red | 3082d | close not a bug | 8 | 15 | 1 | User asks for help with `sudo lxd init` failing with 'dropping privs did not work: no data available' while setting up Snapcraft — an LXD/host environment support question, not a Snapcraft defect; no labels, no replies. |
|
rockcraft issue #401 |
where does the python3 symlink come from? | cjdcordeiro | 1092d | close not a bug | 5 | 91 | 4 | An open report finds python3 with python3.8-venv but not direct python3.8; venv's extra wheel dependencies pull python3-minimal, which owns the symlink, so the difference is expected. |
|
snapcraft (launchpad) issue #2072436 |
sudo snap install snapd, error: cannot communicate with server: Post... | ~lad203 | 845d | close not a bug | 5 | 15 | 1 | User support request: snapd installed via apt on a Raspberry Pi Zero W fails to start, so `snap install snapd` reports `dial unix /run/snapd.socket: connection refused`. No Snapcraft involvement; unlabelled and untriaged. |
|
snapcraft (launchpad) issue #2138729 |
[Not a Bug] Need info for xvfb / headless-display access | ~t-a-k | 283d | close not a bug | 5 | 15 | 1 | Support request (explicitly '[Not a Bug]'): author wants guidance running Xvfb/headless display for Chromium+Selenium in a snap; hit a store security-review alert and got no forum reply. No snapcraft defect reported. |