Issue & PR triage
Loading...
Showing 100 of 646 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
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 | 3438d | 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 #1624854 |
"Developer has not signed agreement" when run snap push | ~psivaa | 3646d | 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 #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 #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 #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 #1666161 |
Can’t dry-run a build to check snapcraft.yaml | ~mpt | 3491d | 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 #1693451 |
Support CircleCI for building | ~popey | 3397d | 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 #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 #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 #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 #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 #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 #1617052 |
snapcraft: do not suppress ImportErrors for top-level exceptions with local plugins | ~nacc | 3669d | close stale | 95 | 55 | Request to stop snapcraft from masking ImportErrors when loading local plugins, so top-level import failures (wrong filename or parent plugin name) surface instead of 'unknown plugin'. 10 years old, no labels, no comments, no maintainer activity. |
|
snapcraft (launchpad) issue #1634038 |
Snapcraft should verify namespace before uploading | ~joetalbott | 3617d | close stale | 95 | 60 | Feature request from 2016 asking snapcraft to verify the user's namespace before uploading, to avoid expensive post-upload failures. Open for ~10 years with zero comments, no labels, and no maintainer interaction. |
|
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 #1771767 |
File dispute not working | ~cprov | 3040d | 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 #1771778 |
Inconsistent parameter syntax | ~popey | 3040d | 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 #1772885 |
dropping privs did not work: No data available | ~edo.red | 3034d | 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 #1667318 |
Add Track information to 'status', 'close', and 'revisions' output | ~joetalbott | 3487d | close stale | 95 | 65 | Feature request to add track information to snapcraft status, close, and revisions command output. Filed ~9.5 years ago by external contributor with zero comments, no labels, and no maintainer interaction. |
|
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 #1778530 |
rust plugin. failed build with RUST ver. 1.27 | ~general-beck | 3000d | close stale | 95 | 65 | Snapcraft rust plugin fails with Rust 1.27: 'could not execute process rustc -vV (never executed)'; 1.26.2 works. 8 years old, zero comments, no maintainer response. The plugin has since been substantially rewritten. |
|
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 #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 #1652441 |
unity7: LauncherEntry API does not work due to snapd not respecting the... | ~mvo | 3549d | 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 #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 #1995895 |
Cannot override stage | ~jardon | 1404d | close stale | 95 | 50 | Snapcraft pack fails with FileNotFoundError during prime step when using override-stage. Open for 3.8 years with no maintainer engagement. |
|
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 #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 #1826748 |
python: Errors regarding to the missing `--single-version-externally-managed` option | ~brlin | 2693d | close stale | 95 | 60 | Python plugin build fails because it passes the deprecated --single-version-externally-managed flag to setup.py, which newer setuptools rejects. 7+ years old, unlabelled, no maintainer response; reporter used a custom plugin workaround. |
|
snapcraft (launchpad) issue #1848038 |
HACKING.md does not explain how to run snapcraft from a source tree | ~racb | 2524d | close stale | 95 | 70 | Request for HACKING.md to document running snapcraft from a source tree so code changes take effect. ~7 years old, 0 comments, no labels; the root HACKING.md no longer exists - docs were restructured into docs/contribute/. |
|
snapcraft (launchpad) issue #1666160 |
Can’t distinguish programmatically between snapcraft.yaml errors and other errors | ~mpt | 3491d | close stale | 95 | 60 | 2016 feature request for programmatic error codes distinguishing snapcraft.yaml validation failures from other build errors, so build.snapcraft.io could attach yaml errors to its UI. No labels, no comments, no maintainer activity for ~9.5 years. |
|
snapcraft (launchpad) issue #1999038 |
"snapcraft release" chokes given an invalid revision value | ~rpjday | 1375d | 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 #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 #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 #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 #1617253 |
snapcraft syntax documentation is incomplete | ~rogpeppe | 3669d | close stale | 95 | 72 | 10-year-old report that snapcraft.yaml syntax docs omitted app-level plugs. Docs have since been fully restructured into docs/reference/ (58 files); the old URL paths no longer exist. No maintainer interaction, zero comments. |
|
snapcraft (launchpad) issue #1617346 |
Need richer autotools control | ~stub | 3668d | close stale | 95 | 60 | Feature request from 2015 asking the autotools plugin to support overriding make steps (e.g. make world, install-world) for a custom build pipeline. No maintainer response or labels; a similar Launchpad bug (1619912) requesting make-targets remains open. |
|
snapcraft (launchpad) issue #1591565 |
go plugin is not striping the .git from the source | ~elopio | 3744d | close stale | 95 | 75 | 2015 bug report: the legacy go parts plugin does not strip the .git suffix from source URLs, so go get targets the wrong package path (e.g. ./cli.git/...). No labels, no comments, inactive ~9.5 years; the go plugin no longer exists in modern snapcraft. |
|
snapcraft (launchpad) issue #1681861 |
classic snaps recurse | ~chris.macnaughton | 3440d | close stale | 95 | 72 | Classic snap command wrappers generated by snapcraft use bare command names instead of $SNAP/bin/command paths, causing failures since PATH is not reset in classic confinement. 3429 days old, no labels, no comments, no maintainer interaction. |
|
snapcraft (launchpad) issue #1856242 |
Python plugin: ship pyc files only | ~om26er | 2465d | close stale | 95 | 70 | Feature request to make the Python plugin ship only .pyc files (removing .py) to reduce snap size. Open since 2019, unlabelled, zero comments, no maintainer activity. The current craft-parts python plugin v2 no longer bytecompiles, so the premise is outdated. |
|
snapcraft (launchpad) issue #1940830 |
snapcraft remote-build fails in Windows when using a \\wsl$ path | ~lucyllewy | 1846d | close stale | 95 | 70 | snapcraft remote-build on Windows crashes with a ValueError when the project lives on a \\wsl$ mount, because link_or_copy_tree calls ntpath.relpath across different mounts. Old snapcraft 7.x code path; no maintainer activity in ~5 years. |
|
snapcraft (launchpad) issue #1946406 |
snapcraftcontent.com shows certificate error | ~steve010 | 1800d | close stale | 95 | 70 | Revoked SSL certificate on canonical-bos01.cdn.snapcraftcontent.com broke automated snap downloads. Open ~5 years with zero maintainer interaction; a similar CDN cert issue was resolved externally by Canonical renewing certificates. |
|
snapcraft (launchpad) issue #1947914 |
concurrent snapcraft builds with multipass provider | ~geekorous | 1787d | close stale | 95 | 60 | Concurrent snapcraft builds with the multipass provider assign all instances the same IPv4, aborting builds with no debug info. No labels, comments, or maintainer activity in ~4.8 years; targets snapcraft 5.0 on EOL Ubuntu 18.04/20.04. |
|
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 #1711333 |
snaps must have accompanying source available | ~jr | 3313d | close stale | 95 | 60 | 9-year-old policy proposal requiring snap developers to upload source code for licensing compliance. Zero comments, no labels, no maintainer interaction. Never triaged or acted upon. |
|
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 #1981072 |
Core22 Snap builds don't output error logs | ~farshidtz | 1527d | close stale | 95 | 70 | Core22 snap builds don't output error logs to stdout/stderr on Launchpad, making debugging difficult. Issue is 4 years old with zero maintainer engagement. |
|
snapcraft (launchpad) issue #1987853 |
snapcraft terminates override-build script prematurely without error | ~nicolasbock | 1477d | close stale | 95 | 85 | Snapcraft prematurely terminates override-build scripts after core18 to core20 upgrade, with no error output. Untriaged and inactive for over 4 years. |
|
snapcraft (launchpad) issue #1989248 |
Displaying plugins formats output differently for core20 v core22 | ~rpjday | 1463d | close stale | 95 | 75 | Inconsistent formatting of `snapcraft plugins` output across core18, core20, and core22 bases. Issue is 1454 days old with no maintainer engagement or labels. |
|
snapcraft (launchpad) issue #1990298 |
fatal: detected dubious ownership in repository at '/root/project' when ran... | ~saviq | 1452d | close stale | 95 | 75 | snapcraft --use-lxd fails with Git dubious ownership error when using version: git. Issue is 4 years old with no maintainer interaction. |
|
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 #2015327 |
Files in path to snapcraft.yaml are excluded in source directive | ~kian-parvin | 1256d | close stale | 95 | 85 | Bug report about files in the source path being excluded when using source: ../.. in snapcraft.yaml. Open for over 3 years with no activity or maintainer response. |
|
snapcraft (launchpad) issue #1638508 |
API package creation from the stage | ~bzoltan | 3601d | 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 #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 #1752576 |
tests.unit.test_lifecycle.CoreSetupTestCase.test_core_setup_if_docker_env fails | ~kalikiana | 3117d | close stale | 95 | 70 | 2017-era snapcraft unit test failure: test_lifecycle CoreSetupTestCase regex expected bare 'unsquashfs' but code emits full /snap/snapcraft path. No labels, no comments, no maintainer response in 8.5 years; referenced test no longer exists in the modern codebase. |
|
snapcraft (launchpad) issue #1800659 |
"Writing more data than expected" while snapping an ros project | ~ghost069 | 2874d | close stale | 95 | 75 | User on snapcraft 2.43.1 hit an apt FetchError ('Writing more data than expected') pulling catkin/ROS deps. No maintainer response in ~8 years; the error is an apt cache/mirror issue and the affected version is long EOL. |
|
snapcraft (launchpad) issue #1576289 |
image loaders (gdkpixbuf) not easy to integrate | ~seb128 | 3788d | close stale | 95 | 85 | Feature request to automate gdk-pixbuf loader integration in snaps. Now implemented via desktop extensions: desktop-exports sets GDK_PIXBUF_MODULE_FILE/MODULEDIR and regenerates the cache. 0 comments, no maintainer activity in ~9 years. |
|
snapcraft (launchpad) issue #1847321 |
Snap with python3 + tkinter crashes with SEGFAULT | ~eikekuehn42 | 2530d | close stale | 95 | 45 | Snap built with python3 + tkinter segfaults when creating a tkinter Label; minimal repro repo provided. No comments or maintainer activity for ~6.4 years; the original build stack is long out of support. |
|
snapcraft (launchpad) issue #1703471 |
$SNAP/usr/local/bin should be on the $PATH | ~ev | 3350d | close stale | 95 | 55 | Request to add $SNAP/usr/local/bin to the PATH in snap command-*.wrapper files, since autotools defaults to that prefix. Open ~9 years with no labels, comments, or maintainer interaction. |
|
snapcraft (launchpad) issue #1740500 |
"The name <foo> is already taken" is a poor experience | ~popey | 3179d | close stale | 95 | 80 | UX complaint that the 'The name <foo> is already taken' error from snapcraft register is off-putting and discourages new users from claiming a name they legitimately own. 8+ years old, no maintainer response, and the register command/prompt has since been removed from current snapcraft. |
|
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 #2099923 |
Snapcraft builds are failing: install of snap "snapcraft" failed | ~snawoot | 564d | close stale | 95 | 80 | Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response. |
|
snapcraft (launchpad) issue #1903046 |
Progressive release stops showing metrics when set to 100% target | ~noise | 2137d | 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 #1608932 |
multiple parts with same git repo makes build checkout out redundant repos | ~adam-stokes | 3693d | 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 #1749699 |
Delta error is shown on first push, can be avoided? | ~facundo | 3131d | 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 #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 #1646546 |
snapcraft packages .so from /usr instead of from .deb | ~aacid | 3571d | close stale | 95 | 60 | 2016-era report that snapcraft picked up .so files from the host /usr instead of from .deb packages, so snap contents depended on the host system. No maintainer response or labels. Likely obsolete since snapcraft now builds inside a confined core base. |
|
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 #1681722 |
classic snaps cannot find stage packages in $PATH | ~stub | 3441d | 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 #1695081 |
autotools plugin should support explicit autogen or autoreconf | ~sabdfl | 3389d | close stale | 95 | 70 | Feature request (2015) for the autotools plugin to support explicit autogen/autoreconf steps. No comments or labels; core request since implemented in the autotools v2 plugin via autogen.sh and bootstrap support (PR #3398). |
|
snapcraft (launchpad) issue #1709060 |
Trouble allocating fonts in a Tcl/Tk (Python 3.5) based snap | ~kushalchauhan98 | 3323d | close stale | 95 | 75 | Tcl/Tk font allocation error when running a Python 3.5 tkinter snap built with snapcraft 2.33. No maintainer interaction; issue is 9 years old with zero comments. |
|
snapcraft (launchpad) issue #1948597 |
TypeError: load() missing 1 required positional argument: 'Loader' | ~kenneth-loafman | 1783d | close stale | 95 | 80 | Snapcraft 2.43.1 crashes during snap build with PyYAML TypeError (load() missing Loader) in internal/states/_state.py. No maintainer interaction for ~4.5 years; the affected code path no longer exists in the current codebase. |
|
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 #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 #1638840 |
snapcraft copies /etc/apt/sources but ignores /etc/apt/preferences | ~aacid | 3600d | close stale | 95 | 70 | Snapcraft copies /etc/apt/sources but ignores /etc/apt/preferences, causing wrong package selection in complex setups. 9.8 years old, zero comments, no labels, no maintainer interaction. Current codebase uses craft-archives with AptPreferencesManager, a completely different architecture. |
|
snapcraft (launchpad) issue #1758859 |
'snapcraft push' dies with traceback if credentials are invalid | ~romain-janvier | 3092d | close stale | 95 | 72 | snapcraft push crashes with UnicodeDecodeError traceback on invalid credentials, reported in 2018 via Travis CI for CloudCompare; no labels, no comments, no maintainer interaction in 8+ years. |
|
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 #1600035 |
no way to differentiate between build-time and run-time env vars in plugins | ~thomir-deactivatedaccount | 3718d | close stale | 95 | 65 | Feature request to differentiate build-time vs run-time environment variables in plugin BasePlugin.env() method. Issue is 10 years old with no maintainer engagement or comments. |
|
snapcraft (launchpad) issue #1869604 |
Fails to realize the source folder changed with Multipass | ~saviq | 2357d | close stale | 95 | 50 | Bug where building the same project from different source folders reuses the previous Multipass instance instead of creating a new one. 6+ years old with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #1908061 |
gnome-3-34 extension is missing libraries | ~christianrauch | 2098d | close stale | 95 | 70 | gnome-3-34 snap extension missing harfbuzz, causing a pango symbol lookup error (hb_buffer_set_invisible_glyph) in built snaps. Open ~5.7 years, zero comments, no maintainer response; extension is deprecated. |
|
snapcraft (launchpad) issue #1856594 |
Snapcraft tutorial errors out on OSX with multipass error, "returned exit code 2" | ~dobsorg | 2461d | close stale | 95 | 70 | Dec 2019 report: snapcraft 3.9 on macOS fails via multipass (apt 404s, mount exit code 2) and crashes with AttributeError on os.sched_getaffinity. No maintainer activity; that code path no longer exists in current snapcraft, and macOS support was dropped. |
|
snapcraft (launchpad) issue #1921950 |
Can't build simple snap, maybe because of missing kmod arp_tables | ~paddor | 1991d | close stale | 95 | 80 | User's snapcraft 4.6 build stalls after snapcraftctl build; host KVM kernel lacks the arp_tables module needed by multipass networking, plus unrelated store 403 and polkit errors. Untriaged, 0 comments, ~5.4 years old, on long-EOL versions. |
|
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 #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 #1770364 |
Using 2 remote parts, file not being copied from stage to prime | ~gerboland | 3047d | 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. |
|
charmcraft issue #1096 |
Spread tests should ensure that juju can correctly parse the output. | lengau | 1236d | close stale | 95 | 70 | Feature request to install juju on spread test runners so tests can verify juju can parse the built charm/bundle output. No labels, no comments, no activity in ~3.4 years; bundle support was later removed from charmcraft. |
|
snapcraft (launchpad) issue #1771218 |
Could not execute process 'rustc -vV' (never executed) | ~mmacedoeu | 3042d | close stale | 95 | 85 | Travis CI build failing to locate rustc after installation. Issue is 8+ years old with zero comments or maintainer activity. The project has since migrated to GitHub Actions, making the Travis integration referenced here obsolete. |
|
snapcraft (launchpad) issue #1794727 |
node plugin doesn't run yarn install during build | ~lucyllewy | 2907d | close stale | 95 | 85 | Nodejs plugin yarn support bug from 8 years ago; the nodejs plugin has been removed and replaced by the npm plugin which only supports npm, so the reported yarn install issue is no longer applicable to the current codebase. |
|
snapcraft (launchpad) issue #1795430 |
build-package "on amd64 to armhf" seems to be not working | ~mvo | 2902d | close stale | 95 | 70 | Cross-building with build-on/run-on architecture grammar does not install the specified build-packages (e.g. gcc-arm-linux-gnueabihf) unless an explicit --target-arch is passed. Reported in 2018, no maintainer interaction, zero comments. |
|
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 #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 #1823512 |
`snapcraft --shell` shouldn't run the lifecycle steps | ~brlin | 2715d | close stale | 95 | 60 | Bug report claiming `snapcraft --shell` runs lifecycle steps instead of dropping into the build environment shell. 7+ years old, 0 comments, no labels; the `--shell` flag was removed in the modern CLI and `snapcraft shell` now provides the requested behavior. |
|
snapcraft (launchpad) issue #1825797 |
cmake: Shouldn't use sourcedir for building | ~brlin | 2700d | close stale | 95 | 85 | Request for cmake plugin to use out-of-source builds (build in SNAPCRAFT_PART_BUILD instead of SNAPCRAFT_PART_SRC). 2689 days old, no labels, no comments, no maintainer interaction. The current craft-parts cmake plugin already implements out-of-source builds via get_out_of_source_build() returning True. |
|
snapcraft (launchpad) issue #1995293 |
no uid/gid mappings when building on core22 with multipass | ~andreitoterman | 1411d | close stale | 95 | 60 | Multipass build with core22 mounts project directory without uid/gid mappings, causing ownership issues |
|
snapcraft (launchpad) issue #1798881 |
patchelf fails on i386 vscode | ~popey | 2884d | close stale | 95 | 60 | i386 vscode snap build fails because patchelf 0.9 cannot patch the 32-bit ELF (virtual address space underrun); no maintainer response, unlabelled, ~7.5 years old. |
|
snapcraft (launchpad) issue #1992557 |
snapcraft remote-build snapcraft.yaml validation too strict | ~fnordahl | 1431d | close stale | 95 | 55 | snapcraft remote-build validation rejects empty LD_LIBRARY_PATH in environment, blocking some classic snaps. Issue is 4 years old with no maintainer engagement. |