Snap.d error: cannot communicate with server connection refused

aregowe · June 25, 2018, 4:06pm

error: cannot communicate with server: Post http://localhost/v2/snaps/hello-world: dial unix /run/snapd.socket: connect: connection refused

https://i.stack.imgur.com/t2RDe.png

Can’t get anything snap to work. What the? For instance, if I even try to run the basic calculator that comes with Ubuntu, it doesn’t even run. If I try to start calculator, it says:

/var/lib/snapd has 'other' write 40777

Any ideas?

ogra · June 25, 2018, 4:13pm

that looks like snapd did not start at all … take a look with

systemctl status snapd.service

also (not sure if it works in that state) the output of snap version would surely be helpful

aregowe · June 25, 2018, 4:17pm

The error I receive is:

janderson@jUbuntu:~$ systemctl status snapd.service
● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-06-25 08:14:12 EDT; 4min 12s ago
  Process: 1107 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
 Main PID: 1107 (code=exited, status=1/FAILURE)

Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
Jun 25 08:14:12 jUbuntu systemd[1]: Stopped Snappy daemon.
Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Start request repeated too quickly.
Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
Jun 25 08:14:12 jUbuntu systemd[1]: Failed to start Snappy daemon.

Also

janderson@jUbuntu:~$ snap version
snap    2.32.9+18.04
snapd   unavailable
series  -

ogra · June 25, 2018, 4:25pm

very interesting that your snap version output stops at “series” where it should also show kernel version and the release you are running, like:

$ snap version
snap    2.33
snapd   2.33
series  16
ubuntu  16.04
kernel  4.13.0-43-generic

is this an unmodified 18.04 install using default packages for kernel and such ?

aregowe · June 25, 2018, 4:31pm

Weird, yes it’s an unmodified version. The only things I’ve done is:

Install PHP Storm IDE
Install Slack
Install Sublime text editor
Install PHP 7.1, Nginx, MySQL
Install Symless Synergy (1 mouse between 2 pcs)
Install Discord
Install Filezilla
Set my DNS to Google DNS ( 8.8.8.8 )

Also modified hosts for working with Magento 2.2.2 cms platform

127.0.0.1	localhost
127.0.1.1	jUbuntu

127.0.0.1 local.sportysm2.com
127.0.0.1 local-pilotshop.sportysm2.com
127.0.0.1 local-wrightbros.sportysm2.com
127.0.0.1 local-preferredliving.sportysm2.com
127.0.0.1 local-toolshop.sportysm2.com

This machine also dual boots Ubuntu 18.04 and Windows 10 pro 64-bit.

Machine Specs:

ogra · June 25, 2018, 4:34pm

perhaps @zyga-snapd or @chipaca have more suggestions how to debug this …

zyga-snapd · June 25, 2018, 4:36pm

Hey

Can you please provide journalctl -xu snapd.service

aregowe · June 25, 2018, 4:38pm

Sure thing! It is:

(Was too long for post)

zyga-snapd · June 25, 2018, 4:39pm

Hmm

Can you systemctl start snapd.service now? I don’t see anything bad in the logs

aregowe · June 25, 2018, 4:40pm

I didn’t see it initially, but there was more, I had to scroll down in terminal. Too much to post on the forum:

zyga-snapd · June 25, 2018, 4:42pm

So the issue is:

Jun 25 08:14:12 jUbuntu snapd[1107]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0

Did you do some chmoding?

aregowe · June 25, 2018, 4:42pm

I don’t recall doing any chmodding of that directory, I did chmod my home/janderson/magento2 directory though, where I develop in Magento locally.

What should the permissions of that directory be?

zyga-snapd · June 25, 2018, 4:44pm

Well, something has changed the permissions. Just make sure they are not world writable. sudo chmod o-w /var/lib/snapd/assertions/asserts-v0 should do it

aregowe · June 25, 2018, 4:48pm

All righty, just tried that, then ran

janderson@jUbuntu:~$ systemctl start snapd.service
Job for snapd.service failed because the control process exited with error code.
See "systemctl status snapd.service" and "journalctl -xe" for details.


janderson@jUbuntu:~$ systemctl status snapd.service
● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-06-25 00:45:53 EDT; 1min 13s ago
  Process: 17077 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
 Main PID: 17077 (code=exited, status=1/FAILURE)

Jun 25 00:45:53 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
Jun 25 00:45:53 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
Jun 25 00:45:53 jUbuntu systemd[1]: Stopped Snappy daemon.
Jun 25 00:45:53 jUbuntu systemd[1]: snapd.service: Start request repeated too quickly.
Jun 25 00:45:53 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
Jun 25 00:45:53 jUbuntu systemd[1]: Failed to start Snappy daemon.

