Issue & PR triage
Loading...
Showing 100 of 597 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1711333 |
snaps must have accompanying source available | ~jr | 3360d | keep open | 74 | 57 | 7 | Maintainer-acknowledged request to persist and publish snap source and build assets for license compliance remains open, with no implementation found. |
|
snapcraft (launchpad) issue #1933224 |
Recent changes completely break 32bit snaps | ~ogra | 1955d | keep open | 72 | 76 | 23 | Base-snap library filtering omits armhf runtime libraries from armhf/arm64 snaps, silently producing broken Raspberry Pi releases; maintainers acknowledge the bug, but no fix is recorded. |
|
snapcraft (launchpad) issue #2015091 |
snapcraft download debian package from incorrect arch | ~aristochen | 1305d | needs triage | 68 | 85 | 21 | Cross-building for arm64 on amd64 resolved explicitly qualified bsdmainutils:arm64 to an amd64 package; the valid report remains untriaged and a similar bug is still open. |
|
snapcraft (launchpad) issue #2099923 |
Snapcraft builds are failing: install of snap "snapcraft" failed | ~snawoot | 612d | needs triage | 68 | 76 | 19 | Reported Launchpad Bionic non-i386 builds cannot install Snapcraft 7.x/stable because core20 needs snapd 2.61; the issue remains open, untriaged, and unanswered. |
|
snapcraft (launchpad) issue #2041182 |
Desktop extension doesn't update GDK pixbuf module cache when reverting | ~gbeuzeboc | 1099d | keep open | 68 | 86 | 42 | Desktop extensions keep a revision-specific .last_revision while sharing its GDK pixbuf cache, so snap reverts can reuse loaders from another revision and crash; the maintainer-approved move is not implemented. |
|
snapcraft (launchpad) issue #2036424 |
Mantic s390x install fails: grep-status: *** stack smashing detected ***: terminated | ~dbungert | 1137d | keep open | 66 | 72 | 17 | Snapcraft-built Subiquity on Mantic s390x had a missing ELF RPATH, mixing core22's loader with host glibc. Edge core22 worked, but stable core22 still failed on LPAR; the issue remains open. |
|
snapcraft (launchpad) issue #1582469 |
clean behavior is confusing | ~niemeyer | 3818d | needs triage | 65 | 58 | 8 | The 2016 clean/redo UX proposal remains open; modern Snapcraft still exposes clean, while the requested un/re commands are absent from the current command set. |
|
snapcraft (launchpad) issue #1887096 |
not able to install MAAS from snap on ppc64le | ~jhusakowski | 2303d | keep open | 65 | 85 | 23 | MAAS snap installs segfault on ppc64le in older and stable releases because of libsnapcraft-preload; 3.3/edge installs successfully, but stable-channel resolution remains unconfirmed. |
|
snapcraft (launchpad) issue #1882535 |
[focal/core20][python3.7+] staging conflicts when multiple python parts have... | ~dmitriis | 2334d | keep open | 65 | 65 | 11 | Overlapping Python dependencies generate nondeterministic bytecode, RECORD, and venv artifacts that block staging; confirmed to affect multiple users, with workarounds but no complete fix. |
|
snapcraft (launchpad) issue #1670388 |
classic snap are missing some env variables for reaching command name. (snap... | ~didrocks | 3524d | needs triage | 65 | 75 | 32 | Classic snap wrappers omit snap-local PATH entries, so commands such as chuck-norris-cli can pass packaging but fail at runtime; the confirmed report remains open. |
|
snapcraft (launchpad) issue #1764100 |
pyqt5 cannot load xcb plugin | ~ihaywood3 | 3119d | needs triage | 65 | 62 | 15 | PyQt5 snap aborts because libQt5XcbQpa.so.5 has an undefined QPlatformTheme::fileIconPixmap symbol; the report has no labels or maintainer comments. |
|
snapcraft (launchpad) issue #2012503 |
wrong arch of stage packages | ~ondrak | 1317d | keep open | 64 | 88 | 27 | Confirmed cross-build stage packages are fetched for amd64 instead of arm64; no fix or verification is recorded, so the valid cross-compilation bug remains open. |
|
snapcraft (launchpad) issue #1824473 |
Changed stage-snaps property does not make pull step dirty | ~brlin | 2757d | needs triage | 62 | 78 | 35 | No response or triage is present. Current craft-parts still omits stage-snaps from PullState.properties_of_interest, matching the reported stale-step and build crash. |
|
snapcraft (launchpad) issue #1750527 |
dashboard does not validate text fields | ~chipaca | 3173d | close resolved | 62 | 88 | 23 | Dashboard/store control-character validation was implemented in 2018, and the remaining snapd safe-display path was confirmed fixed in 2020; the Launchpad issue remains open. |
|
snapcraft (launchpad) issue #1813634 |
not reliable way to detect target architecture | ~ondrak | 2831d | close resolved | 62 | 90 | 29 | Snapcraft 8.0.0 added explicit build-for architecture variables, superseding the ambiguous 3.0.1-era target_arch and SNAPCRAFT_ARCH_TRIPLET behavior. |
|
snapcraft (launchpad) issue #1834207 |
removing parts should clean stage and prime… stages? | ~saviq | 2683d | keep open | 62 | 88 | 31 | Removing a part leaves its prior files in stage/prime and packages them; the report has a clear reproducer and maintainer confirmation, but no fix reference is recorded. |
|
snapcraft (launchpad) issue #1995424 |
A way to get debug symbols | ~ilya-fedin | 1457d | keep open | 60 | 45 | 4 | Requests debug-symbol distribution for diagnosing snap crashes; maintainer reports active design work, while uploadable components offer a partial path but are documented as not production ready. |
|
snapcraft (launchpad) issue #1896820 |
Snapcraft can't be run against a local or remote LXD project | ~stgraber | 2227d | needs triage | 60 | 55 | 9 | Support user-selected local and remote LXD projects is still pending; Snapcraft hard-codes its own local LXD project, while remote-instance work is tracked separately. |
|
snapcraft (launchpad) issue #2015370 |
Undefined Symbol Error While trying to launch Application from a snap... | ~ameya-v-singh | 1303d | needs triage | 58 | 44 | 7 | 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. |
|
snapcraft (launchpad) issue #1965814 |
snap contains python 3.8 and 3.9 libs | ~kenneth-loafman | 1683d | keep open | 58 | 45 | 8 | A core20 build staged Python 3.8 and 3.9 files; Duplicity added a packaging workaround, but the underlying Snapcraft conflict and potential side effects remain unresolved. |
|
snapcraft (launchpad) issue #1836206 |
snapped app with qtwebengine fails to run | ~teoretyk | 2667d | needs triage | 58 | 49 | 7 | QtWebEngine apps abort at startup: the helper and resources are initially missing, and after a bind-mount workaround Chromium still fails in DenySetgroups. The report remains untriaged. |
|
snapcraft (launchpad) issue #1566331 |
snapcraft autotools plugin doesn't support building other architectures | ~cmiller | 3859d | close resolved | 58 | 88 | 27 | Autotools cross-compilation is now supported through target build-for selection, CRAFT_ARCH_TRIPLET_BUILD_FOR, and --host configuration; the historical request has been implemented. |
|
snapcraft (launchpad) issue #1673186 |
the gox classic snap gets stuck consuming a lot of cpu | ~zyga | 3515d | close resolved | 58 | 92 | 28 | Classic snap wrappers could resolve their own /snap/bin launcher and spin in an exec/fork loop. Snapcraft later added a classic-PATH workaround in #2889, resolving the report. |
|
snapcraft (launchpad) issue #1908061 |
gnome-3-34 extension is missing libraries | ~christianrauch | 2145d | keep open | 58 | 69 | 10 | GNOME 3.34 extension users can get startup crashes when staged HarfBuzz, GLib, or GIO libraries shadow the content snap; the cause and deletion workaround are known, but no general conflict detection fix is identified. |
|
snapcraft (launchpad) issue #1921397 |
Cant build snaps with snapcraft when snap store is down | ~bugraaydogar | 2044d | keep open | 58 | 61 | 12 | Reported Snap Store outages can block builds; maintainers identified refresh, base, extension, injection, and default-provider paths, but no complete fix or current reproducer is documented. |
|
snapcraft (launchpad) issue #1999321 |
Snapcraft is stuck on "launching instance..." indefinitely | ~mjakeman | 1418d | close resolved | 58 | 92 | 30 | Endless LXD startup on failed container DNS now times out via craft-providers; Snapcraft 7.5.4 is recorded as fixing the wait. Multipass arm64 and Docker diagnostics remain separately tracked. |
|
snapcraft (launchpad) issue #2065801 |
Snapcraft hangs with no space left on device | ~nteodosio | 897d | needs triage | 58 | 48 | 10 | Reported in June 2024: an ENOSPC during a large Chromium build could leave the builder hanging instead of returning control; the cause remains untriaged. |
|
snapcraft (launchpad) issue #1835638 |
inconsistent to arch behaviour | ~ondrak | 2672d | needs triage | 58 | 70 | 13 | Snapcraft 3.6 advanced grammar can omit stage-packages on native builds and mix host/target packages in nested on/to cases; the old report remains open and untriaged. |
|
snapcraft (launchpad) issue #1885074 |
stage-packages behaviour inconsistent | ~ondrak | 2317d | needs triage | 58 | 64 | 18 | Snapcraft 4.0.7 reportedly creates an empty core18 arm64 snap when stage-packages use :arm64 suffixes natively, while cross-compilation succeeds; no triage or resolution is recorded. |
|
snapcraft (launchpad) issue #1681861 |
classic snaps recurse | ~chris.macnaughton | 3488d | close resolved | 58 | 86 | 38 | Classic PATH recursion was addressed by commit 343ac2862, which added the snapcraft-runner workaround; current metadata tests still expect that runner in command chains. |
|
snapcraft (launchpad) issue #1893262 |
pygtk apps fail with gnome-3-34 extension | ~ken-vandine | 2254d | keep open | 58 | 82 | 26 | Python GTK apps using GNOME extensions still fail in core20/core22 because runtime Python module paths remain incompatible; a minimal reproducer is provided despite an earlier PYTHONPATH fix attempt. |
|
snapcraft (launchpad) issue #1684225 |
retry store actions when it returns a 503 error | ~elopio | 3480d | keep open | 58 | 72 | 20 | Maintainer-requested resilience for temporary Store 503 responses remains open: all store commands should retry with backoff, but current request handling has no 503-specific retry path. |
|
snapcraft (launchpad) issue #1998269 |
Gnome extension breaks fontconfig for some applications | ~zoopgoop | 1430d | needs triage | 58 | 64 | 14 | Untriaged GNOME-extension fontconfig failures block Wine initialization and Steam UI fonts; a minimal reproducer and FONTCONFIG_FILE workaround exist, but root cause and current impact remain unverified. |
|
snapcraft (launchpad) issue #2161192 |
python plugin not working at all with snapcraft 9+ | ~t-a-k | 103d | close resolved | 58 | 67 | 23 | Core26 Python plugin builds and module loading were fixed; packaging Python separately is now documented as required by the base. |
|
snapcraft (launchpad) issue #1804845 |
Applications requiring UTF-8 fail | ~merlijn-sebrechts | 2897d | needs triage | 58 | 57 | 13 | UTF-8-dependent packaged apps can fail because host locales are unavailable; no generic fallback is visible, and the open report remains untriaged despite documented workarounds. |
|
snapcraft (launchpad) issue #1913599 |
remote-build always recovers, even when --recover is not specified | ~nymea | 2100d | close resolved | 58 | 92 | 37 | remote-build recovery is now opt-in: interrupted builds are resumed only with --recover, addressing the reported automation and artifact-provenance risk. |
|
snapcraft (launchpad) issue #1921418 |
wrong architecture of stage-snaps when cross building | ~ondrak | 2044d | keep open | 58 | 87 | 26 | Cross-building downloads host-architecture stage-snaps instead of build-for artifacts; the acknowledged craft-415 bug appears unresolved in current craft-parts. |
|
snapcraft (launchpad) issue #1759740 |
Library discovery for rpath patching needs to be deterministic | ~kyrofa | 3136d | keep open | 58 | 90 | 23 | RPATH patching still resolves duplicate SONAMEs with an unsorted os.walk, so Snapcraft may choose a library contrary to ld precedence; this maintainer-authored issue remains open. |
|
snapcraft (launchpad) issue #1859046 |
Allow Custom Build Certificate Authority And Proxy Credentials | ~zicklag | 2485d | close resolved | 58 | 96 | 31 | LXD build proxy and custom CA support was implemented through proxy CLI/provider plumbing and an option for installing custom CA certificates in build environments. |
|
snapcraft (launchpad) issue #1917919 |
snapcraft validate (and possibly other operations requiring gpg passphrases)... | ~roadmr | 2064d | keep open | 58 | 76 | 26 | GPG-backed assertion signing can fail on headless systems because no terminal is passed to gpg-agent; exporting GPG_TTY=$(tty) is reported to fix it |
|
snapcraft (launchpad) issue #1576282 |
Snaps built from deb can't be gettext translated | ~seb128 | 3836d | close resolved | 58 | 87 | 24 | Deb-built snap gettext localization was historically blocked by missing locale data and hard-coded /usr paths; current desktop integration sets LOCPATH and redirects bindtextdomain to snap locale directories. |
|
snapcraft (launchpad) issue #2073910 |
snapcraft cannot connect through a transparent SSL proxy | ~rudratrivedi | 828d | needs triage | 58 | 78 | 22 | Snapcraft 7.5.5/8.3.1 rejects a system-trusted MITM proxy CA; setting REQUESTS_CA_BUNDLE works, but the report remains untriaged. |
|
snapcraft (launchpad) issue #1918999 |
stage-packages for classic snaps silently drop core20 snap debs | ~racb | 2057d | keep open | 58 | 78 | 25 | Classic snaps using stage-packages lose dependencies already present in core20 because base-package filtering silently omits them; a bare-base workaround exists, but the underlying filtering bug remains open. |
|
snapcraft (launchpad) issue #2012504 |
PATH auto extended with stage paths | ~ondrak | 1317d | keep open | 58 | 76 | 25 | Cross-builds can prepend target-architecture staged binaries to a part's build PATH, executing tools such as Python from the wrong architecture. Maintainers acknowledged the defect, which remains open. |
|
snapcraft (launchpad) issue #1987853 |
snapcraft terminates override-build script prematurely without error | ~nicolasbock | 1525d | needs triage | 57 | 81 | 24 | override-build silently skips trailing commands when a build tool consumes stdin on core20+, but piping a separate stdin stream works around it; the underlying failure remains untriaged. |
|
snapcraft (launchpad) issue #1999385 |
Removing a `package-repositories:` entry does not affect existing containers | ~saviq | 1417d | needs triage | 57 | 69 | 17 | Removing a package-repositories entry leaves its APT source in reused build containers, risking unintended package resolution. The report remains open, untriaged, and uncommented; no resolving change was found. |
|
snapcraft (launchpad) issue #2025447 |
Incorrect Downloads directory for LDAP user in snapped firefox & chromium | ~dgadomski | 1217d | keep open | 56 | 91 | 38 | LDAP/AD users' Firefox and Chromium snaps download into snap data instead of ~/Downloads; reproduced on 22.04, confirmed for multiple users, and a SNAP_REAL_HOME fix was validated. |
|
snapcraft (launchpad) issue #1889741 |
Snapcraft concurrent build | ~lawrencegripper | 2281d | keep open | 56 | 84 | 23 | Concurrent first-time builds can race during pyxdg cache-path creation; the flaw was still reported on Snapcraft 8.2.12 despite a 2022 upstream fix attempt. |
|
snapcraft (launchpad) issue #2031494 |
snapcraft login doens't work on fresh multipass or lxd | ~gbeuzeboc | 1170d | close resolved | 56 | 95 | 29 | Snapcraft 7.5.2 could not log in on fresh Multipass/LXD systems without a usable keyring; Snapcraft 8.0.0 added file-based credential fallback. |
|
snapcraft (launchpad) issue #1995293 |
no uid/gid mappings when building on core22 with multipass | ~andreitoterman | 1459d | keep open | 55 | 88 | 30 | Reproduced Multipass/core22 builds leave /root/project owned by ubuntu:ubuntu instead of root:root; the unset mapping was traced to craft-providers. |
|
snapcraft (launchpad) issue #1862516 |
Missing items in LD_LIBRARY_PATH break numpy stage-packages | ~aglavic | 2454d | needs triage | 55 | 70 | 16 | Numpy staged via stage-packages fails at runtime because libblas.so.3 and liblapack.so.3 sit in nested blas/lapack directories outside the library search path; the old issue is untriaged. |
|
snapcraft (launchpad) issue #2147036 |
Lots of noise produced at the end of build | ~nteodosio | 211d | needs triage | 55 | 65 | 20 | A failed snapcraft --debug build prints a huge escaped duplicate of its output before opening a shell, obscuring the error; the issue remains open and untriaged. |
|
snapcraft (launchpad) issue #1744608 |
customize snapcraft environment based on architecture. | ~bsutton | 3203d | keep open | 55 | 68 | 17 | Architecture-conditional grammar remains unsupported for app and top-level environment variables; current models accept plain dictionaries, while grammar processing covers only selected part keys. |
|
snapcraft (launchpad) issue #2012074 |
snapcraft cannot build snap by default on aarch64 | ~gbeuzeboc | 1322d | close resolved | 55 | 92 | 30 | ARM64 default builds failed on Snapcraft 7.3.1 because core20 selected amd64-only Multipass images; later defaults use core22/LXD on Linux, addressing the reported path. |
|
snapcraft (launchpad) issue #1996206 |
Linter is checking against host libs when using --build-for argument | ~dbruno74 | 1449d | needs triage | 55 | 70 | 13 | Cross-architecture builds may lint arm64 libraries against x86_64 core22 paths; the report remains open, unlabelled, and untriaged without a confirmed fix. |
|
snapcraft (launchpad) issue #1823308 |
automatically inject dbus slot & use it | ~apachelogger | 2764d | needs triage | 55 | 68 | 17 | Requests automatic D-Bus slot injection from desktop metadata, including X-DBUS-ServiceName; it remains open and untriaged, with current common-id and explicit bus-name support not covering the requested inference. |
|
snapcraft (launchpad) issue #1807125 |
After snapcraft refresh, old multipass containers no longer work | ~igorljubuncic-deactivatedaccount | 2884d | needs triage | 55 | 63 | 14 | Snapcraft 3.0.1 could reuse incompatible Multipass VMs after a 3.0.0 refresh, causing a misleading missing-project error until snapcraft clean; the report is untriaged. |
|
snapcraft (launchpad) issue #1964329 |
meson plugin uses internet access during build, instead of pull | ~xnox | 1695d | close resolved | 55 | 58 | 22 | Legacy Meson plugin installed its build dependency with pip during build, blocking offline riscv builds; the legacy plugin is now absent and the active plugin only runs meson and ninja. |
|
snapcraft (launchpad) issue #1842376 |
No standard way of specifying memory requirements for multipass build VMs | ~dmitriis | 2613d | needs triage | 55 | 74 | 15 | Open, unlabelled request for a project-level Multipass RAM setting: Go builds are OOM-killed at the documented 2 GiB default, while only an environment-variable override is available. |
|
snapcraft (launchpad) issue #1670323 |
binary entry (and lib) for python projects not installed in final snap | ~didrocks | 3524d | close resolved | 55 | 88 | 28 | A 2017 Python-plugin wheel regression omitted setup.py scripts and libraries when the project name matched a requirement; later wheel/install-ordering work appears to fix it. |
|
snapcraft (launchpad) issue #1856594 |
Snapcraft tutorial errors out on OSX with multipass error, "returned exit code 2" | ~dobsorg | 2509d | keep open | 55 | 62 | 13 | macOS Multipass bootstrap hits apt 404s and then mount failures, blocking the tutorial; the host-side CPU-affinity crash has a fallback, but the primary failure remains unconfirmed. |
|
snapcraft (launchpad) issue #1774410 |
Having python3-netaddr as a stage package produces external symlink | ~bjornt | 3073d | close resolved | 55 | 72 | 27 | Snapcraft 2.42 could leave python3-netaddr stage-package symlinks pointing outside the snap; later normalization and regression fixes now rewrite them internally. |
|
snapcraft (launchpad) issue #1965113 |
Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used | ~osomon | 1688d | keep open | 55 | 70 | 23 | Desktop snaps fail to launch ("cannot open display") in Xorg sessions after a Wayland session was used, because desktop-exports detects Wayland by a leftover socket. Root cause identified; workaround DISABLE_WAYLAND=1; still open. |
|
snapcraft (launchpad) issue #1735410 |
Localization support | ~mkljczk | 3255d | keep open | 55 | 48 | 8 | Localization of Snapcraft's user-facing text remains unimplemented; the 2017 request is labeled bitesize/l10n but still lacks scope and detailed acceptance criteria. |
|
snapcraft (launchpad) issue #1746403 |
snapcraft fails to find hooks if ran from snap directory. | ~bsutton | 3193d | keep open | 55 | 82 | 22 | Running Snapcraft from snap/ can misidentify the assets directory as the project root and omit adjacent hooks; PR #3379 adds a warning, but lookup remains order-based. |
|
snapcraft (launchpad) issue #1646546 |
snapcraft packages .so from /usr instead of from .deb | ~aacid | 3619d | keep open | 55 | 62 | 16 | Snapcraft's prime step can replace a staged .deb library with a different host /usr .so; a maintainer reproduced the stage/prime mismatch, but no resolution is recorded. |
|
snapcraft (launchpad) issue #1681152 |
snap may execute host, not wrapped, executables | ~cgull | 3491d | needs triage | 55 | 60 | 21 | Classic snap wrappers may execute host binaries instead of snap payloads; a concrete mosh reproducer exists, but no triage followed and later PATH-related work may apply. |
|
snapcraft (launchpad) issue #1712808 |
udev interface fails in privileged containers | ~saviq | 3353d | close resolved | 55 | 70 | 23 | Long-standing bug: snap installs in privileged LXD/LXC containers fail with "cannot reload udev rules". Fixed upstream by snapd PR 14930 and SRU'd as snapd 2.68.5 to jammy/noble/plucky; jammy verification still pending. |
|
snapcraft (launchpad) issue #1663051 |
Stage package cache is never cleaned | ~kyrofa | 3550d | keep open | 55 | 68 | 19 | Open, triaged cache-growth bug: source-hash-specific stage-package caches grow without cleanup; maintainers proposed an apt-get clean-style reset, but no clearing command or fix is evident in the current tree. |
|
snapcraft (launchpad) issue #2158702 |
Snapcraft API not answering | ~t-a-k | 121d | needs triage | 55 | 45 | 10 | api.snapcraft.io v2/snaps/info intermittently returns HTTP 200 with no parsable version (~70% failures), breaking version detection in GitHub remote builds; unlabelled, no maintainer reply, awaiting triage on the store API side |
|
snapcraft (launchpad) issue #1795827 |
Snapcraft doesn't install snapcraft inside the lxd container | ~saviq | 2948d | close resolved | 55 | 84 | 22 | Historical LXD builds failed because Snapcraft was not injected into the container; the modern Craft Providers LXD path injects Snapcraft and resolves the legacy failure. |
|
snapcraft (launchpad) issue #2008502 |
mishandled private git+ssh repo url | ~ondrak | 1343d | keep open | 55 | 65 | 21 | Launchpad git+ssh URL mangling was fixed in craft-parts 1.19.1, but the confirmed open request now targets an unimplemented warning for git:// sources rejected by Launchpad builders. |
|
snapcraft (launchpad) issue #1833220 |
stage-snaps not usable with a brand store | ~anonymouse67 | 2690d | keep open | 55 | 78 | 13 | Brand-store credentials do not work for stage-snaps/build-snaps in LXD or Multipass; host builds work with absolute credentials, but no resolution is recorded. |
|
snapcraft (launchpad) issue #1919397 |
snapcraft doesn't run store checks locally, causing disappointment at upload time | ~racb | 2053d | keep open | 55 | 74 | 15 | Bundled local store validation remains unimplemented; merged PR #2783 only added optional upload-time warnings when review-tools is already installed. |
|
snapcraft (launchpad) issue #1688703 |
Enable optimizations by default | ~eyelash | 3463d | keep open | 55 | 72 | 22 | Optimized defaults remain inconsistent: current craft-parts docs still require explicit release settings for CMake and Meson, while Colcon now defaults to Release. |
|
snapcraft (launchpad) issue #1602258 |
Support other distributions as sources (Fedora, Mageia, openSUSE, Debian)... | ~ngompa13 | 3761d | keep open | 54 | 67 | 4 | Confirmed RFE remains open: source abstraction exists, but RPM/DNF package resolution, matching distro build environments, and non-Ubuntu source selection remain unimplemented. |
|
snapcraft (launchpad) issue #2080610 |
Library linter should still consider ignored files for dependencies | ~saviq | 776d | keep open | 52 | 66 | 10 | Library linter skips ignored (dlopen'ed) ELF files before computing dependencies, so their dependencies get falsely flagged unused; maintainer acknowledged the need for a dependency-graph refactor, still unimplemented. |
|
snapcraft (launchpad) issue #2061517 |
`remote-build` lacks support for selecting Snapcraft channel | ~saviq | 927d | keep open | 52 | 82 | 21 | remote-build still cannot select or mirror the local Snapcraft channel; valid upstream-dependent feature work remains open, with a GitHub implementation issue tracking it. |
|
snapcraft (launchpad) issue #2007480 |
The 'url' of 'package-repositories' can't handle PPA token from the... | ~laiderlai | 1351d | needs triage | 52 | 82 | 19 | Untriaged request to expand environment variables in APT repository URLs so private PPA credentials can stay out of snapcraft.yaml; no maintainer response. |
|
snapcraft (launchpad) issue #2017587 |
SNAP_REAL_HOME causes problem | ~soumyadghosh | 1284d | keep open | 52 | 45 | 8 | Setting HOME=$SNAP_REAL_HOME reportedly makes empty user folders unusable; use cases are documented, but the open report lacks a minimal reproducer and has no identified fix. |
|
snapcraft (launchpad) issue #2002538 |
override-prime ignore failure on rebuild | ~gbeuzeboc | 1387d | needs triage | 52 | 86 | 26 | A failed override-prime step is cached as complete, letting a second build skip priming and package the snap; an exact old-version reproducer is provided, but the report remains untriaged. |
|
snapcraft (launchpad) issue #1654304 |
Allow pinning a source archive | ~mterry | 3584d | close resolved | 52 | 86 | 23 | APT pinning for the Ubuntu Touch overlay is now implemented via package-repositories priority, with craft-archives writing preferences and spread tests covering a PPA; this old request is resolved. |
|
snapcraft (launchpad) issue #1737561 |
stage-packages do not honor --target-arch | ~lool | 3244d | keep open | 52 | 78 | 29 | Cross-builds still fetch stage-packages for the host architecture; current craft-parts passes step_info.host_arch instead of the requested target architecture. |
|
snapcraft (launchpad) issue #1802327 |
cannot use build snaps that are marked private in the store | ~apachelogger | 2912d | keep open | 52 | 82 | 18 | Private or separate-store build snaps remain unavailable through build-snaps/stage-snaps despite working snap installs; the open issue remains valid with no identified fix. |
|
snapcraft (launchpad) issue #2044389 |
snapcraft clean failed but exit 0 | ~moisesperezespinosa | 1071d | keep open | 52 | 90 | 31 | Snapcraft 7.5.3 reports a missing build environment during clean but exits 0; a maintainer confirmed the bug and agreed it should fail, with no fix recorded. |
|
snapcraft (launchpad) issue #2011842 |
Incorrect default LD_LIBRARY_PATH | ~saviq | 1323d | keep open | 52 | 76 | 12 | Core22+ Snapcraft emits unsupported shell expansion for LD_LIBRARY_PATH; the behavior is reproduced and remains blocked on snapd environment-list support. |
|
snapcraft (launchpad) issue #1904212 |
ValueError: No revision information for 1 | ~popey | 2176d | keep open | 52 | 79 | 18 | Open report of a Store channel-map race that makes snapcraft upload --release fail after the revision was created; maintainers confirmed it and users reproduced it through Snapcraft 5.0. |
|
snapcraft (launchpad) issue #1753995 |
patchelf warning / binary segfaults | ~sajoupa | 3158d | keep open | 52 | 57 | 12 | PatchELF corrupted Go-built Telegraf classic snaps into runtime segfaults; no-patchelf avoided the crash, but a 2019 Snapcraft 3.8 reproduction remains unverified on current code. |
|
snapcraft (launchpad) issue #1790004 |
Snapcraft should warn if it produces a snap that the store will reject | ~ej-finneran | 2982d | needs triage | 52 | 62 | 12 | Requests local warnings for Snap Store rejection conditions. The reported permission failure is concrete, but mode validation is absent from current linters and broader local store-check work remains open. |
|
snapcraft (launchpad) issue #1989012 |
package-repositories assumes architecture | ~ondrak | 1513d | needs triage | 52 | 82 | 26 | Snapcraft 7.1.3 injects Architectures: arm64 into an APT source when package-repositories omits architectures; the report is old, untriaged, and may be superseded by later craft-archives handling. |
|
snapcraft (launchpad) issue #2013242 |
Do not allow two different apps to have the same autostart-desktop file | ~3v1n0 | 1310d | needs triage | 52 | 84 | 33 | Requests validation preventing different apps from sharing an autostart .desktop file; current Snapcraft only validates each filename's format, leaving the conflict undetected. |
|
snapcraft (launchpad) issue #2075493 |
`plugin: meson` no longer functional for Rust on `base:` < `core22` "Could... | ~saviq | 819d | keep open | 52 | 76 | 15 | Meson-based Rust builds on core20 fail after Meson 1.5 requires a TOML parser. Maintainers accepted the scenario and chose archive-installed build tools, but no implementation or resolution is recorded. |
|
snapcraft (launchpad) issue #1790346 |
store review fails on "unknown keys in snap/manifest.yaml: snapcraft..." | ~saviq | 2979d | close resolved | 52 | 87 | 34 | Core18 snap uploads were rejected because generated manifest.yaml contained unsupported snapcraft-* keys; later review-tools compatibility coverage indicates the problem was addressed. |
|
snapcraft (launchpad) issue #2018456 |
Lack of support for ssh agent | ~suligap | 1274d | keep open | 52 | 63 | 12 | SSH pulls in core22 LXD builds hang on hidden interactive prompts; --bind-ssh only mounts ~/.ssh and never forwards SSH_AUTH_SOCK. Reproduced by maintainer, feature request still unimplemented. |
|
snapcraft (launchpad) issue #1861026 |
python3 ctypes can't find libs on due to ld cache | ~jdstrand | 2467d | close resolved | 52 | 82 | 11 | UC strict snaps let ctypes resolve bundled libraries through the host ldconfig cache; commit 786d0b8eab91c3be850f07195b4cd2c52dbdfbf7 is recorded as a workaround. |
|
snapcraft (launchpad) issue #2011993 |
override-build exits prematurely, part build succeeds | ~awe | 1323d | needs triage | 50 | 60 | 10 | Snapcraft 7.x may mark an override-build successful after flutter-elinux exits early, deferring failure until packing reports bin/workshops missing; the cause remains unresolved and untriaged. |
|
snapcraft (launchpad) issue #2050860 |
remote-build `version: git` resolved too late | ~saviq | 1010d | keep open | 50 | 68 | 15 | Remote-build preserves clean Git history, but auto-commits dirty trees before resolving version: git, yielding a different SHA-dirty version; warning versus pre-resolution remains undecided. |
|
snapcraft (launchpad) issue #1668555 |
Using organize to move a folder to a child folder fails due to recursion | ~jamesh | 3530d | close resolved | 50 | 94 | 29 | The historical organize recursion is addressed by self-move protection; organize now runs during build, resolving both reported behaviors in current code. |
|
snapcraft (launchpad) issue #1979269 |
core22 build just hangs if lxd has no network connectivity | ~peterpall | 1591d | needs triage | 50 | 64 | 18 | Core22 managed builds can stall indefinitely at LXD instance launch without usable host networking; the untriaged report requests a timeout or clearer failure feedback. |
|
snapcraft (launchpad) issue #1743587 |
snapcraft push returns non exit zero code if snap requires manual review | ~serge-borovkov | 3208d | keep open | 50 | 71 | 20 | Manual-review status is printed during upload but is not raised as an error, so automation can treat an unreleased revision as a successful push. |