Showing 100 of 2042 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1804957 |
Malicious namesquatting of snaps | ~buzz-- | 2848d | close not a bug | 100 | 75 | Complaint that a user squatted the 'bitcoin' snap name and is forcing outdated, incompatible software on users. No labels, no comments, no maintainer activity in ~7.8 years. A store policy/moderation concern, not a snapcraft tool defect. |
|
snapcraft (launchpad) issue #1666161 |
Can’t dry-run a build to check snapcraft.yaml | ~mpt | 3490d | close stale | 100 | 65 | Feature request (9.5 years old, no maintainer activity) for a dry-run build that validates snapcraft.yaml without performing the build. The core capability now exists via the snapcraft validate command, so the request is largely obsolete. |
|
snapcraft (launchpad) issue #1824077 |
IsADirectoryError occurred when migrating /usr/bin/X11 symlink in stage step | ~brlin | 2712d | close stale | 100 | 75 | snapcraft 3.3 (2019) crashes with IsADirectoryError in _migrate_files when staging a symlink (usr/bin/X11) that points to '.'. 2701 days old, 0 comments, no labels, no maintainer interaction; old internal staging code since rewritten. |
|
snapcraft (launchpad) issue #1619818 |
No explicit error message when trying to push the same snap twice | ~elopio | 3661d | close stale | 100 | 70 | Request to surface the store's 'already been uploaded' message instead of a generic error when pushing a duplicate snap. 10 years old, no activity; snapcraft push was later removed, so it is no longer applicable. |
|
snapcraft (launchpad) issue #1849582 |
Mumble Crashes | ~derekagraham78 | 2515d | close stale | 100 | 80 | Mumble snap crash reported via pastebin link only, no description or reproduction steps. 2504 days old with zero comments and no maintainer interaction. Pastebin link likely dead. |
|
snapcraft (launchpad) issue #1682822 |
Snapcraft deb does not work on KDE Neon. snap does. | ~frecel | 3437d | close stale | 100 | 80 | Old snapcraft deb package crashes on KDE Neon with 'not supported on this operating system' at import. 9+ years old, no labels or comments; the failing code path no longer exists in the current codebase and the deb install method is superseded by the snap. |
|
snapcraft (launchpad) issue #1617002 |
LP build: "/usr/bin/ld: cannot find -llibrary" | ~eldar | 3669d | close stale | 100 | 80 | Reporter's kicad-dev-snap failed on Launchpad (Xenial) with linker error 'cannot find -lngspice' while building locally succeeded. 10 years old, zero comments, no maintainer response, Xenial base long EOL. |
|
snapcraft (launchpad) issue #1995856 |
Get Desktop icon from snap instead of source tree | ~merlijn-sebrechts | 1404d | close not a bug | 100 | 70 | Feature request to allow icon field in snapcraft.yaml to reference files in the snap instead of source tree. Issue is 3.8 years old with no maintainer interaction. |
|
snapcraft (launchpad) issue #1826262 |
Error: The part has run through its entire lifecycle | ~saviq | 2697d | close stale | 100 | 72 | Snapcraft 1.x build error 'part has run through its entire lifecycle' reported in 2017 when modifying multipass snapcraft.yaml; zero comments, no labels, project since fully rearchitected into craft-* subprojects. |
|
snapcraft (launchpad) issue #1624854 |
"Developer has not signed agreement" when run snap push | ~psivaa | 3645d | close stale | 100 | 65 | User hit 403 'Developer has not signed agreement' (user-not-ready) on snapcraft push, resolved via IRC by signing at myapps.developer.ubuntu.com. Suggests adding that link to the error message. 10 years old, no maintainer activity. |
|
snapcraft (launchpad) issue #1663051 |
Stage package cache is never cleaned | ~kyrofa | 3502d | close stale | 98 | 55 | Snapcraft's stage-package cache (keyed by source hash) is never cleaned and grows unbounded as new packages/sources are fetched. Self-filed by a maintainer ~9.5 years ago with no labels, comments, or follow-up; related Launchpad bug closed without resolution. |
|
snapcraft (launchpad) issue #1869542 |
snapcraft unable to find snap/snapcraft.yaml file | ~keshavnrj | 2358d | close stale | 98 | 60 | snapcraft 3.11 (2019) loses snap/snapcraft.yaml after a few builds and drops to the VM shell; workaround is snapcraft clean. 6+ years old, no labels, no maintainer comments, tied to a long-superseded build environment. |
|
snapcraft (launchpad) issue #1693451 |
Support CircleCI for building | ~popey | 3396d | close stale | 98 | 70 | Feature request to add CircleCI as a supported CI for building/pushing snaps, with encrypted store credentials comparable to the Travis workflow. Open ~9 years, labelled integrations, zero comments, no maintainer activity. |
|
snapcraft (launchpad) issue #1735004 |
Push issue with bad internet connection | ~hatari | 3209d | close stale | 98 | 72 | Snapcraft push fails with binary_sha3_384 duplicate error after interrupted upload on slow connection; requests server return upload_id for resume. 8+ years old, zero comments, no labels, push command since removed. |
|
snapcraft (launchpad) issue #1959851 |
gnome-3-38 extension not compatible with python plugin on core20 | ~goodsoftworx | 1682d | close stale | 98 | 60 | gnome-3-38 extension sets PYTHONPATH to its own interpreter, overriding the python plugin and causing build errors on core20. Affects PyGObject-based GTK 3 snaps. No maintainer activity in 4.5 years; core20 base is legacy. |
|
snapcraft (launchpad) issue #1675545 |
undefined symbol: _Py_RefTotal | ~evarlast | 3459d | close stale | 98 | 70 | Reports undefined symbol _Py_RefTotal when loading the Cheetah C extension built for python2 inside a snap, asking whether the python plugin supports python2 C modules. No labels, no comments, no maintainer response; ~9.4 years old and python2 is EOL. |
|
snapcraft (launchpad) issue #1709674 |
Catkin plugin: consumer snap still pulls in packages contained in producer snap | ~kyrofa | 3320d | close stale | 96 | 58 | Catkin (ROS1) plugin bug: a consumer snap still pulls in packages already contained in the producer snap, implying a flaw in the underlay logic. Filed by a maintainer in 2016 as an investigation note; no labels, comments, or activity since. |
|
snapcraft (launchpad) issue #1670162 |
publish complains about desktop file un-necessarily | ~popey | 3477d | close stale | 96 | 55 | Snapcraft publish validation falsely requires a .desktop file when a snap uses the x11 plug, blocking a CLI utility from releasing to stable. Reported ~9.5 years ago with no maintainer response; the quoted error is from the old snapcraft 1.x publish flow. |
|
snapcraft (launchpad) issue #1652441 |
unity7: LauncherEntry API does not work due to snapd not respecting the... | ~mvo | 3548d | close stale | 95 | 80 | Unity 7 LauncherEntry progress bar fails because snapd renames snap .desktop files, breaking application:// URI resolution. Open since 2016 with no labels or maintainer interaction; Unity 7 is EOL. |
|
snapcraft (launchpad) issue #2017688 |
staging lsb-release in python part make the part fail | ~gbeuzeboc | 1235d | needs triage | 95 | 70 | Untriaged bug report stating that staging lsb-release in a python part causes ensurepip to fail due to PATH pollution. No maintainer interaction in over 3 years. |
|
snapcraft (launchpad) issue #2052928 |
Pulling from private repository without known_hosts hangs forever | ~gbeuzeboc | 942d | needs triage | 95 | 50 | SSH pull from private repo hangs when known_hosts is missing; SSH authenticity prompt is hidden by snapcraft progress bar. Untriaged, 935 days old. |
|
snapcraft (launchpad) issue #2020348 |
Snapcraft tries to run chisel and fails | ~itrue | 1208d | close stale | 95 | 55 | Typo in stage-packages (missing $ before CRAFT_TARGET_ARCH) causes snapcraft to try running chisel instead of giving a clear syntax error. Unlabelled, no maintainer response, 1200 days old. |
|
snapcraft (launchpad) issue #1604909 |
Python3 plugin fails to install requirements that are only available as wheels | ~ralsina | 3705d | close stale | 95 | 72 | Snapcraft 1.x python3 plugin passed --install-option=--prefix=usr to pip 8.1.2, which disabled wheel usage and broke installs of wheel-only packages (e.g. entrypoints). 10 years old, 0 comments, no maintainer interaction; the plugin was since rewritten in the modern craft-parts codebase. |
|
snapcraft (launchpad) issue #1638508 |
API package creation from the stage | ~bzoltan | 3600d | close stale | 95 | 70 | 2016 feature proposal to add a snapcraft 'development' plugin that tars up the stage with filtered content, creating an API/developer package (headers/libs) for runtime snaps like ubuntu-qt-runtime. No labels, comments, or activity for about 10 years. |
|
snapcraft (launchpad) issue #1666739 |
Content interface parsing too lenient | ~michihenning | 3489d | close stale | 95 | 55 | Snapcraft silently accepts a string for the content interface read/write path instead of requiring a list, deferring the error to snapd install time. Reporter wants snapcraft to reject the invalid YAML. Unlabelled, no maintainer activity in ~9.5 years. |
|
snapcraft (launchpad) issue #1681722 |
classic snaps cannot find stage packages in $PATH | ~stub | 3440d | close stale | 95 | 60 | Classic snaps with stage-packages cannot find dependent binaries because snap bin directories are missing from default PATH. 9+ years old, zero comments, no labels. A related workaround (PR #2889, snapcraft-runner) was merged to address classic snap PATH resolution. |
|
snapcraft (launchpad) issue #1673658 |
python package failed to install because of directories in the source | ~thomir-deactivatedaccount | 3466d | close stale | 95 | 70 | Snapcraft 2.27.1-era report that the python plugin fails to install packages when the source contains directories, leaving the executable unstaged. No comments, author account deactivated, and the affected version is long obsolete. |
|
snapcraft (launchpad) issue #1676684 |
Python plugin tries to chmod symlinks to system files | ~mrjogo | 3455d | close stale | 95 | 70 | Old snapcraft python plugin (pre-rewrite) crashed with PermissionError when _fix_permissions tried to chmod root-owned symlinks to system files after a prior part staged python-dev. The plugin has since been fully rewritten as a thin wrapper around craft-parts; the offending _fix_permissions/_replicate_owner_mode code no longer exists in the repo. |
|
snapcraft (launchpad) issue #2011719 |
snapcraft expand-extensions is broken | ~scarlettmoore | 1276d | close stale | 95 | 85 | snapcraft expand-extensions command produces invalid YAML with parse-info field error. Issue is ~3.5 years old with no activity. |
|
snapcraft (launchpad) issue #1882270 |
feature request: allow pdb tracing of snapcraft plugin code | ~dmitriis | 2289d | close stale | 95 | 70 | Feature request (6+ years old, no labels, no comments) to add built-in pdb tracing of snapcraft plugin code for step-by-step build debugging; motivated by legacy bug 1882124 from the Python 3.6 plugin era. |
|
snapcraft (launchpad) issue #1805581 |
snapcraft fail | ~temasek | 2845d | close stale | 95 | 75 | Snapcraft 2.43.1 catkin plugin crash: rosdep cannot find key for roscpp_tutorials, raising FileNotFoundError during pull. 2834 days old, zero comments, no labels; the catkin plugin no longer exists in modern snapcraft. |
|
snapcraft (launchpad) issue #1839604 |
build-base seems broken | ~niemeyer | 2590d | close stale | 95 | 75 | Seven-year-old question about snapcraft rejecting 'base: bare' with 'build-base: core18' via a confusing validation error. No maintainer response; validation was rewritten in snapcraft 8.x, where build-base is now required for bare bases, so the reported combination is now valid. |
|
snapcraft (launchpad) issue #1903046 |
Progressive release stops showing metrics when set to 100% target | ~noise | 2136d | close stale | 95 | 55 | snapcraft status stops showing progressive release metrics once target reaches 100%. Reported 5.8 years ago with zero maintainer interaction, no labels, and no comments. Progressive release feature has since evolved (PR #6189 merged). |
|
snapcraft (launchpad) issue #1826481 |
LXDInstanceProvider does not pass proxy information to lxc exec | ~bnevis | 2696d | close stale | 95 | 70 | Request to pass proxy env vars (http_proxy, https_proxy, no_proxy) to lxc exec in LXDInstanceProvider for builds behind firewalls. Class no longer exists in current codebase; LXD legacy support was removed. |
|
snapcraft (launchpad) issue #1669854 |
Hidden files are not staged after "dump" | ~joeborg | 3479d | close stale | 95 | 55 | Reports that hidden files/dirs from a tar.gz unpacked via the dump plugin are dropped during part staging and again from stage to prime, though they appear in the install dir. 9.5 years old, zero comments, no maintainer interaction. |
|
snapcraft (launchpad) issue #1768233 |
Chains of parts with python contents can fail with pkg_resources import error | ~jocave | 3055d | close stale | 95 | 75 | Python part wheel build fails with pkg_resources.py31compat ImportError for bitstring on xenial. 8+ years old, zero comments, no labels. Parts system since rewritten in craft-parts with modern pip/setuptools, making this error no longer reproducible. |
|
snapcraft (launchpad) issue #1594794 |
Embedded version required in snapcraft.yaml | ~stub | 3734d | close stale | 95 | 55 | Feature request from 2014 to let snapcraft.yaml's version key reference a part name so the version is derived from the plugin (e.g. Python setup.py) for Launchpad auto-builds. 10 years old, zero comments, no labels, no maintainer engagement; targets obsolete snapcraft 1.x. |
|
snapcraft (launchpad) issue #1813364 |
The `setup.py` parse-info method treats description/long_description keys wrongly | ~brlin | 2786d | needs triage | 95 | 55 | Snapcraft's setup.py parse-info maps description to snap description and ignores long_description, mismatching setuptools conventions; open since 2018 with no maintainer activity. |
|
snapcraft (launchpad) issue #1834207 |
removing parts should clean stage and prime… stages? | ~saviq | 2635d | close stale | 95 | 55 | Bug report from 2017: removing a part from snapcraft.yaml does not clean its contents from stage/prime, so the built snap still includes the removed part's files. No labels, no comments, no maintainer activity in ~7 years. |
|
snapcraft (launchpad) issue #1918267 |
The warning for CVE-2020-27348 could include a reference to how to fix | ~seb128 | 2012d | close stale | 95 | 55 | Feature request to enhance the CVE-2020-27348 empty LD_LIBRARY_PATH warning in snapcraft build logs to include a hint on how to fix the issue or a link to relevant documentation. No maintainer response, no labels, inactive for ~5.5 years. |
|
snapcraft (launchpad) issue #1871273 |
Can't Buidl on WSL2 any Longer | ~vision9 | 2349d | close stale | 95 | 70 | Snapcraft build fails on WSL2 with KeyError 'dependencies' in the nodejs plugin's _get_installed_node_packages while parsing yarn output. 6+ years old, zero comments, no maintainer response; old plugin architecture since replaced. |
|
snapcraft (launchpad) issue #1567524 |
Support tar.lzma | ~olivier-interfasys | 3809d | close stale | 95 | 58 | Feature request to support tar.lzma archives in the sources plugin. 10+ years old, zero comments, no maintainer interaction; the sources plugin is a legacy component likely no longer present. |
|
snapcraft (launchpad) issue #1998341 |
Local pytest/unit run test_get_extensions_data_dir() fails | ~giusebar18 | 1381d | close stale | 95 | 55 | Local pytest test_get_extensions_data_dir() fails due to missing extensions data directory; resolved by running pip install .; no maintainer engagement in 1373 days |
|
snapcraft (launchpad) issue #1638622 |
dump plugin cannot copy a single file | ~jamesj | 3600d | needs triage | 95 | 70 | Request for the dump plugin to support copying individual files (like the deprecated copy plugin's files property). No maintainer response in ~9.6 years; dump plugin still only accepts source, so the gap persists. |
|
snapcraft (launchpad) issue #1608932 |
multiple parts with same git repo makes build checkout out redundant repos | ~adam-stokes | 3692d | close stale | 95 | 60 | snapcraft 2.13.1: parts sharing the same git source each get their own checkout instead of a shared cache. No maintainer activity for ~9.5 years; the 2.x series is EOL and modern craft-parts-based snapcraft uses a shared source cache. |
|
snapcraft (launchpad) issue #1875781 |
Unable to verify self signed certificate | ~taitenpeng | 2327d | close stale | 95 | 85 | Tracking bug for an OpenSSL self-signed certificate verification failure (openssl/openssl#1418) that broke HTTPS behind corporate proxies. Upstream fix (openssl/openssl#10587) merged in 2019. No activity for ~3.3 years, no labels or comments. |
|
snapcraft (launchpad) issue #1837268 |
cannot build snap in Arch Linux | ~shackraseaslug | 2611d | close stale | 95 | 75 | Snapcraft 3.6 on Arch Linux segfaults during VM build, leaving a stale multipass instance that fails to remount. Reported July 2019; no labels, no comments, no maintainer activity in ~7 years; the core18 multipass build path is long obsolete. |
|
snapcraft (launchpad) issue #1655634 |
Unable to release classic snap to beta channel | ~stub | 3530d | close stale | 95 | 55 | snapcraft release prints only 'Package is not ready to be published' with no reason, blocking the user from releasing a classic snap to beta. No labels, no comments, no maintainer response; inactive for ~6 years. |
|
snapcraft (launchpad) issue #2039971 |
Add support for _daemon_ as a valid system-username in snapcraft.yaml | ~morrisong | 1057d | needs triage | 95 | 50 | Validation schema in snapcraft doesn't accept _daemon_ as a valid system-username, requiring passthrough workaround. Issue is 3 years old with no maintainer response. |
|
snapcraft (launchpad) issue #1751828 |
using executable from core snap fails sanity check | ~ondrak | 3119d | close stale | 95 | 55 | Snapcraft's sanity check fails when an application command references an executable provided by the core snap (e.g., ping). Workaround: install the binary on the build host. Unanswered since 2017. Old host-based check likely obsolete in modern snapcraft. |
|
snapcraft (launchpad) issue #1807125 |
After snapcraft refresh, old multipass containers no longer work | ~igorljubuncic-deactivatedaccount | 2836d | needs triage | 95 | 70 | snapcraft reuses outdated multipass containers after snap refresh, causing 'Could not find snap/snapcraft.yaml' errors until snapcraft clean is run; untriaged, no maintainer activity for ~7.7 years |
|
snapcraft (launchpad) issue #2006076 |
panic when use socks proxy | ~mohammadv184 | 1314d | close stale | 95 | 60 | Reported crash when using SOCKS proxy with snapcraft login. No maintainer engagement, no labels, no comments, inactive for 1305 days. |
|
snapcraft (launchpad) issue #1877448 |
Hooks stanza doesn't match parts and apps | ~ted | 2318d | needs triage | 95 | 75 | Feature request proposing a syntax change to the hooks stanza in snapcraft.yaml to use named hooks instead of trigger-based keys, for consistency with parts/apps. Open 6+ years with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #2043012 |
The --base command option for the `snapcraft help` command no longer works | ~brlin | 1038d | close stale | 95 | 75 | The --base option for snapcraft help command no longer works; issue is 1030 days old with no maintainer activity or comments |
|
snapcraft (launchpad) issue #1582417 |
snapcraft doesn't create binary-identical reproducible builds | ~cmiller | 3770d | needs triage | 95 | 65 | Feature request for byte-identical reproducible snap builds (deterministic plugin order, identical output across machines). Open ~10 years with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #1843147 |
snapcraft mishandles .PNG extension | ~merlijn-sebrechts | 2561d | needs triage | 95 | 45 | Snapcraft accepts uppercase .PNG icon extension and fails to remove stale icon files when the icon type changes, leaving both old and new icons in /meta/gui/. No maintainer interaction since filing ~7 years ago. |
|
snapcraft (launchpad) issue #1841892 |
snapcraft options are position-dependent | ~saviq | 2571d | close stale | 95 | 65 | Reports snapcraft CLI flags are position-dependent: `snapcraft --use-lxd build` silently ignores the flag while `snapcraft build --use-lxd` works. Unanswered for ~7 years; `--use-lxd` was later removed from snapcraft, making the example obsolete. |
|
snapcraft (launchpad) issue #2014963 |
Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | ~brlin | 1259d | close stale | 95 | 60 | Snapcraft fails when using snap try due to snapd not allowing file downloads for try-mode snaps. Issue is 1251 days old with no maintainer engagement. |
|
snapcraft (launchpad) issue #1769519 |
Setting the snapcraft.yaml version field to 'git' produces undocumented and... | ~njmcphail | 3050d | close stale | 95 | 55 | Snapcraft 2.42 (2018): setting version: git in snapcraft.yaml substitutes a mangled git describe output; tags with invalid chars (e.g. underscore) yield an invalid version that snap refuses to install, with no error. No maintainer interaction in 8+ years. |
|
snapcraft (launchpad) issue #1688703 |
Enable optimizations by default | ~eyelash | 3416d | needs triage | 95 | 70 | Request (2018) to make snapcraft plugins consistently enable optimizations by default, or at least document each plugin's default optimization behavior. No maintainer response; plugins have since been refactored into craft-parts. |
|
snapcraft (launchpad) issue #1716055 |
It is not possible to install a build-snap with a closed risk | ~elopio | 3290d | close stale | 95 | 55 | build-snaps with a closed channel (e.g. latest/candidate) crashes with KeyError instead of falling back to the next open risk level; filed by maintainer elopio 9 years ago, zero activity, old internal/repo code path no longer exists in current architecture |
|
snapcraft (launchpad) issue #1727787 |
segmentation fault | ~hawat-thufir | 3242d | close stale | 95 | 80 | Segfault when running ubuntu-make.umake android after installing the ubuntu-make classic snap. ~9 years old, no labels, no comments, no maintainer interaction; crash is in the external ubuntu-make app, not snapcraft. |
|
snapcraft (launchpad) issue #1857705 |
The dotnet plugin does not support the current version of .Net Core | ~katrinag | 2450d | close stale | 95 | 82 | Request to update the snapcraft dotnet plugin to support .NET Core 3.0+ and bases beyond core16. The plugin has since been fully reworked in snapcraft 8.x to support core22+ and modern .NET SDKs, making this obsolete. |
|
snapcraft (launchpad) issue #1889082 |
snapcraft could be more helpful in figuring out prime/organize errs vs... | ~anonymouse67 | 2237d | close stale | 95 | 70 | Request to improve snapcraft error message for command-chain items to distinguish between missing file, wrong location, and non-executable script. No maintainer interaction in 6+ years. |
|
snapcraft (launchpad) issue #1698888 |
Snapcraft dpkg-query error on multiarch OS | ~pcercuei | 3371d | needs triage | 95 | 65 | Snapcraft fails on multiarch OS with both i686 and x86_64 libc6 installed, as dpkg -L libc6 returns an ambiguous package name error. 9-year-old issue with no maintainer interaction; the dpkg -L call still exists in craft-parts. |
|
snapcraft (launchpad) issue #1803235 |
signup process does not send activation email | ~lhonda | 2859d | close stale | 95 | 75 | Report that forum.snapcraft.io signup did not send an activation email (Discourse forum infrastructure problem, not a snapcraft codebase bug). No labels, no comments, no maintainer activity in ~8 years. |
|
snapcraft (launchpad) issue #1606819 |
snapcraft doesn't tell me where to put the .py file for my custom plugin | ~zyga | 3698d | close stale | 95 | 65 | Request for a clearer error when a custom plugin's .py file is in the wrong location; author self-resolved in an edit (file goes in parts/plugins/x_foo.py, 'plugin: x-foo'). No maintainer activity for ~8.6 years. |
|
snapcraft (launchpad) issue #1766101 |
Snapcraft not handling cmake nested builds, not including build script files... | ~anoncoward8348 | 3064d | close stale | 95 | 55 | Snapcraft 2.41 (classic) user reports three problems building FeedReader: cmake plugin fails on nested builds, build-override output not primed, meson build linking host glibc/gcc/zlib. No maintainer interaction; version superseded by core22 rewrite. |
|
snapcraft (launchpad) issue #1871660 |
create-key with no passphrase with pop-up loop | ~jamesj | 2347d | close not a bug | 95 | 70 | snapcraft create-key cannot be run without a passphrase on a headless VM (Ubuntu 18.04 EC2); pressing enter at the passphrase prompts triggers a looping pop-up. Open ~6.4 years with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #1809475 |
Feature Request: Snapcraft should ship gitignore when running `snapcraft init` | ~brlin | 2821d | close stale | 95 | 65 | Feature request from 7.7 years ago asking snapcraft init to auto-create a .gitignore file using the community Snap.gitignore template. Zero comments, no labels, no maintainer interaction. The init command still exists but the project has been fully restructured since filing. |
|
snapcraft (launchpad) issue #1807553 |
Snapcraft crashes when updating parts using organize key | ~brlin | 2834d | close stale | 95 | 60 | Snapcraft crashes with shutil.Error when a part's organize key maps a directory into its own subpath during non-clean rebuilds; no maintainer response, no labels, no reproducible steps, and the organize code has since been rewritten in craft-parts. |
|
snapcraft (launchpad) issue #1882124 |
snapcraft does not properly surface an error message during the pip presence... | ~dmitriis | 2290d | close stale | 95 | 58 | Snapcraft's pip presence check swallows the real exception (ModuleNotFoundError: distutils.util) on second/subsequent runs, showing only 'Exited with code 1'. Legacy plugin code, Python 3.6 era, untriaged and inactive ~6 years. |
|
snapcraft (launchpad) issue #1881515 |
Snapcraft pulling wrong arch of debs when building foreign snaps | ~taitenpeng | 2294d | close stale | 95 | 72 | 2018 report: --target-arch=armhf on x86 pulls x86-64 stage-packages debs instead of armhf. No labels, comments, or maintainer response in 6+ years. Legacy --target-arch flag removed; modern cross-compile documents the :$CRAFT_ARCH_BUILD_FOR suffix requirement. |
|
snapcraft (launchpad) issue #1922981 |
unable to run on centos 8 VM | ~anonymouse67 | 1983d | close not a bug | 95 | 70 | Traceback when building the snapd snap with the LXD snap on a CentOS 8 VM. Snapcraft requires an Ubuntu host, so this is an unsupported platform. 5.4 years old, 0 comments, no maintainer interaction. |
|
snapcraft (launchpad) issue #1767077 |
Container names are inconsistent lxd vs multipass | ~popey | 3060d | needs triage | 95 | 55 | Request for consistent build container naming between LXD (snapcraft-<name>) and Multipass (random <name>) so snapcraft containers are easy to spot. No labels, no comments, no maintainer activity for ~7.5 years. |
|
snapcraft (launchpad) issue #1771778 |
Inconsistent parameter syntax | ~popey | 3039d | close stale | 95 | 60 | snapcraft release accepts comma-separated channels but snapcraft close does not, requiring space-separated args. 8+ years old, zero comments, no labels, project since completely rewritten. |
|
snapcraft (launchpad) issue #1646081 |
Gadget snap cannot be built twice | ~zyga | 3572d | needs triage | 95 | 55 | Building a gadget snap twice in the same directory fails with a 'gadget.yaml and prime/meta/gadget.yaml are the same file' error on snapcraft 2.22.1. Unlabelled, no comments, 3561 days old, references a deprecated version. |
|
snapcraft (launchpad) issue #1814729 |
Setting SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY doesn't take effect | ~popey | 2775d | close stale | 95 | 65 | SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY change ignored when reusing existing Multipass VM; filed in 18.10 era, 0 comments, no maintainer interaction in 7.5 years, related LP bug closed without resolution |
|
snapcraft (launchpad) issue #1748324 |
python plugin fails on hashes in requirements.txt | ~ipmb | 3137d | close stale | 95 | 70 | Python plugin (snapcraft 2.35) fails when requirements.txt contains --hash entries, as pip's --require-hashes mode rejects the file:// directory requirement. Old plugin architecture removed; issue is 8.5 years old with no maintainer activity. |
|
snapcraft (launchpad) issue #1813634 |
not reliable way to detect target architecture | ~ondrak | 2783d | needs triage | 95 | 55 | Snapcraft 3.0.1: project.target_arch and SNAPCRAFT_ARCH_TRIPLET give inconsistent values for target arch across native, cross, and multi-arch (build-on/run-on) builds. No maintainer response, no labels, inactive ~7 years. |
|
snapcraft (launchpad) issue #1838474 |
nodejs plugin assumes a version key in the package.json | ~robcresswell-deactivatedaccount | 2600d | close stale | 95 | 75 | Nodejs plugin crashed with KeyError when package.json lacked a version key, with no fallback to snapcraft.yaml version. Reported 2019, zero comments, no maintainer response. The nodejs plugin has since been removed and replaced by the npm plugin, so the referenced code no longer exists. |
|
snapcraft (launchpad) issue #1772885 |
dropping privs did not work: No data available | ~edo.red | 3033d | close stale | 95 | 75 | User reports 'dropping privs did not work: no data available' when running sudo lxd init while setting up snapcraft. It is a support question about LXD (an external tool), not a snapcraft bug. Open 8+ years with zero comments, labels, or maintainer interaction. |
|
snapcraft (launchpad) issue #1749699 |
Delta error is shown on first push, can be avoided? | ~facundo | 3130d | close stale | 95 | 60 | User reports snapcraft push prints 'Error generating delta: delta saving is less than 10%' on a first push where no delta can exist. No labels, no comments, no maintainer activity in ~8.5 years; delta compression has since been removed from snapcraft. |
|
snapcraft (launchpad) issue #1750006 |
Revamp tests for using utilities in deb/snap/docker | ~kyrofa | 3129d | close stale | 95 | 70 | Maintainer task to revamp complex unit tests verifying which utilities are used when Snapcraft runs from a deb, snap, or docker. 8.5 years old, no labels, zero comments; near-identical issue snapcraft#1932 was closed without action. |
|
snapcraft (launchpad) issue #1958282 |
Pass proxy settings to override-pull | ~mr-cal | 1697d | close stale | 95 | 70 | Feature request to pass proxy settings into override-pull. Open for 4.6 years with zero comments, no labels, and no maintainer engagement. |
|
snapcraft (launchpad) issue #1798205 |
Underscores in app names not reported properly | ~roger.light | 2887d | needs triage | 95 | 60 | Snapcraft reports the wrong app name in validation errors when an app name contains an underscore: with apps 'one' and 'two_three', the error blames the valid app 'one' instead of 'two_three'. Open since 2014, no labels, comments, or maintainer activity. |
|
snapcraft (launchpad) issue #1815358 |
python package not updating during snap creation | ~falko-o | 2770d | close stale | 95 | 60 | Snapcraft python plugin fails to rebuild a changed Python package on re-run, keeping the old version; user must flip source-type git/local to force a build. Legacy multipass-VM flow, no maintainer activity in ~7.5 years. |
|
snapcraft (launchpad) issue #1752580 |
tests.integration.general.test_parser.TestParserWikis fails | ~kalikiana | 3116d | close stale | 95 | 75 | 8.5-year-old report that TestParserWikis failed locally because the bin/snapcraft-parser binary was missing (Python 3.5 era). The old tests/integration/general suite no longer exists in the repo; no maintainer engagement. |
|
snapcraft (launchpad) issue #1741091 |
Installing snapcraft (and its dependencies) | ~tanesh | 3173d | close stale | 95 | 75 | Reports a missing 'cd snapcraft' step in the HACKING.md install guide. Open 8+ years with zero comments, no labels, and no maintainer interaction; the referenced HACKING.md no longer exists at the repo root (docs restructured into docs/contribute/). |
|
snapcraft (launchpad) issue #1827217 |
create-key without a passphrase is not possible using multipass | ~0-luke | 2690d | close stale | 95 | 55 | 2018 report that snapcraft create-key cannot be run without a passphrase in a multipass VM: pressing return loops back to the confirm-password prompt. Open ~7.3 years with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #1627042 |
prime in nodejs plugin does work if used multiple times in one snapcraft.yaml | ~maarten-ectors | 3640d | close stale | 95 | 65 | nodejs plugin yields correct stage but wrong prime when two separate parts both use the plugin; a single part with multiple node-packages works. 10-year-old report, no labels, no maintainer activity. |
|
snapcraft (launchpad) issue #1774410 |
Having python3-netaddr as a stage package produces external symlink | ~bjornt | 3025d | needs triage | 95 | 55 | Specifying python3-netaddr as a stage-package in snapcraft 2.42 yields symlinks pointing outside the snap (to /var/lib/...), while build-packages give relative symlinks. Unlabelled, zero comments, no maintainer activity in ~8 years. |
|
snapcraft (launchpad) issue #1771767 |
File dispute not working | ~cprov | 3039d | close stale | 95 | 60 | 2017 report that filing a snap-name dispute via the register-name API returns an already_registered error instead of already_claimed. No labels, no comments, no maintainer activity for ~6 years; store integration has since been rewritten. |
|
snapcraft (launchpad) issue #1816858 |
Set snap name to a human readable name in store upload | ~sil | 2760d | close stale | 95 | 65 | Feature request to auto-derive a human-readable title (e.g. 'Adobe Photoshop') from the snap name during store upload. Open since 2018 with zero comments or maintainer engagement; the CLI no longer sets the store display name in modern snapcraft. |
|
snapcraft (launchpad) issue #1999038 |
"snapcraft release" chokes given an invalid revision value | ~rpjday | 1374d | close stale | 95 | 70 | Issue about confusing error when 'snapcraft release' receives invalid revision. Stale for 1366 days with no maintainer response. The release command appears to have been removed or deprecated. |
|
snapcraft (launchpad) issue #1743587 |
snapcraft push returns non exit zero code if snap requires manual review | ~serge-borovkov | 3160d | needs triage | 95 | 65 | snapcraft push returns non-zero exit code when a snap requires manual review despite successful upload; reporter expects zero exit code. Unlabeled, zero comments, inactive for over eight years. |
|
snapcraft (launchpad) issue #2008003 |
Multipass build provider does not support resource settings core core22 snaps | ~jocado | 1298d | close stale | 95 | 75 | Multipass build provider does not support resource settings (CPU/memory env vars) for core22 snaps. Untriaged, no maintainer response, 1290 days old. |
|
snapcraft (launchpad) issue #1770364 |
Using 2 remote parts, file not being copied from stage to prime | ~gerboland | 3046d | close stale | 95 | 55 | Snapcraft bug (2017): with two remote parts, a file staged by the xwayland-kiosk-helper remote part (lib/libxwayland-preload.so) is not copied into prime, while another file from the same part is. No maintainer response or activity in 8+ years. |
|
snapcraft (launchpad) issue #2041712 |
Can't use github account to upload a software to snapstore | ~yingshaoxo | 1050d | close stale | 95 | 65 | User requests GitLab/Bitbucket as alternative GitHub authentication for Snap Store after their GitHub account was banned. No maintainer response in 1042 days. |
|
snapcraft (launchpad) issue #2007479 |
speedx doesn't launch in ubuntu 22.04.1 | ~624wtl | 1304d | close not a bug | 95 | 80 | User reports speedx Qt application fails to launch on Ubuntu 22.04.1 due to missing wayland-egl plugin. Issue is 1295 days old with no maintainer response or comments. |