Issue & PR triage
Loading...
Showing 100 of 213 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #1666639 |
unusual mode 'rwxr-xr-x' for symlink ' | ~joeborg | 3537d | needs triage | 50 | 35 | 5 | A Click Apps build failed with “unusual mode 'rwxr-xr-x' for symlink”; the affected paths, complete logs, and reproduction details were never provided. |
|
snapcraft (launchpad) issue #2161190 |
Rebuild fails because of 'version' can be set only once | ~t-a-k | 103d | needs triage | 50 | 62 | 13 | Incremental Snapcraft packing can fail when override-pull sets version again, requiring snapcraft clean; the report remains unlabelled and unanswered. |
|
snapcraft (launchpad) issue #2002474 |
Snapcraft does not take the environment variables into account during build | ~snorbi | 1387d | needs triage | 48 | 82 | 15 | Snap packaging fails when an app command references an app-defined JAVA_HOME; snap pack reports $JAVA_HOME paths as missing. The report has a YAML reproducer and literal-path workaround, but no labels or maintainer discussion. |
|
snapcraft (launchpad) issue #2139423 |
Error: saving config file for the container failed | ~nteodosio | 272d | needs triage | 48 | 55 | 10 | An existing LXD build container fails to start with a config-save error. Manual start unblocks the build, but the untriaged report lacks diagnostics needed to identify the cause. |
|
snapcraft (launchpad) issue #1992213 |
Snapcraft crashes when the APT unprivileged user owns the host's source list... | ~brlin | 1482d | needs triage | 48 | 68 | 15 | Snapcraft 8187 crashed opening a 0600 _apt-owned APT metadata file. The legacy LXD path was removed, but equivalent current apt-cache checks still need review. |
|
snapcraft (launchpad) issue #2052798 |
snapcraft overwrites log file names on error | ~popey | 993d | needs triage | 48 | 77 | 20 | Failure logs are overwritten by subsequent status messages because error paths lack line breaks, truncating the CMake log path. The valid report is reproducible but has not been triaged. |
|
snapcraft (launchpad) issue #1947914 |
concurrent snapcraft builds with multipass provider | ~geekorous | 1835d | needs triage | 48 | 55 | 10 | Snapcraft 5/Core 18 Multipass builds reportedly shared 10.30.202.6 and terminated silently; the old report has no maintainer assessment and needs triage against current versions. |
|
snapcraft (launchpad) issue #1995895 |
Cannot override stage | ~jardon | 1452d | needs triage | 48 | 76 | 16 | Snapcraft 7.2.6 fails when override-stage leaves /root/stage/bin missing; the reproducible crash has no labels, maintainer response, or recorded diagnosis. |
|
snapcraft (launchpad) issue #2052928 |
Pulling from private repository without known_hosts hangs forever | ~gbeuzeboc | 990d | needs triage | 48 | 78 | 22 | SSH-based Git source pulls can block indefinitely when the host is absent from known_hosts because the host-key prompt is obscured by pull progress; clear core22 reproducer, no maintainer triage. |
|
snapcraft (launchpad) issue #2028686 |
snapcraft pack failure from git worktree | ~dbungert | 1192d | needs triage | 48 | 67 | 18 | Snapcraft 7.5.0 reportedly cannot pack a source-type: git project from a linked worktree; steps are provided, but the report remains untriaged and lacks failure output. |
|
snapcraft (launchpad) issue #1862666 |
musl libc support | ~cjp256 | 2453d | needs triage | 48 | 57 | 7 | Musl-built parts fail dependency resolution on libc.musl-x86_64.so.1 unless a loader layout is supplied; ELF handling remains GNU/glibc-specific and untriaged. |
|
snapcraft (launchpad) issue #1839885 |
cmake parts build without install target broken after plugin update | ~neasoon | 2635d | needs triage | 48 | 58 | 9 | CMake plugin update removed Make-style artifact customization, breaking projects without an install target; current craft-parts still always invokes target install, but the untriaged issue needs review. |
|
snapcraft (launchpad) issue #1818017 |
Please support custom cloud-init config for Multipass VMs | ~brlin | 2800d | needs triage | 48 | 54 | 8 | Request to merge user cloud-init settings into new Multipass build VMs; remains open, unlabelled, and untriaged, with implementation now likely owned by craft-providers. |
|
snapcraft (launchpad) issue #2017688 |
staging lsb-release in python part make the part fail | ~gbeuzeboc | 1283d | needs triage | 48 | 78 | 18 | Python part venv creation fails in ensurepip when lsb-release is staged or part ordering changes; the cause appears tied to interpreter PATH resolution, but the report remains untriaged. |
|
snapcraft (launchpad) issue #2131202 |
Opera and LossLessCut is no possible open in Wayland | ~maciek-borzecki | 350d | needs triage | 48 | 35 | 4 | Opera and LosslessCut snaps fail to start on Wayland (ENOENT on /run/user/1000/snap.$SNAP/wayland-0). Misfiled to snapcraft but ask is a snapd change; maintainer asked whether it is app-packaging fault, unanswered. |
|
snapcraft (launchpad) issue #1831111 |
Snapcraft strips build ID | ~sophie-w | 2709d | needs triage | 48 | 54 | 8 | Snapcraft may strip GNU build IDs while PatchELF rewrites binaries, reportedly crashing Mesa's i965_dri.so; no-patchelf works around it, but the untriaged report lacks confirmation. |
|
snapcraft (launchpad) issue #2161030 |
linter with gpu-extension not relevant | ~t-a-k | 105d | needs triage | 48 | 58 | 9 | Library linting emits false missing-dependency warnings for libraries supplied through the GPU extension’s Mesa slots; installed-snap linting is also requested. The issue remains untriaged. |
|
snapcraft (launchpad) issue #2127927 |
Allow {stage,build}-snaps and extensions to point to locally provided snaps | ~nteodosio | 379d | needs triage | 48 | 58 | 10 | Feature request to let build-snaps, stage-snaps, and extension dependencies reference local .snap files; support remains Store-only and the issue has not been triaged. |
|
snapcraft (launchpad) issue #1744013 |
snap does not support revocation of signing keys | ~vilvo | 3206d | needs triage | 48 | 64 | 14 | Model assertions can be signed with a local key, but Snapcraft exposes no revocation workflow; after 3,179 days it remains open, unlabeled, and without maintainer input. |
|
snapcraft (launchpad) issue #2017771 |
apt update failure during core22 destructive-mode pulls | ~suligap | 1282d | needs triage | 48 | 68 | 11 | Core22 snapcraft pull --destructive-mode reportedly fails apt update for stage-packages when run non-root; --bind-ssh does not help. The report remains open, untriaged, and without maintainer feedback. |
|
snapcraft (launchpad) issue #1847321 |
Snap with python3 + tkinter crashes with SEGFAULT | ~eikekuehn42 | 2578d | needs triage | 48 | 52 | 9 | Python3 + tkinter snap segfaults when creating a Label; minimal reproducer repo linked, but no diagnosis, no yaml shown, no maintainer response since 2019. Author cross-referenced LP#1709060; another user confirmed similar breakage in a 2020 forum thread. |
|
snapcraft (launchpad) issue #2008558 |
changing cmake-parameters doesn't invalidate part | ~merlijn-sebrechts | 1342d | needs triage | 48 | 72 | 22 | A core20 CMake part remains stale after cmake-parameters changes; no maintainer triage, attached configuration, or resolving change is visible. |
|
snapcraft (launchpad) issue #1681722 |
classic snaps cannot find stage packages in $PATH | ~stub | 3488d | needs triage | 47 | 50 | 8 | Classic snaps cannot resolve executables staged in payload bin directories because Snapcraft omits those directories from PATH; this longstanding request remains untriaged. |
|
snapcraft (launchpad) issue #1825797 |
cmake: Shouldn't use sourcedir for building | ~brlin | 2747d | needs triage | 47 | 78 | 20 | CMake builds still read from SNAPCRAFT_PART_SRC, preventing patches to a build-tree copy before snapcraftctl build; current craft-parts behavior needs maintainer triage. |
|
snapcraft (launchpad) issue #2006076 |
panic when use socks proxy | ~mohammadv184 | 1361d | needs triage | 46 | 29 | 5 | Snapcraft 7.2.9 reportedly crashes during login when a SOCKS proxy is configured; proxy details, reproduction steps, and a traceback are missing, with no maintainer triage. |
|
snapcraft (launchpad) issue #2060820 |
`UBUNTU_STORE_AUTH_DATA_FILENAME` should be passed from Snapcraft to SnapD... | ~jordanmg13 | 932d | needs triage | 46 | 48 | 10 | Snapcraft 7 reportedly failed to download an authenticated store snap during an LXD destructive build until an absolute credentials path was passed to snapd; no current reproducer exists. |
|
snapcraft (launchpad) issue #2045895 |
patchelf missing snap libdir rpath | ~saviq | 1057d | needs triage | 46 | 76 | 20 | Classic Flutter builds show patchelf omitting bundled usr/lib RPATH entries required by the classic linter; the concrete mismatch remains untriaged with no linked fix. |
|
snapcraft (launchpad) issue #1647343 |
Validator for the snap's icon appears to check the file before the snap is compiled | ~michael-r-milton | 3615d | needs triage | 46 | 66 | 17 | Icon validation rejects packaged-container paths before building, while asset finalization supports prime-relative paths; this old, untriaged report needs assessment against current behavior. |
|
snapcraft (launchpad) issue #1850921 |
Python plugin: file conflicts when using the plugin with a custom version of... | ~ntamas | 2554d | needs triage | 46 | 55 | 8 | Python plugin reportedly provisions Python 3.5 before a custom-Python part is staged, causing /usr/bin conflicts; this Snapcraft 2.44 report remains untriaged against the current plugin architecture. |
|
snapcraft (launchpad) issue #1719946 |
Snapcraft has three unsynced bug lists | ~mpt | 3319d | needs triage | 45 | 52 | 7 | Bug tracking remains split across Launchpad and GitHub and needs a maintainer decision; current README and contribution docs already direct reporters to GitHub. |
|
snapcraft (launchpad) issue #1897098 |
Trigger font cache rebuild if new fonts added to the system | ~igorljubuncic-deactivatedaccount | 2226d | needs triage | 45 | 30 | 3 | Placeholder design request to refresh snap font caches when host/user fonts change after install; discussed 2021, no labels, no agreed spec, no activity since Feb 2021 |
|
snapcraft (launchpad) issue #1995856 |
Get Desktop icon from snap instead of source tree | ~merlijn-sebrechts | 1452d | needs triage | 45 | 78 | 12 | No syntax supports sourcing the top-level icon from a built part; implementation is needed for downloaded build-time assets, but the issue has no maintainer triage or discussion. |
|
snapcraft (launchpad) issue #1882255 |
autotools plugin does not allow specifying a build directory different from... | ~dmitriis | 2337d | needs triage | 45 | 86 | 20 | Autotools lacks an opt-in out-of-source build directory, blocking libvirt versions that reject in-source configure; the reproducer is detailed but the issue remains untriaged. |
|
snapcraft (launchpad) issue #1583236 |
snapcraft APT sources checking too strict | ~cmiller | 3816d | needs triage | 45 | 43 | 6 | Snapcraft still turns any apt-get update failure into a package-list refresh error; this old report needs a modern reproducer and a policy for distinguishing harmless source failures. |
|
snapcraft (launchpad) issue #2053119 |
Pulling from private repository with passphrase protected key fails | ~gbeuzeboc | 988d | needs triage | 45 | 58 | 12 | Snapcraft 8.0.2 with --bind-ssh fails to prompt for a passphrase-protected SSH key during a private Git clone; no fix or maintainer triage is recorded. |
|
snapcraft (launchpad) issue #2059717 |
please allow omitting source for the dump plugin | ~ogra | 945d | needs triage | 45 | 50 | 16 | Request to let dump parts omit source and rely on stage-packages; current dump properties still require source, and maintainer requested a concrete example YAML. |
|
snapcraft (launchpad) issue #1810738 |
Catkin plugin missing rosdep and stage packages source lists customization | ~benjamin.leclerc | 2852d | needs triage | 45 | 48 | 10 | Old open Catkin plugin request to expose rosdep and stage-package source lists; no maintainer response, and compatibility with the current plugin needs validation. |
|
snapcraft (launchpad) issue #1807553 |
Snapcraft crashes when updating parts using organize key | ~brlin | 2881d | needs triage | 45 | 32 | 5 | A non-clean rebuild reportedly crashes while organize moves a stale directory into itself. No reproducer or maintainer triage exists; current craft-parts has a self-organization guard. |
|
snapcraft (launchpad) issue #1957766 |
plugin:meson is not installed during pull stage | ~xnox | 1750d | needs triage | 45 | 52 | 13 | Snapcraft 6.0.1 Meson-part builds reportedly fetch Meson during build after the proxy expires; the issue remains open with no labels, comments, or triage. |
|
snapcraft (launchpad) issue #1595964 |
pull, build and other commands should be idemnpotent | ~didrocks | 3779d | needs triage | 45 | 38 | 6 | Lifecycle commands rebuild state destructively, hindering plugin composition; the broad idempotency request remains valid but untriaged and without a current reproducer |
|
snapcraft (launchpad) issue #1851905 |
Unable to build with lxd when using lxd with lvm pool. | ~extraymond | 2546d | needs triage | 45 | 62 | 15 | Snapcraft 3.8/3.9.2 --use-lxd reportedly assumes a directory-backed LXD pool and fails on LVM pools; the old report has no maintainer triage or follow-up. |
|
snapcraft (launchpad) issue #1638840 |
snapcraft copies /etc/apt/sources but ignores /etc/apt/preferences | ~aacid | 3647d | needs triage | 45 | 35 | 7 | APT host pinning was reported ignored in 2016; the Zesty/Yakkety reproducer is obsolete, while modern Snapcraft supports declared repository priorities through craft-archives, leaving host-preference behavior to revalidate. |
|
snapcraft (launchpad) issue #2026734 |
ld throws libc_nonshared.a: No such file or directory when run inside snap... | ~mertkirpici | 1207d | needs triage | 45 | 82 | 17 | Runtime GCC in a snap cannot link because libc_nonshared.a is unresolved; an exact repro and bind-file workaround exist, but the issue remains unlabeled and untriaged. |
|
snapcraft (launchpad) issue #1865167 |
Removing a hook script and building, script still present | ~knitzsche | 2435d | needs triage | 45 | 76 | 16 | Incremental builds can retain a deleted snap/hooks script until snapcraft clean; the report has no maintainer triage or confirmed resolution. |
|
snapcraft (launchpad) issue #2016899 |
Remove directory step takes too long | ~nteodosio | 1290d | needs triage | 45 | 61 | 11 | Snapcraft cleanup of a Chromium build directory takes 11–82 minutes under LXD after failure, blocking resumed builds; reproduced on 7.3.1 and 8.3.4 and awaiting triage. |
|
snapcraft (launchpad) issue #2015327 |
Files in path to snapcraft.yaml are excluded in source directive | ~kian-parvin | 1303d | needs triage | 45 | 68 | 13 | Core22 builds with Snapcraft 7.3.1 omit files from a source: ../.. tree and produce a dirty Git version; Core20 and Snapcraft 4.8 do not. The report is untriaged. |
|
snapcraft (launchpad) issue #1856242 |
Python plugin: ship pyc files only | ~om26er | 2513d | needs triage | 45 | 45 | 6 | Python plugin bytecode-only packaging is untriaged; its 2019 workflow is stale because the current plugin delegates to craft-parts and no longer contains compileall. |
|
snapcraft (launchpad) issue #2009970 |
Desktop extension symlinks aren't updated on snap revert | ~lauren-brock | 1329d | needs triage | 45 | 72 | 21 | Desktop extensions store .last_revision in versioned $SNAP_USER_DATA, so after `snap revert` the marker already matches and desktop-launch skips symlink refresh, leaving stale/broken symlinks. Reported by an external contributor; unlabelled, no maintainer response, code still unchanged. |
|
snapcraft (launchpad) issue #1667318 |
Add Track information to 'status', 'close', and 'revisions' output | ~joetalbott | 3535d | needs triage | 45 | 68 | 18 | Legacy request to expose track data in status, close, and revisions; a contributor linked snapcore/snapcraft#1161, while current code only clearly shows a Track column for status and no maintainer triage is recorded. |
|
snapcraft (launchpad) issue #2065278 |
flutter plugin: cache SDK across parts | ~saviq | 903d | needs triage | 44 | 72 | 16 | Flutter plugin stores its SDK in each part's build directory, causing separate clones and precaches; the optimization remains valid but untriaged and has no maintainer response. |
|
snapcraft (launchpad) issue #2014963 |
Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | ~brlin | 1307d | needs triage | 44 | 71 | 18 | `snap try` Snapcraft could not self-inject into legacy LXD builds because snapd cannot download a try snap; the affected provider is removed, but current behavior needs retesting. |
|
snapcraft (launchpad) issue #1976290 |
extension files get repeated over and over each time snapcraft is recreated | ~rastersoft-gmail | 1613d | needs triage | 43 | 58 | 11 | Incremental builds reportedly accumulate stale GNOME extension sources in Python build/lib, growing the snap; the 2022 report remains open without maintainer triage or a confirmed fix. |
|
snapcraft (launchpad) issue #2006599 |
using advanced grammar to build towards a certain arch does not work with stage-snaps | ~ogra | 1359d | needs triage | 43 | 68 | 15 | Cross-build grammar selects a foreign-architecture stage snap, but its download lacks the target store architecture and reports the snap missing. A workaround exists; the report remains untriaged. |
|
snapcraft (launchpad) issue #1831752 |
Missing grammar for conditional configflags on/to architecture | ~fnordahl | 2703d | needs triage | 43 | 77 | 14 | Architecture-conditional configflags remain unsupported for plugin-specific part keys; this old, untriaged proposal has only an author follow-up and no maintainer response. |
|
snapcraft (launchpad) issue #1617907 |
Two python parts in the same snapcraft.yaml result in not installing the... | ~liu-xiao-guo | 3713d | needs triage | 43 | 55 | 10 | Snapcraft 2.14 fails when multiple Python parts stage conflicting interpreter files. Similarity to resolved bug #1531570 was disputed, and the old report remains unverified. |
|
snapcraft (launchpad) issue #2019489 |
build fails pip update of pip setuptools wheel | ~kenneth-loafman | 1265d | needs triage | 43 | 64 | 12 | Python-part builds can fail after automatically upgrading pip, setuptools, and wheel because system pkg_resources requires the old pip; the report remains open and untriaged. |
|
snapcraft (launchpad) issue #1835556 |
No way to natively build for the non-host arch | ~laney | 2673d | needs triage | 42 | 61 | 8 | A 2018 request for native i386 builds through matching LXD or Multipass environments remains open and untriaged; current --build-for support and provider image coverage need review. |
|
snapcraft (launchpad) issue #1989149 |
File conflicts between parts should include files with identical contents | ~rpjday | 1512d | needs triage | 42 | 67 | 12 | Snapcraft still allows identical same-path files from different parts without warning; changing this collision behavior remains unresolved in craft-parts. |
|
snapcraft (launchpad) issue #2080356 |
Two python3 parts using setuptools are always conflicting on core22 | ~gbeuzeboc | 778d | needs triage | 42 | 70 | 10 | Two python plugin parts always collide on core22 because each part's venv embeds its own install path in bin/activate*, __pycache__ and RECORD; only workaround is manual stage exclusions. No maintainer response. |
|
snapcraft (launchpad) issue #1869530 |
push timeout | ~casper-dcl | 2406d | needs triage | 42 | 58 | 14 | Request to avoid indefinite blocking on Store processing or add a timeout; legacy push is removed, but replacement upload still polls without a timeout option. |
|
snapcraft (launchpad) issue #1996621 |
Multiple levels of mixed prime inclusion/exclusion fail silently | ~lauren-brock | 1444d | needs triage | 42 | 72 | 13 | Nested stage/prime paths beneath an excluded parent are silently omitted. A minimal reproducer is provided, but the issue remains unlabeled and untriaged. |
|
snapcraft (launchpad) issue #2051841 |
Plugs/Slots implicit assignment should be deprecated for `base: core24` | ~saviq | 1002d | needs triage | 42 | 70 | 14 | Configured top-level plugs/slots still create implicit core24 connections without warnings; only null-valued entries warn. The proposed deprecation or unused-connection warning remains untriaged. |
|
snapcraft (launchpad) issue #1735004 |
Push issue with bad internet connection | ~hatari | 3257d | needs triage | 42 | 52 | 7 | Upload/push on a flaky connection fails with a bad gateway after the file reached the store; retrying then fails with 'binary_sha3_384: A file with this exact same content has already been uploaded'. Reporter asks for resumable uploads (returning an upload_id) and a workaround. No maintainer response or labels. |
|
snapcraft (launchpad) issue #1662634 |
Please add snapcraft version key | ~ted | 3551d | needs triage | 42 | 58 | 11 | A snapcraft.yaml minimum-version key could produce a clear required-version message instead of a schema error; the proposal remains unimplemented and untriaged. |
|
snapcraft (launchpad) issue #1893850 |
Snapcraft doesn't inject itself into build VM if host rev doesn't change | ~kyrofa | 2249d | needs triage | 42 | 78 | 17 | An old, unlabeled report says sideloaded Snapcraft snaps with identical x1 revisions can leave a stale build-VM copy; the tracker has no follow-up or confirmed hash-based fix. |
|
snapcraft (launchpad) issue #1965309 |
Record the git ID used for the build in the log | ~seb128 | 1687d | needs triage | 42 | 76 | 23 | Build logs omit the resolved Git commit for branch-based part sources, making failed-build reproduction harder; no maintainer triage or implementation is recorded. |
|
snapcraft (launchpad) issue #1822727 |
Snapcraft complains the missing `source` property when the source URL is... | ~brlin | 2767d | needs triage | 42 | 66 | 12 | Dynamic override-pull builds cannot omit source because validation still requires it, while a dummy source triggers source-type detection failure. This old, unlabelled report needs reproduction against the current lifecycle. |
|
snapcraft (launchpad) issue #1825820 |
Snapcraft doesn't update the `snapcraft-project` disk source when the path is moved | ~brlin | 2747d | needs triage | 42 | 68 | 13 | LXD builds reportedly fail after moving a project because the instance retains the old disk source. LXD remains supported, but this untriaged report needs verification against the current craft-providers integration. |