← Back to issue list

LXD not running error message is vague

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1728649
Type
issue
State
closed
Author
~ev
Labels
—
Created
Updated
Closed

Current evaluation

Enhancement request to improve the vague "Connection refused; is LXD running?" error from `snapcraft cleanbuild`. Discussion stalled over whether to recommend purging the apt lxd package; closed incomplete and later expired by Launchpad janitor with no code change.

Resolution: closed stale

Reason: The discussion ended with sergiusens setting status to incomplete on 2017-10-30, and the bug was later auto-closed by the Launchpad janitor on 2018-02-06 with "Expired for Snapcraft because there has been no activity for 60 days." No commit in the snapcraft history introduces the proposed LXD setup instructions, and grepping for "newgrp lxd" and "apt purge lxd" yields no matches, confirming the error text was never changed.

Evaluated by: mr-cal-bot

No scores available.

Issue body

""" ubuntu@subtly-needed-chaffinch:~/cli$ snapcraft cleanbuild Connection refused; is LXD running? There are either no permissions or the remote 'local' does not exist. Verify the existing remotes by running `lxc remote list` """ We could improve this. How about: """ Could not connect to LXD, which is necessary for cleanbuild. If the LXD snap is not installed, run:   sudo apt purge lxd   sudo snap install lxd   sudo lxd init   newgrp lxd """

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale Enhancement request to improve the vague "Connection refused; is LXD running?" error from `snapcraft cleanbuild`. Discussion stalled over whether to recommend purging the apt lxd package; closed incomplete and later expired by Launchpad janitor with no code change.
stealth/space-bunny-alpha — closed stale Request for clearer cleanbuild LXD guidance was auto-expired in 2018 after 60 days of inactivity; Launchpad bug 1728649 closed with no fixing PR or commit.
stealth/space-bunny-alpha — closed stale Closed without a recorded fix; the request for clearer cleanbuild LXD guidance received no discussion or linked implementation before the report went stale.
qwen/qwen3.6-35b-a3b — — Suggested improved LXD error messaging was closed without implementation or discussion. The request appears abandoned due to zero comments and prolonged inactivity.
qwen/qwen3.6-35b-a3b — — Abandoned. The suggested error message improvement for LXD connection failures was not implemented.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The suggested error message improvements were not adopted, likely abandoned or superseded by newer Snapcraft versions.
qwen3.6-35b-a3b-mtp-q6 — — Proposed clearer error messaging and installation steps for LXD connection failures. Closed with no comments or code changes, indicating the enhancement was abandoned or declined due to inactivity.

Update history

Date Change
created

Related work

  • Related To: snapcraft (launchpad)#1728649 (confidence 50%)

    Follow-up comments (kalikiana) identified the underlying cause as the lxd-client deb and lxd snap using different socket paths, but no tracking change was linked.

Related issues

Issue Project State Summary Similarity
#1550381 lxd should be a suggestion, not a direct dependency snapcraft (launchpad) closed LXD was changed from a direct dependency to a suggestion in canonical/snapcraft PR #343 (commit 7147a43ba), resolving Launchpad #1550381.
70%
#1928046 Misleading error message about lxd.migrate snapcraft (launchpad) open A false-positive LXD deb-package warning blocked Snapcraft despite the LXD snap being installed; the maintainer planned to remove the check, but the issue remains open.
70%