Fedora 30 workstation - System upgrade brake snapd

snap find hello
2019/12/18 10:51:37.387870 cmd_linux.go:70: DEBUG: re-exec not supported on distro “fedora” yet
error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/find?q=hello&scope=wide: dial unix /run/snapd.socket: connect: no such file or directory

sudo systemctl restart snapd
A dependency job for snapd.service failed. See ‘journalctl -xe’ for details.

sudo systemctl status snapd
snapd.service - Snappy daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.service; enabled; vendor preset: disabled)
Active: inactive (dead)

gru 18 10:43:28 localhost.localdomain systemd[1]: Dependency failed for Snappy daemon.
gru 18 10:43:28 localhost.localdomain systemd[1]: snapd.service: Job snapd.service/start failed with result ‘dependency’.
gru 18 10:43:28 localhost.localdomain systemd[1]: snapd.service: Triggering OnFailure= dependencies.
gru 18 10:55:07 localhost.localdomain systemd[1]: Dependency failed for Snappy daemon.
gru 18 10:55:07 localhost.localdomain systemd[1]: snapd.service: Job snapd.service/start failed with result ‘dependency’.
gru 18 10:55:07 localhost.localdomain systemd[1]: snapd.service: Triggering OnFailure= dependencies.
gru 18 10:55:09 localhost.localdomain systemd[1]: Dependency failed for Snappy daemon.
gru 18 10:55:09 localhost.localdomain systemd[1]: snapd.service: Job snapd.service/start failed with result ‘dependency’.
gru 18 10:55:09 localhost.localdomain systemd[1]: snapd.service: Triggering OnFailure= dependencies.

this systemd service file content

[Unit]
Description=Snappy daemon
Requires=snapd.socket
OnFailure=snapd.failure.service

This is handled by snapd

X-Snapd-Snap: do-not-start

[Service]

Disabled because it breaks lxd

(https://bugs.launchpad.net/snapd/+bug/1709536)

#Nice=-5
OOMScoreAdjust=-900
ExecStart=/usr/libexec/snapd/snapd
EnvironmentFile=-/etc/sysconfig/snapd
Restart=always
WatchdogSec=5m
Type=notify
SuccessExitStatus=42
RestartPreventExitStatus=42
KillMode=process

[Install]
WantedBy=multi-user.target

Thanks for the report. Looks like snapd.service did not start because its dependencies failed. AFAIK
snapd.socket is the only dependency of snapd.service, can you run systemctl restart snapd.socket? Is there anything about systemd failing to start snapd.socket in the journal (system journal, not the unit specific bit)?

after systemctl restart snapd.socket work proper. I make restart system and confirm if this help.

Yes now work proper after restart