← Back to issue list

USB and Core22 and Snap

View original Github issue

Metadata

Project
snapcraft
Number
#5291
Type
issue
State
closed
Author
wills721
Labels
Type: Invalid Status: Triaged
Created
Updated
Closed

Current evaluation

Closed as Invalid by maintainer mr-cal: USB device visibility on Core22 is a snapd runtime/interface problem, not a Snapcraft build bug; reporter directed to the Snapcraft forum and asked for Snapcraft error logs.

Resolution: closed not a bug

Reason: No Snapcraft code change was made or needed. Maintainer mr-cal closed the report labelled 'Type: Invalid' on 2025-04-21, stating snapd runtime issues belong on the Snapcraft forum and asking for logs from an actual Snapcraft error before a bug would be tracked; searches of the snapcraft repo found no matching commits or code references tied to this report.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### Bug Description Cannot see the USB device. I tried a post here but to no avail https://forum.snapcraft.io/t/ubuntu-core-22-snap-and-usb/45911 Basically, I am trying every possible plug and no matter what when my USB device gets plugged in i cannot find it. ### To Reproduce Snap a yaml that requires access to USB ### Environment Core22 on Compute 4 ### snapcraft.yaml ```yaml plugs: - mount-observe - network-bind - process-control - raw-usb - hardware-observe - log-observe - home-for-greengrass - docker-cli - docker-executables - root-dot-docker - serial-port - physical-memory-control - i2c - gpio-control ``` ### Relevant log output ```shell no device under /dev ``` ### Additional context _No response_

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed not a bug Closed as Invalid by maintainer mr-cal: USB device visibility on Core22 is a snapd runtime/interface problem, not a Snapcraft build bug; reporter directed to the Snapcraft forum and asked for Snapcraft error logs.
stealth/space-bunny-alpha — closed not a bug Closed as invalid/support request: USB device not appearing in /dev is a snapd runtime/interface concern, not a Snapcraft bug. Maintainer @mr-cal pointed the reporter to the snapcraft forum and asked for Snapcraft logs.
stealth/space-bunny-alpha — closed not a bug Closed as invalid/support request: the maintainer redirected this snapd runtime USB problem to the Snapcraft forum and requested Snapcraft error logs to investigate a build-tool bug.
qwen/qwen3.6-35b-a3b — — Closed as invalid. Maintainer directed the user to the Snapcraft forum for snapd runtime support, noting that snapcraft-specific error logs are required to investigate a build tool bug. No code changes were made.
qwen/qwen3.6-35b-a3b — — Closed as invalid. Maintainer redirected the reporter to the Snapcraft forum for runtime support, noting the report lacked Snapcraft-specific error logs and appeared to be a snapd configuration issue rather than a tool bug.
qwen3.6-35b-a3b-mtp-q6 — — Closed as invalid. Maintainer directed the user to the Snapcraft forum for runtime support, noting the report lacks evidence of a snapcraft bug. Internal Jira tickets were created, but the issue was resolved by redirecting to community support.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1981072 Core22 Snap builds don't output error logs snapcraft (launchpad) closed Launchpad core22 snap builds showed no error output. Closed as fixed after snapcraft PR canonical/snapcraft#3889 (commit 72ad273f2) plus craft-parts logging fixes; maintainer confirmed Snapcraft 8 reports stdout/stderr for core22 builds.
72%