janderson@jUbuntu:~$ journalctl -xe
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #8 0x7ffe8bb06650 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f660c5d3b38 @ 54)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #9 0x7ffe8bb067a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f660c5d3bc0 @ 1626)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #10 0x7ffe8bb06850 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f660c5d3c48 @ 100)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #11 0x7ffe8bb068e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f660c5d3cd0 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #12 0x7ffe8bb069d0 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f660c5d3230 @ 386)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #13 0x7ffe8bb06a80 b   resource:///org/gnome/shell/ui/tweener.js:245 (0x7f660c5cf808 @ 159)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #14 0x7ffe8bb06ae0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #15 0x7ffe8bb06b80 b   resource:///org/gnome/shell/ui/tweener.js:220 (0x7f660c5cf780 @ 15)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: == Stack trace for context 0x5613a5486340 ==
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #0 0x7ffe8bb01af0 b   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c101098 @ 10)
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a86a94e0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #1 0x7ffe8bb01be0 b   self-hosted:251 (0x7f660c5c3ab0 @ 223)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #2 0x5613a5911ab0 i   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c3f8f78 @ 28)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #3 0x7ffe8bb029b0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #4 0x5613a5911a38 i   resource:///org/gnome/shell/ui/iconGrid.js:281 (0x7f660c3f8a28 @ 34)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #5 0x5613a59119b0 i   resource:///org/gnome/shell/ui/viewSelector.js:361 (0x7f660c1e3d58 @ 25)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #6 0x7ffe8bb055c0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #7 0x5613a5911930 i   resource:///org/gnome/shell/ui/viewSelector.js:354 (0x7f660c1e3cd0 @ 22)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #8 0x7ffe8bb06650 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f660c5d3b38 @ 54)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #9 0x7ffe8bb067a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f660c5d3bc0 @ 1626)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #10 0x7ffe8bb06850 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f660c5d3c48 @ 100)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #11 0x7ffe8bb068e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f660c5d3cd0 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #12 0x7ffe8bb069d0 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f660c5d3230 @ 386)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #13 0x7ffe8bb06a80 b   resource:///org/gnome/shell/ui/tweener.js:245 (0x7f660c5cf808 @ 159)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #14 0x7ffe8bb06ae0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #15 0x7ffe8bb06b80 b   resource:///org/gnome/shell/ui/tweener.js:220 (0x7f660c5cf780 @ 15)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: == Stack trace for context 0x5613a5486340 ==
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #0 0x7ffe8bb01af0 b   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c101098 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #1 0x7ffe8bb01be0 b   self-hosted:251 (0x7f660c5c3ab0 @ 223)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #2 0x5613a5911ab0 i   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c3f8f78 @ 28)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #3 0x7ffe8bb029b0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #4 0x5613a5911a38 i   resource:///org/gnome/shell/ui/iconGrid.js:281 (0x7f660c3f8a28 @ 34)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #5 0x5613a59119b0 i   resource:///org/gnome/shell/ui/viewSelector.js:361 (0x7f660c1e3d58 @ 25)
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7b140), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #6 0x7ffe8bb055c0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #7 0x5613a5911930 i   resource:///org/gnome/shell/ui/viewSelector.js:354 (0x7f660c1e3cd0 @ 22)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #8 0x7ffe8bb06650 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f660c5d3b38 @ 54)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #9 0x7ffe8bb067a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f660c5d3bc0 @ 1626)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #10 0x7ffe8bb06850 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f660c5d3c48 @ 100)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #11 0x7ffe8bb068e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f660c5d3cd0 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #12 0x7ffe8bb069d0 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f660c5d3230 @ 386)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #13 0x7ffe8bb06a80 b   resource:///org/gnome/shell/ui/tweener.js:245 (0x7f660c5cf808 @ 159)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #14 0x7ffe8bb06ae0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #15 0x7ffe8bb06b80 b   resource:///org/gnome/shell/ui/tweener.js:220 (0x7f660c5cf780 @ 15)
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7ade0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7aa80), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7b800), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu dbus-daemon[1206]: [session uid=1000 pid=1206] Successfully activated service 'org.gnome.seahorse.Application'
Jun 25 00:45:54 jUbuntu dbus-daemon[1206]: [session uid=1000 pid=1206] Successfully activated service 'org.gnome.Calendar'
Jun 25 00:45:55 jUbuntu PackageKit[1539]: resolve transaction /426_dbedcabd from uid 1000 finished with cancelled after 291ms
Jun 25 00:45:55 jUbuntu gnome-software[1642]: internal error: failed, but no error code: cancelled
Jun 25 00:45:55 jUbuntu PackageKit[1539]: resolve transaction /427_adbecabb from uid 1000 finished with success after 247ms
Jun 25 00:45:56 jUbuntu gnome-calculator_gnome-calculator.desktop[17184]: /var/lib/snapd has 'other' write 40777
Jun 25 00:46:19 jUbuntu nautilus[16883]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)
...skipping...
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #8 0x7ffe8bb06650 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f660c5d3b38 @ 54)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #9 0x7ffe8bb067a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f660c5d3bc0 @ 1626)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #10 0x7ffe8bb06850 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f660c5d3c48 @ 100)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #11 0x7ffe8bb068e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f660c5d3cd0 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #12 0x7ffe8bb069d0 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f660c5d3230 @ 386)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #13 0x7ffe8bb06a80 b   resource:///org/gnome/shell/ui/tweener.js:245 (0x7f660c5cf808 @ 159)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #14 0x7ffe8bb06ae0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #15 0x7ffe8bb06b80 b   resource:///org/gnome/shell/ui/tweener.js:220 (0x7f660c5cf780 @ 15)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: == Stack trace for context 0x5613a5486340 ==
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #0 0x7ffe8bb01af0 b   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c101098 @ 10)
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a86a94e0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #1 0x7ffe8bb01be0 b   self-hosted:251 (0x7f660c5c3ab0 @ 223)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #2 0x5613a5911ab0 i   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c3f8f78 @ 28)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #3 0x7ffe8bb029b0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #4 0x5613a5911a38 i   resource:///org/gnome/shell/ui/iconGrid.js:281 (0x7f660c3f8a28 @ 34)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #5 0x5613a59119b0 i   resource:///org/gnome/shell/ui/viewSelector.js:361 (0x7f660c1e3d58 @ 25)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #6 0x7ffe8bb055c0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #7 0x5613a5911930 i   resource:///org/gnome/shell/ui/viewSelector.js:354 (0x7f660c1e3cd0 @ 22)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #8 0x7ffe8bb06650 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f660c5d3b38 @ 54)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #9 0x7ffe8bb067a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f660c5d3bc0 @ 1626)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #10 0x7ffe8bb06850 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f660c5d3c48 @ 100)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #11 0x7ffe8bb068e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f660c5d3cd0 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #12 0x7ffe8bb069d0 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f660c5d3230 @ 386)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #13 0x7ffe8bb06a80 b   resource:///org/gnome/shell/ui/tweener.js:245 (0x7f660c5cf808 @ 159)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #14 0x7ffe8bb06ae0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #15 0x7ffe8bb06b80 b   resource:///org/gnome/shell/ui/tweener.js:220 (0x7f660c5cf780 @ 15)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: == Stack trace for context 0x5613a5486340 ==
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #0 0x7ffe8bb01af0 b   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c101098 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #1 0x7ffe8bb01be0 b   self-hosted:251 (0x7f660c5c3ab0 @ 223)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #2 0x5613a5911ab0 i   resource:///org/gnome/shell/ui/iconGrid.js:416 (0x7f660c3f8f78 @ 28)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #3 0x7ffe8bb029b0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #4 0x5613a5911a38 i   resource:///org/gnome/shell/ui/iconGrid.js:281 (0x7f660c3f8a28 @ 34)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #5 0x5613a59119b0 i   resource:///org/gnome/shell/ui/viewSelector.js:361 (0x7f660c1e3d58 @ 25)
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7b140), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #6 0x7ffe8bb055c0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #7 0x5613a5911930 i   resource:///org/gnome/shell/ui/viewSelector.js:354 (0x7f660c1e3cd0 @ 22)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #8 0x7ffe8bb06650 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f660c5d3b38 @ 54)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #9 0x7ffe8bb067a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f660c5d3bc0 @ 1626)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #10 0x7ffe8bb06850 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f660c5d3c48 @ 100)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #11 0x7ffe8bb068e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f660c5d3cd0 @ 10)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #12 0x7ffe8bb069d0 b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f660c5d3230 @ 386)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #13 0x7ffe8bb06a80 b   resource:///org/gnome/shell/ui/tweener.js:245 (0x7f660c5cf808 @ 159)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #14 0x7ffe8bb06ae0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f660c5b5de0 @ 71)
Jun 25 00:45:54 jUbuntu org.gnome.Shell.desktop[1346]: #15 0x7ffe8bb06b80 b   resource:///org/gnome/shell/ui/tweener.js:220 (0x7f660c5cf780 @ 15)
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7ade0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7aa80), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu gnome-shell[1346]: Object Clutter.Clone (0x5613a8d7b800), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destr
Jun 25 00:45:54 jUbuntu dbus-daemon[1206]: [session uid=1000 pid=1206] Successfully activated service 'org.gnome.seahorse.Application'
Jun 25 00:45:54 jUbuntu dbus-daemon[1206]: [session uid=1000 pid=1206] Successfully activated service 'org.gnome.Calendar'
Jun 25 00:45:55 jUbuntu PackageKit[1539]: resolve transaction /426_dbedcabd from uid 1000 finished with cancelled after 291ms
Jun 25 00:45:55 jUbuntu gnome-software[1642]: internal error: failed, but no error code: cancelled
Jun 25 00:45:55 jUbuntu PackageKit[1539]: resolve transaction /427_adbecabb from uid 1000 finished with success after 247ms
Jun 25 00:45:56 jUbuntu gnome-calculator_gnome-calculator.desktop[17184]: /var/lib/snapd has 'other' write 40777
Jun 25 00:46:19 jUbuntu nautilus[16883]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)

