Issue & PR triage
Loading...
Showing 37 of 37 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft issue #6017 |
XKB_CONFIG_ROOT pointing to non-existent directory in kde-neon-6/kde-neon-qt6 | RealLucioCarreras | 266d | needs triage | 68 | 82 | 29 | Untriaged core24 KDE Neon extension bug: XKB paths resolve to absent runtime directories, causing an xkbcommon error and Sayonara segfault; current code retains the invalid exports. |
|
snapcraft issue #5721 |
Failed to pull source: unable to determine source type of... | jkbeg | 434d | needs triage | 60 | 94 | 35 | Snapcraft's 8_core22 container resolves extension data under /usr/share while the image installs it in site-packages, breaking ROS 2 builds; the path mismatch remains in current code. |
|
snapcraft issue #6497 |
kernel plugin: /proc/version_signature is empty for kernels built from... | canonical-nicoharnois | 14d | needs triage | 60 | 80 | 34 | Kernel plugin leaves CONFIG_VERSION_SIGNATURE empty when building from Ubuntu kernel source with flavour config. Reporter has a patch ready. |
|
snapcraft issue #4658 |
File permissions leak through to built snap | samuelallan72 | 961d | needs triage | 58 | 87 | 24 | A restrictive host umask can preserve inaccessible source modes in built snaps, reproducing an OpenStack runtime PermissionError; the report remains untriaged and unresolved. |
|
snapcraft issue #4587 |
Improvements to the PythonPlugin for core24 | tigarmo | 986d | needs triage | 58 | 55 | 12 | Core24 Python-plugin support merged in #4666, but the proposed interpreter-symlink and default-shebang linters plus broader Python/GNOME integration work remain open and untriaged. |
|
snapcraft issue #6299 |
Snapcraft upload+release not capturing review error | farshidtz | 129d | needs triage | 55 | 68 | 17 | snapcraft upload --release prints "Revision N created ... and released to ..." even when store review failed ("Status: error while processing"), leaving the revision in no channel. Two examples given; no maintainer response yet. |
|
snapcraft issue #6064 |
Extend advanced grammer to all keys of snapcraft | soumyaDghosh | 248d | needs triage | 55 | 70 | 12 | Advanced grammar remains limited to selected keys, limiting clean architecture-specific apps, part omission, and plugin parameters. The feature is untriaged; plugin-parameter support is tracked in craft-application #985. |
|
snapcraft issue #4935 |
snapcraft cannot connect through a transparent SSL proxy | ghost | 827d | needs triage | 55 | 76 | 22 | Snapcraft 7.5.5/8.3.1 was reported to reject a system-trusted MITM proxy CA for host commands such as whoami; it remains untriaged and unanswered. |
|
snapcraft issue #4569 |
pkg-config based project don't work with kde-neon extension | chubinou | 995d | needs triage | 55 | 90 | 25 | An exact core22 reproducer shows kde-neon no longer exposes Qt5 .pc files to pkg-config; the unlabelled report remains untriaged, and current extension code still omits PKG_CONFIG_PATH. |
|
snapcraft issue #5128 |
KDE Neon 6 broken on arm64 | waveform80 | 741d | needs triage | 52 | 79 | 12 | Reported arm64 kde-neon-6 failure caused by an incomplete kf6-core22 content snap; the issue remains unlabelled and untriaged despite a later related upstream fix. |
|
snapcraft issue #5842 |
Linting about execstack in libraries | soumyaDghosh | 372d | needs triage | 52 | 68 | 23 | Snapcraft’s library linter does not report executable stacks in shared libraries, although Store review can block upload; ELF detection exists, but no linter check or maintainer triage is present. |
|
snapcraft issue #5942 |
LXD device gets corrupted when ssh connection is closed | soumyaDghosh | 305d | needs triage | 52 | 76 | 16 | Untriaged LXD resume failure after SSH disconnect or VM restart: the existing disk device points to a vanished /run/user path. No maintainer response or resolution is recorded. |
|
snapcraft issue #5116 |
Add authentication support to apt repositories | cparich | 744d | needs triage | 50 | 60 | 14 | Add auth.conf.d-style credentials to apt package-repositories; unresolved, unlabelled feature request with no maintainer response and an open craft-archives counterpart. |
|
snapcraft issue #6463 |
docs: Please document best practices for building snaps for all... | julian-klode | 27d | needs triage | 50 | 60 | 14 | Documentation request for best practices on building snaps across all architectures (e.g. seeded snaps), covering remote-build vs Launchpad recipes and edge/beta/stable channel and tag strategies. Unassessed by maintainers. |
|
snapcraft issue #4310 |
Please include .*.hmac files by default in stage and prime | xnox | 1179d | needs triage | 48 | 68 | 25 | FIPS kernel HMAC sidecars are omitted by the default stage and prime filesets; this open, unlabelled request has had no maintainer activity. |
|
snapcraft issue #4578 |
SSH key password prompt doesn't appear when cloning repositories | dilyn-corner | 989d | needs triage | 48 | 77 | 16 | SSH passphrase prompts during Git pulls are overwritten by transient progress output at brief/debug verbosity. A detailed reproducer exists, but the report remains untriaged with no verified fix. |
|
snapcraft issue #4966 |
Shared cache for Python wheels | lengau | 806d | needs triage | 48 | 50 | 9 | Port Charmcraft's shared Python-wheel cache to Snapcraft to avoid repeated downloads and rebuilds; it remains open, unlabelled, and awaiting maintainer triage. |
|
snapcraft issue #5933 |
snapcraft fails with cmake not finding libpugixml.a | luspi | 313d | needs triage | 48 | 82 | 22 | core24 kde-neon-6 packaging fails because CMake loads a broken pugixml config from the SDK while libpugixml.a exists under /usr; the report is untriaged. |
|
snapcraft issue #5931 |
docs: golang plugin doc missing information on cross-compiling | sed-i | 315d | needs triage | 45 | 72 | 24 | Go plugin docs omit a reproducible cross-build failure: its fixed GOBIN makes `go install` reject foreign binaries, while clearing GOBIN prevents the install directory from being created. |
|
snapcraft issue #6479 |
craft_parts.packages.deb.Ubuntu wants gcc, but it is not installable... | nteodosio | 21d | needs triage | 45 | 35 | 6 | Cross-compiling Firefox amd64->arm64 in destructive Docker fails installing build-packages: plugin-injected gcc/make leads to gcc-13 Depends binutils not installable. No maintainer triage yet. |
|
snapcraft issue #5219 |
Snapcraft unable to compile ARM64 kernel | RuhanSA079 | 639d | needs triage | 45 | 82 | 14 | ARM64 core20 kernel cross-builds fail while fetching snapd:arm64; a minimal apt reproducer exists, but the report has no maintainer triage or release mapping. |
|
snapcraft issue #4459 |
icon 'discord.webp' must be either a .png or a .svg | merlijn-sebrechts | 1065d | needs triage | 42 | 64 | 19 | WebP snap icons remain blocked by Snapcraft’s PNG/SVG-only validation; the exact reproduction is clear, but a recent comment questions whether the Snap Store actually accepts WebP uploads. |
|
snapcraft issue #6001 |
`snapcraft clean --destructive` does not delete `.craft` directory | steinbro | 272d | needs triage | 40 | 86 | 19 | Destructive-mode clean leaves the .craft build-state directory behind; the report has an exact reproducer on Snapcraft 8.13.2 but remains untriaged. |
|
snapcraft issue #4802 |
No debug information about conflicting files in staging error in the... | seb128 | 903d | needs triage | 40 | 82 | 17 | Launchpad shows only the brief staging-conflict failure while the conflicting parts and files remain in the execution log; this valid diagnostic gap awaits maintainer triage. |
|
snapcraft issue #5086 |
snapcraft status lists several time the same information | seb128 | 757d | needs triage | 40 | 67 | 14 | Untriaged report: snapcraft status can repeat channel rows for one track and architecture, demonstrated with Snapcraft 8.4.1 on Ubuntu Oracular; no labels or maintainer activity. |
|
snapcraft issue #5171 |
home interface plug attribute "read: all" triggers ValidationError | florcabral | 691d | needs triage | 40 | 65 | 14 | Untriaged report that Snapcraft rejects app-level home plug attributes such as read: all despite documented snapd support; the reproducer contains conflicting list and scalar syntax. |
|
snapcraft issue #4869 |
Truncated error in hash mismatch output | sergiusens | 860d | needs triage | 35 | 70 | 13 | Hash-mismatch diagnostics are truncated in the concise CLI output, hiding parts of the expected and obtained digests; the full log contains both values, but the report remains unlabelled and untriaged. |
|
snapcraft issue #5040 |
Docs: Add a tutorial dedicated to the "default plugin + multiple binaries" scenario | sed-i | 776d | needs triage | 35 | 68 | 17 | Docs request: tutorial for packing multiple Go/Rust binaries with the plugin and iterating parts to discover/prime them. Unlabelled, no maintainer response; docs/tutorials still only has craft-a-snap, so unimplemented. |
|
snapcraft issue #4951 |
Consider adding flag to extensions to list experimental extensions | hartmutobendorf | 818d | needs triage | 32 | 45 | 12 | Feature request to add an --all flag to the extensions listing command and surface the SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS hint, so users can identify experimental extensions. The target command has since been renamed from list-extensions to extensions; the gap still exists. Untriaged. |
|
snapcraft issue #4541 |
Identical `parts` in different snaps contain different contents | dilyn-corner | 1009d | needs triage | 32 | 58 | 10 | A reported core24 build produced different stage_packages for ostensibly identical netplan parts; the original reproducer is detailed, but a later core22 test could not reproduce it and no triage followed. |
|
snapcraft issue #4891 |
Issue a warning when building a snap that stages another snap built on a... | kian99 | 848d | needs triage | 32 | 64 | 9 | Feature request (c/p from forum) to warn at build time when a part stages a snap built on a different base, which causes glibc/AppArmor denials at runtime. Only a bot comment linking internal ticket CRAFT-3126; no maintainer triage. |
|
snapcraft issue #4801 |
Doesn't tell you about conflicting files in staging before exiting the debug shell | seb128 | 903d | needs triage | 31 | 76 | 16 | Staging conflict diagnostics are omitted before --debug opens a shell, forcing users to find the conflicting parts and files in the log; the exact-reproducer report remains open and untriaged. |
|
snapcraft issue #6460 |
docs: add guidance for progressive release pause and resume capability | shaloo | 28d | needs triage | 30 | 75 | 18 | Documentation request to add progressive-release pause/resume guidance to the manage-revisions-and-releases page; resume uses `snapcraft release ... --progressive nn` with nn above the paused percentage. |
|
snapcraft issue #6291 |
New version gives error | silicology1 | 139d | needs triage | 30 | 25 | 3 | Snapcraft 9.0.0 fails `snapcraft pack` with git clone exit 128 cloning canonical/gpu-snap for the gnome extension's gpu/cleanup part; no snapcraft.yaml or logs supplied, maintainer asked for a reproducer. |
|
snapcraft issue #6239 |
Update package repositories test | mr-cal | 177d | needs triage | 30 | 42 | 7 | core26 package-repositories spread test still short-circuits test_apt_ppa with a 'no Release file' MATCH because the snappy-dev/deadsnakes PPAs lack resolute suites. Blocked on external Launchpad state; a volunteer offered to help with no maintainer reply. |
|
snapcraft issue #6331 |
docs: truncated sentence | CAD97 | 112d | needs triage | 25 | 80 | 17 | Docs bug: snapcraft's docs/explanation/parts.rst includes craft-parts common docs with :start-line: 5, which skips the first line of the opening paragraph, rendering 'About parts' with a mid-sentence start. Root cause identified. |
|
snapcraft issue #6318 |
snapcraft's lxc command string is not working without LANG=C on Ubuntu Touch | fredldotme | 119d | needs triage | 22 | 32 | 4 | Reports `snapcraft pack` failing on Ubuntu Touch (arm64 JingPad A1): LXC `exec ... env ... systemctl is-system-running` times out in craft_providers' LXD provider unless LANG=C is set. Untriaged, no maintainer response. |