improve the error message when snap daemon is not running

Bug #1961480 reported by K0RR
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Confirmed
Undecided
Unassigned

Bug Description

When the snapd is not running (systemctl status snapd) the error message is:
error: cannot communicate with server: Post "http://localhost/v2/snaps": dial unix /run/snapd.socket: connect: no such file or directory

Which is not user-friendly and doesn't tell what's wrong. It should say "Make sure snapd is running"

Revision history for this message
Alberto Mardegan (mardy) wrote :

Hi Radek, thanks for the suggestion, it sounds good to me!

Just wondering, since we got another bug in these days about snapd being unreachable: what did you do to find yourself in this situation? Did you explicitly shutdown snapd yourself, or did you encounter some issue?

(for reference: https://bugs.launchpad.net/bugs/1961418)

Changed in snapcraft:
status: New → Confirmed
affects: snapcraft → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.