Showing 100 of 2042 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
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 #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 #2020138 |
Exclude architectures | ~ilya-fedin | 1212d | close stale | 95 | 65 | Feature request to add 'build-not-on' or architecture exclusion support in snapcraft YAML. Currently only whitelist (build-on/build-for) is available. Issue is 3+ years old with no maintainer response or activity. |
|
snapcraft (launchpad) issue #1849707 |
stage-snap causes issues when mixing cores | ~joeborg | 2514d | close stale | 95 | 65 | stage-snap staging a core16 snap into a core18 build overwrites the build environment and triggers file conflicts; reporter proposes a warning on core mismatch. No maintainer activity in ~6.8 years; core16/core18 are EOL. |
|
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 #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 #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 #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 #2028047 |
Calling snapcraft clean shouldn't load the project | ~gbeuzeboc | 1151d | needs triage | 95 | 30 | snapcraft clean loads project and plugins from host PYTHONPATH, causing crashes when host has conflicting Python modules. Issue is 1143 days old with no maintainer engagement. |
|
snapcraft (launchpad) issue #1668555 |
Using organize to move a folder to a child folder fails due to recursion | ~jamesh | 3482d | needs triage | 95 | 40 | Snapcraft organize directive causes infinite recursion when moving a folder into its own child path (e.g. '.': lib/python3.6/site-packages). Workaround via glob ('*') documented in issue. 9+ years old, zero comments, no labels, never triaged. |
|
snapcraft (launchpad) issue #1612741 |
Snapcraft go plugin install issues | ~josvaz | 3682d | needs triage | 95 | 60 | Snapcraft's go plugin fails to build godoc because go install writes to $GOROOT/bin (permission denied), a known golang bug; reporter also asks snapcraft to prevent installs into $GOROOT or force install path inside the snap. No labels, no comments, no maintainer activity in ~10 years. |
|
snapcraft (launchpad) issue #2019489 |
build fails pip update of pip setuptools wheel | ~kenneth-loafman | 1217d | close stale | 95 | 75 | Build fails when pip upgrade in venv breaks pkg_resources version resolution. Untriaged, 1209 days old, no maintainer response. |
|
snapcraft (launchpad) issue #1597075 |
ant plugin only looks for jar files in directory named "target" | ~jenny-murphy | 3727d | needs triage | 95 | 55 | Request to make the ant plugin's jar search directory configurable (hardcoded to 'target'). 10-year-old feature request with zero comments and no maintainer interaction; repo has since been heavily restructured. |
|
snapcraft (launchpad) issue #1897098 |
Trigger font cache rebuild if new fonts added to the system | ~igorljubuncic-deactivatedaccount | 2178d | close stale | 95 | 70 | Placeholder request (2019) to rebuild the font cache when new system/user fonts appear after a snap install. No labels, comments, or maintainer activity for ~6 years; desktop extensions now rebuild the cache via a configure-fonts hook. |
|
snapcraft (launchpad) issue #1862516 |
Missing items in LD_LIBRARY_PATH break numpy stage-packages | ~aglavic | 2406d | close stale | 95 | 70 | 2019 report that stage-packages python3-numpy fails at runtime because libblas/liblapack live in subdirectories not on the library search path; reporter found an LD_LIBRARY_PATH workaround. No labels, comments, or maintainer activity in 6.5 years. |
|
snapcraft (launchpad) issue #1863430 |
unhelpful failure message | ~jdstrand | 2400d | close stale | 95 | 70 | Snapcraft push shows only a CalledProcessError traceback when the review-tools check fails, hiding the actual review output. Unlabeled, zero comments, inactive ~5.7 years; the review-tools code path has since been removed from snapcraft. |
|
snapcraft (launchpad) issue #1917639 |
--debug drops me into an unexpected directory | ~racb | 2018d | needs triage | 95 | 55 | Snapcraft 4.5.1 --debug drops the user into /root instead of the override-stage script's working directory. Reported ~5.5 years ago, zero comments, no labels, no maintainer interaction. Related Launchpad bugs 1848513 (env vars) and 1848732 (snapcraftctl) still open. |
|
snapcraft (launchpad) issue #1886388 |
Parameterized builds are required for snapcraft build | ~muthiahn | 2259d | close stale | 95 | 65 | Feature request from 2018 to add parameterized builds to snapcraft so a git-source part can be built from different branches via a build parameter. No labels, no comments, no maintainer response in ~6 years; largely addressable today via environment variable substitution in snapcraft.yaml. |
|
snapcraft (launchpad) issue #1863961 |
completion /usr/lib/snapd/etelpmoc.sh error | ~casper-dcl | 2396d | close stale | 95 | 75 | Snapd's etelpmoc.sh completion wrapper fails inside a snap: /usr/share/bash-completion/bash_completion is missing, so tab completion breaks for the gh CLI on Ubuntu 16.04/snapd 2.43.2. Open ~6.5 years, no maintainer activity; bug is in snapd, not snapcraft. |
|
snapcraft (launchpad) issue #1865230 |
snapcraft --use-lxd should have message about requring sudo | ~haydenb | 2387d | close stale | 95 | 65 | snapcraft 3.x --use-lxd (LXD provider, a technology preview) left LXD in a broken state when run without sudo; reporter suggests failing early. 6.5 years old, zero comments, no labels or maintainer interaction; LXD preview since superseded by Multipass. |
|
snapcraft (launchpad) issue #2012074 |
snapcraft cannot build snap by default on aarch64 | ~gbeuzeboc | 1274d | close stale | 95 | 85 | snapcraft init defaults to core20 base which lacks arm64 Multipass images, causing build failures on aarch64. Fixed by PR #4118 which changed the default init base to core22. |
|
snapcraft (launchpad) issue #1865834 |
Snapcraft doesn't always copy the host's version into the VM | ~ken-vandine | 2384d | close stale | 95 | 60 | Snapcraft VM builds intermittently refresh snapcraft to stable channel instead of copying the host version, causing schema validation failures. 6.5 years old, 0 comments, no labels, no maintainer interaction. Related PRs #1364 and #1412 have been merged addressing host version injection and container refresh. |
|
snapcraft (launchpad) issue #1869030 |
Running several instances of snapcraft in parallel for a given snap name... | ~osomon | 2361d | close stale | 95 | 55 | Parallel snapcraft builds for the same snap name share a multipass VM, causing apt lock file conflicts. Feature request to allow unique VM/container names. 6.4 years old, zero comments, no labels, no maintainer interaction. |
|
snapcraft (launchpad) issue #1845276 |
snapcraft shouldn't complain about snap/README.md | ~anonymouse67 | 2544d | close not a bug | 95 | 62 | Request to stop snapcraft warning about snap/README.md as a non-snapcraft path so docs can live in the snap/ dir. 7 years old, zero comments, no labels or maintainer response; the warning is intentional and already documents the snap/local/ workaround. |
|
snapcraft (launchpad) issue #1820797 |
Snapcraft should allow prepending/appending additional text from description... | ~brlin | 2734d | needs triage | 95 | 65 | Feature request to let packagers prepend/append custom text (e.g. unofficial-snap disclaimers) to the description adopted via adopt-info. ~7.5 years old, no labels, no comments, no maintainer interaction; never triaged. |
|
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 #1627854 |
finalzed binary (step prime) are not stripped | ~servusoft | 3637d | close stale | 95 | 70 | Feature request from 2016 to add a --strip option to the prime step for stripping binaries with cross-compilation support. No maintainer engagement in ~10 years; no evidence the feature was implemented. |
|
snapcraft (launchpad) issue #1629910 |
init-plugin command for new plugin creation | ~jaymell | 3630d | close stale | 95 | 55 | Feature proposal for an 'init-plugin' command to scaffold new snapcraft plugins; opened ~10 years ago by an external contributor, zero comments, no PR submitted, no maintainer engagement, and it predates the current parts-based plugin architecture. |
|
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 #1651339 |
Add keyword maven-target to help of maven plugin | ~mtonnie | 3553d | close stale | 95 | 70 | Request to add the maven-targets keyword description to the maven plugin's help text; reported against snapcraft 2.23, no maintainer interaction, and the maven plugin has since moved to craft-parts. |
|
snapcraft (launchpad) issue #1642350 |
webbrowser-app silently being excluded from stage-packages | ~mterry | 3586d | close stale | 95 | 85 | Launchpad-generated unity8-session snap silently excluded webbrowser-app from stage-packages on xenial. 9+ years old, zero comments, no labels, no maintainer response. Xenial is EOL and unity8-session is no longer relevant to modern snapcraft. |
|
snapcraft (launchpad) issue #1649181 |
snapcraft search: 'ascii' codec can't encode character '\xae' in position... | ~liu-xiao-guo | 3561d | close stale | 95 | 60 | snapcraft search crashes with an 'ascii' codec error when a part description contains a non-ASCII character (e.g. ®). Reported against snapcraft 2.22.1 on a classic dragonboard; no maintainer response, labels, or activity for ~10 years. |
|
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 #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 #2004544 |
Rebuilding a Go project results in error "error obtaining VCS status" in... | ~saviq | 1317d | needs triage | 95 | 35 | Rebuilding a Go snap in LXD fails with VCS status error; unlabelled, no maintainer response, 1309 days old |
|
snapcraft (launchpad) issue #1999385 |
Removing a `package-repositories:` entry does not affect existing containers | ~saviq | 1369d | needs triage | 95 | 40 | Removing a package-repositories entry from configuration does not remove it from existing containers. Unlabelled, no maintainer response, 1361 days old. |
|
snapcraft (launchpad) issue #1987421 |
Add support for a version of `${shlibs:Depends}` to `snapcraft.yaml` | ~saviq | 1480d | needs triage | 95 | 60 | Feature request to add ${shlibs:Depends} shorthand for automatic staging of shared library packages. Untriaged, no maintainer response in 1470 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 #2002980 |
Unpredictable "passthrough" behaviour | ~ondrak | 1334d | close stale | 95 | 65 | Inconsistent passthrough behavior between snapcraft.yaml and gadget.yaml; untriaged, no activity for 1326 days |
|
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 #1861638 |
pip fails when project requirement result binary already exists | ~daveparrish | 2413d | needs triage | 95 | 55 | Snapcraft python plugin pip download fails on rebuild when a result binary already exists, because pip lacks --exists-action. Reporter included a patch and error trace; no maintainer response, no labels, 0 comments, ~6.5 years old. |
|
snapcraft (launchpad) issue #1965113 |
Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used | ~osomon | 1640d | close stale | 95 | 60 | Firefox snap fails to start in Xorg after Wayland session with 'cannot open display: :0' despite $DISPLAY being set. No maintainer response in 1632 days. |
|
snapcraft (launchpad) issue #1681692 |
Snap delta too large warning language can be improved | ~sabdfl | 3441d | close stale | 95 | 72 | Request to simplify the 'delta generated was too large' warning to a single line with an explicit threshold. Open 9+ years with zero comments and no maintainer interaction; the exact warning text no longer appears in the current codebase. |
|
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 #1858020 |
export-login --acls are not documented | ~abitrolly | 2445d | close stale | 95 | 55 | Documentation gap: snapcraft export-login --acls help text does not list valid ACL values (e.g. package_push vs package_upload). Open 6.7 years, zero comments, no labels, no maintainer interaction. |
|
snapcraft (launchpad) issue #1617565 |
'snapcraft plugins' should replace list-plugins and show a proper list | ~sabdfl | 3667d | close stale | 95 | 55 | Request to rename 'snapcraft list-plugins' to 'snapcraft plugins' and display each plugin's first description line. 10 years old, no labels or comments, no maintainer engagement; a related compact-list issue was resolved. |
|
snapcraft (launchpad) issue #1818017 |
Please support custom cloud-init config for Multipass VMs | ~brlin | 2753d | needs triage | 95 | 55 | Feature request to let snapcraft merge a user-supplied cloud-init config (e.g. custom apt mirror / disable-proposed) before initializing its Multipass VM. Open ~7.5 years with no labels, comments, or maintainer engagement; proposed as a workaround for Launchpad bug 1818016. |
|
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 #1621441 |
Need a way to delete account-keys from snapcraft integration tests | ~elopio | 3655d | needs triage | 95 | 70 | Request for a way to delete/disable store account-keys so the register-key integration test (added in PR #726) can run against real stores with fresh keys per run. Open since 2019, no labels, no comments, no maintainer response. |
|
snapcraft (launchpad) issue #1892551 |
snapcraft fails to run if it is installed as a try snap | ~anonymouse67 | 2212d | needs triage | 95 | 55 | Snapcraft 4.x fails when installed via 'snap try': the LXD build provider tries to download the host snapcraft snap file from snapd, which returns 400 for try snaps. Unlabelled, 0 comments, ~6 years old, never triaged. |
|
snapcraft (launchpad) issue #1795780 |
Snapcraft complains about "snapcraft.yaml~" in snap/ dir | ~jamesh | 2901d | close stale | 95 | 85 | Snapcraft warns about editor backup files like snapcraft.yaml~ in the snap/ directory, creating noise that can mask real problems. The issue has been open and unaddressed for 2890 days with no maintainer response. |
|
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 #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 #2002538 |
override-prime ignore failure on rebuild | ~gbeuzeboc | 1339d | close stale | 95 | 60 | Bug: override-prime step skipped after failure on rebuild, causing silent incorrect snap creation. Issue is 1331 days old with no maintainer engagement. |
|
snapcraft (launchpad) issue #1998269 |
Gnome extension breaks fontconfig for some applications | ~zoopgoop | 1382d | close stale | 95 | 70 | GNOME extension causes fontconfig failures in snap applications like Wine and Steam; issue is 1373 days old with no maintainer response or labels. |
|
snapcraft (launchpad) issue #1795642 |
Ignore vcs folders for `source-type: local` builds | ~saviq | 2901d | close stale | 95 | 50 | 2017 feature request to auto-ignore .git/.bazaar/.hg (or add a source-ignore key) for source-type: local builds. No labels, comments, or maintainer interaction for ~8 years; .snapcraftignore workaround noted in the issue itself. |
|
snapcraft (launchpad) issue #1768248 |
remote parts should be able to specify layouts | ~gerboland | 3055d | needs triage | 95 | 70 | Feature request to allow remote parts to specify layout options, motivated by an Xwayland kiosk helper use-case. Open since 2017 with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #1750581 |
Snapcraft’s own snap summary and description are unhelpful | ~mpt | 3125d | needs triage | 95 | 65 | Request to rewrite the snapcraft snap's store summary and description for clarity, grammar, and capitalization. 8.5 years old with zero comments, labels, or maintainer interaction; current store listing state unverified. |
|
snapcraft (launchpad) issue #1739954 |
DNS error causes cascading exception failure | ~rogpeppe | 3183d | close stale | 95 | 70 | Snapcraft 2.34 push dumps a raw urllib3/requests traceback (ending in a Retry TypeError) on DNS failure instead of a friendly error. 8.7 years old, no comments or labels; affected version and storeapi code long since replaced. |
|
snapcraft (launchpad) issue #1665003 |
Poor message when failing to specify a valid version | ~facundo | 3495d | close stale | 95 | 70 | Legacy snapcraft CLI showed a confusing error ('register ... before trying to release or choose an existing revision') when releasing a snap without a registered version. Reported ~9.5 years ago; no maintainer response; the current craft-based codebase no longer contains that message. |
|
snapcraft (launchpad) issue #1675513 |
Snap builds on arm are extremely slow causing them to fail | ~pat-mcgowan | 3459d | close stale | 95 | 60 | 2016 report that arm snap builds on Launchpad took hours and timed out, suspected network throttling. Tagged 'cache' but never discussed; 0 comments and no activity for ~9.4 years. |
|
snapcraft (launchpad) issue #1681152 |
snap may execute host, not wrapped, executables | ~cgull | 3443d | close stale | 95 | 72 | Classic-confinement snap wrappers in /snap/bin may execute host executables instead of the snap's wrapped ones due to PATH resolution. Reported 2017, no maintainer interaction, no labels. Workaround (snapcraft-runner) merged in PR #2889. |
|
snapcraft (launchpad) issue #1990126 |
"snapcraft help <plugin>" fails with SC7 and core22 in project directory | ~rpjday | 1454d | needs triage | 95 | 65 | snapcraft help <plugin> validates snapcraft.yaml unnecessarily, failing when core22 extensions are used. Untriaged, 1445 days old, no maintainer engagement. |
|
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 #1763048 |
Snap names regexes are inconsistent or too permissive | ~adam-collard | 3075d | needs triage | 95 | 65 | Snap name regexes across the store, click-reviewers-tools, and snapd are inconsistent or too permissive (allowing one-char names, leading/trailing dashes, double dashes); snapcraft itself does not enforce a regex. No maintainer response in ~7 years. |
|
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 #1796802 |
PKG_CONFIG_PATH during build step should include multiarch paths | ~brlin | 2895d | needs triage | 95 | 60 | Snapcraft build step sets PKG_CONFIG_PATH to only $SNAPCRAFT_STAGE/lib/pkgconfig, missing multiarch lib/<triplet>/pkgconfig paths, so .pc files installed there are not found by later parts. Unlabelled, zero comments, ~8 years old. |
|
snapcraft (launchpad) issue #1983826 |
Snapcraft 7.1.1 gives vague error when it can't process package | ~koen-vervloesem | 1496d | close stale | 95 | 55 | Snapcraft 7.1.1 returns a vague 'Service unavailable' error when snap upload processing fails, making it hard for users to diagnose the root cause. No maintainer response or labels; issue is 4 years old. |
|
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 #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 #2017771 |
apt update failure during core22 destructive-mode pulls | ~suligap | 1234d | needs triage | 95 | 60 | apt update fails during core22 destructive-mode pulls for non-root users, reported as regression from core20. No maintainer response or labels after 1226 days. |
|
snapcraft (launchpad) issue #2028686 |
snapcraft pack failure from git worktree | ~dbungert | 1144d | close stale | 95 | 60 | snapcraft pack fails when building from a git worktree. Issue is 1136 days old with no labels, no comments, and no maintainer engagement. |
|
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 #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 #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 #1989030 |
snapcore/snapcraft image is outdated (again) | ~ianconsolata | 1465d | needs triage | 95 | 70 | Report that snapcore/snapcraft Docker images are outdated, claiming automation to keep them updated may be broken. Issue is 4 years old with no maintainer response or labels. |
|
snapcraft (launchpad) issue #1989248 |
Displaying plugins formats output differently for core20 v core22 | ~rpjday | 1462d | 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 #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 #1640721 |
Feature Request: Would be nice to have a way to refresh .deb files | ~aacid | 3592d | close stale | 95 | 70 | Feature request to refresh only changed .deb files in a snap build instead of re-downloading the full ~300MB set. Open since 2017 with no labels, comments, or maintainer activity. |
|
snapcraft (launchpad) issue #1841618 |
snapcraft should run apt-get update | ~abitrolly | 2572d | needs triage | 95 | 60 | Feature request (2019) for snapcraft to refresh stale apt-get caches in process containers to avoid build failures. Open ~7 years with zero comments, no labels, no maintainer response; no general cache-refresh logic found in the build path. |
|
snapcraft (launchpad) issue #1637563 |
Add ability to automatically fetch Recommends from (a subset of) stage packages | ~3v1n0 | 3605d | needs triage | 95 | 55 | Feature request for a stage-packages-with-recommends flag so snap Recommends are auto-fetched from stage packages instead of listed manually. Open ~10 years with no labels, comments, or maintainer interaction. |
|
snapcraft (launchpad) issue #1636233 |
Add support for compiler flags in autotools plugin | ~ivan-lezhnjov-iv | 3609d | needs triage | 95 | 60 | Feature request to add compiler flag support (cflags) to the autotools plugin, similar to configflags, needed for packaging PostgreSQL with flags like -fPIC -pie and mit-krb5 paths. No maintainer response, no labels beyond 'plugin', and no activity in ~10 years. |
|
snapcraft (launchpad) issue #1634803 |
snapcraft register-key doesn't use U1 SSO login credentials | ~vrruiz | 3614d | close stale | 95 | 60 | register-key re-prompts for U1 SSO credentials even after a successful snapcraft login, tested on snapcraft 2.19. ~10 years old, unlabelled, 0 comments, no maintainer activity; a near-identical Launchpad bug is also open. |
|
snapcraft (launchpad) issue #1629978 |
create-key prints no progress | ~elopio | 3630d | needs triage | 95 | 70 | snapcraft create-key prints no progress output and can appear stuck while collecting entropy; issue is open, unlabelled, and has no maintainer response. |
|
snapcraft (launchpad) issue #1822910 |
GitKraken fails with XAUTHORITY error (Ubuntu 18.10) | ~william-full-moon | 2719d | close stale | 95 | 70 | GitKraken snap fails to launch on Ubuntu 18.10 with an XAUTHORITY warning and a user-data-directory error; reporter asks for a configurable snap home path. Unlabeled, zero comments, no maintainer activity in ~7 years; the failure is snapd/app-side, not snapcraft. |
|
snapcraft (launchpad) issue #1824473 |
Changed stage-snaps property does not make pull step dirty | ~brlin | 2710d | needs triage | 95 | 55 | Snapcraft bug: changing a part's stage-snaps property does not mark the pull step dirty, so re-running stage skips pull and crashes. Reported ~7.4 years ago with a POC repo; no maintainer response, no labels, zero comments. |
|
snapcraft (launchpad) issue #1735410 |
Localization support | ~mkljczk | 3207d | close stale | 95 | 70 | Request to implement localization (l10n) support in Snapcraft, filed by an external contributor who offered to take it on. Open ~8.7 years with zero comments, no maintainer response, and no evidence of any l10n work in the codebase. |
|
snapcraft (launchpad) issue #1636238 |
make plugin fails to include a Makefile via a relative path from another Makefile | ~ivan-lezhnjov-iv | 3609d | close not a bug | 95 | 55 | make plugin fails to build PostgreSQL contrib because its Makefile includes ../src/Makefile.global, which lies outside the declared source directory. 10 years old, zero comments, no maintainer response. Failure stems from user source config, not a plugin defect. |
|
snapcraft (launchpad) issue #1976290 |
extension files get repeated over and over each time snapcraft is recreated | ~rastersoft-gmail | 1565d | close stale | 95 | 65 | 2021 report that rebuilding a snap with a modified gnome extension without cleaning duplicates python3.8 build/lib artifacts in the squashfs, growing the snap size each rebuild. Zero comments, no maintainer response, and the python3.8-era in-repo extension setup is long outdated. |
|
snapcraft (launchpad) issue #1849092 |
[Errno 17] File exists: 'libbsd.so.0.8.2' ->... | ~winwisely99 | 2517d | close stale | 95 | 70 | Snapcraft 3.8 staging crash: FileExistsError linking libbsd.so.0 into stage after an I/O error on os.link, reported from a Docker build. No maintainer activity for ~7 years; the affected code paths no longer exist in modern snapcraft. |
|
snapcraft (launchpad) issue #1848732 |
--shell does not make snapcraftctl available | ~racb | 2520d | close stale | 95 | 72 | 2019 report that `snapcraft pull --use-lxd --shell` leaves `snapcraftctl` unavailable in the LXD shell. No labels, comments, or maintainer activity for about 6 years. snapcraft 2.x/3.x removed snapcraftctl, so the report is outdated. |
|
snapcraft (launchpad) issue #1666366 |
Need --autoclean or similar | ~michihenning | 3490d | close stale | 95 | 60 | Feature request for an --autoclean option to auto-clean stale parts when a dependency's step needs re-running. 9.5 years old, zero comments, no labels; the legacy parts system it targets was replaced by craft-parts in snapcraft 2.0+. |
|
snapcraft (launchpad) issue #1850921 |
Python plugin: file conflicts when using the plugin with a custom version of... | ~ntamas | 2506d | close stale | 95 | 70 | Snapcraft 2.44 Python plugin bundles default Python 3.5 when a custom Python 3.7 is built in another part, causing file conflicts. Root cause: stage_packages evaluated too early. No maintainer response; predates Snapcraft 3.x which uses craft-parts venv-based Python plugin without stage_packages. |
|
snapcraft (launchpad) issue #1586400 |
Snap type: change from "os" to "core" | ~kyrofa | 3759d | close stale | 95 | 70 | Request to rename snapd's 'os' snap type to 'core' to avoid ambiguity on classic systems. 10+ years old with zero comments; the rename has since been implemented in snapd (core snap is now type 'core'), so the issue is moot. |
|
snapcraft (launchpad) issue #1613779 |
go plugin ignores the source-subdir keyword | ~jgrimm | 3678d | close stale | 95 | 80 | Go plugin (snapcraft 1.x) ignored source-subdir, symlinking GOPATH to git root instead of the subdirectory. 10 years old, 0 comments, no maintainer interaction. The GOPATH-symlink approach and go-importpath key no longer exist in the modern go plugin. |
|
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 #1851905 |
Unable to build with lxd when using lxd with lvm pool. | ~extraymond | 2499d | close stale | 95 | 70 | Snapcraft 3.8/3.9.2 fails with --use-lxd when LXD uses a custom LVM pool, due to a hardcoded /var/snap/lxd/common path. 6+ years old, no labels, no maintainer interaction, no comments. |
|
snapcraft (launchpad) issue #1670146 |
QMake plugin should allow specifying custom Qt paths | ~tim-sueberkrueb | 3477d | close stale | 95 | 55 | Feature request to let the QMake plugin point at a custom Qt installation newer than Ubuntu's archives. Open ~9.5 years, zero comments, no labels, never triaged; the project later added the qbs plugin as the modern Qt build path. |
|
snapcraft (launchpad) issue #1852329 |
appstream parsing fails when comments exist | ~ken-vandine | 2495d | needs triage | 95 | 50 | Snapcraft fails to parse the appstream description when translator comments are present in the metainfo XML. Unlabelled, zero comments, no maintainer interaction, inactive for ~6.8 years. |
|
snapcraft (launchpad) issue #1982420 |
libdevmapper-dev fails to install as build-package using snapcraft:core20 (Multipass) | ~nuccitheboss | 1514d | close stale | 95 | 55 | core20 snap build in Multipass fails installing libdevmapper-dev build-package because the build instance apt upgrade pulls from focal-backports, then sources revert to main, leaving unmet version dependencies. No maintainer activity in ~3.5 years. |