I had the same problem on Suse leap 42.2: # systemctl status snapd ● snapd.service - Snappy daemon Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; vendor preset: disabled) Active: failed (Result: start-limit) since Fri 2017-02-24 09:07:44 GMT; 4s ago Process: 2246 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE) Main PID: 2246 (code=exited, status=1/FAILURE)
Feb 24 09:07:44 kitchen systemd[1]: snapd.service: Unit entered failed state. Feb 24 09:07:44 kitchen systemd[1]: snapd.service: Failed with result 'exit-code'. Feb 24 09:07:44 kitchen systemd[1]: snapd.service: Service hold-off time over, scheduling restart. Feb 24 09:07:44 kitchen systemd[1]: Stopped Snappy daemon. Feb 24 09:07:44 kitchen systemd[1]: snapd.service: Start request repeated too quickly. Feb 24 09:07:44 kitchen systemd[1]: Failed to start Snappy daemon. Feb 24 09:07:44 kitchen systemd[1]: snapd.service: Unit entered failed state. Feb 24 09:07:44 kitchen systemd[1]: snapd.service: Failed with result 'start-limit'. journalctl revealed: snapd[20747]: error: fatal: directory "/var/lib/snapd" must be present so I just did # mkdir /var/lib/snapd and it worked ?! Did someone forget to make /var/lib/snapd in the install package? All good. Tks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631514 Title: snap doesnt work. error: cannot communicate with server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1631514/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