zyga-snapd · June 25, 2018, 4:51pm

I think you broke your system. I don’t think this is a snapd issue really. My suggestion would be to make a backup of essential data and reinstall.

Teddy · November 9, 2018, 8:03am

Hi, been having the same issue for some time now.
I uninstalled snap and re-installed it again to solve the error:

$ sudo apt autoremove --purge snapd

$ sudo apt install snapd

rsv4 · February 18, 2019, 8:34pm

I’ve been having the same issue, I am using ubuntu core on a raspberripi 3B+. I can ping google.com.
here is the return of systemctl status snapd.service:

● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-02-18 20:12:34 UTC; 1min 52s ago
Main PID: 1515 (snapd)
CGroup: /system.slice/snapd.service
└─1515 /usr/lib/snapd/snapd

rsv4 · February 18, 2019, 8:37pm

and here is the journalctl -xe and as you can see it failed, I have restarted the snap, reboot the system and no luck. I removed the support links to be able to post

Feb 18 20:12:33 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'.
Feb 18 20:12:33 localhost.localdomain systemd[1]: Started Failure handling of the snapd snap.
-- Subject: Unit snapd.failure.service has finished start-up
-- Defined-By: systemd
-- Support:
-- 
-- Unit snapd.failure.service has finished starting up.
-- 
-- The start-up result is done.
Feb 18 20:12:33 localhost.localdomain systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
Feb 18 20:12:33 localhost.localdomain systemd[1]: Stopped Snappy daemon.
-- Subject: Unit snapd.service has finished shutting down
-- Defined-By: systemd
-- Support:
-- 
-- Unit snapd.service has finished shutting down.
Feb 18 20:12:33 localhost.localdomain systemd[1]: Starting Snappy daemon...
-- Subject: Unit snapd.service has begun start-up
-- Defined-By: systemd
-- Support:
-- 
-- Unit snapd.service has begun starting up.
Feb 18 20:12:33 localhost.localdomain snapd[1515]: AppArmor status: apparmor is enabled and all features are available
Feb 18 20:12:34 localhost.localdomain snapd[1515]: daemon.go:379: started snapd/2.37.1 (series 16) ubuntu-core/16 (armhf) linux/4.4.0-1100-raspi2.
Feb 18 20:12:34 localhost.localdomain systemd[1]: Started Snappy daemon.
-- Subject: Unit snapd.service has finished start-up
-- Defined-By: systemd
-- Support: 
-- 
-- Unit snapd.service has finished starting up.
-- 
-- The start-up result is done.
Feb 18 20:16:40 localhost.localdomain sudo[1536]: fzorrilla : TTY=pts/0 ; PWD=/var/lib/classic ; USER=root ; COMMAND=/bin/journalctl -xe
Feb 18 20:16:40 localhost.localdomain sudo[1536]: pam_unix(sudo:session): session opened for user root by fzorrilla(uid=0)
lines 1719-1752/1752 (END)

chipaca · February 19, 2019, 11:29am

Hi,

could you describe your issue in more detail?

Also, could you paste the output of snap version?

Thank you.

rsv4 · February 20, 2019, 5:39pm

I have try to use snap refresh, sudo systemctl restart, so on and so forth and always get the same error: cannot communicate with server: Post http://localhost/v2/snaps/

@localhost:~$ snap version
snap 2.37.1
snapd unavailable
series -

a couple of days ago I was able to get the snapd and series information, but I was never able to use snap to get an app. So I do not know what I did wrong, I am a rookie at this so any help is welcome.