I am having this issue with Ubuntu 20.10; and had it on 20.04 - but on
20.04 i wasn't doing as much development work and avoided the problem by
just using the PPA or Synaptic; now it is unavoidable because the
packages i need that are more architecture independent are in Snap, and
each time I try
This is a collection of bug reports and it seems that at least some of
them are already solved either by manually enabling services or using
newer versions of snapd. Are any of these issues still happening?
** Changed in: snapd
Status: Confirmed => Incomplete
--
You received this bug
I experienced that problem with a fresh installation of Ubuntu Core for
RasbperryPI 3 using the official instructions:
https://www.ubuntu.com/download/iot/raspberry-pi-2-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just noting that at least with the latest snapd update I noticed there
was a helpful message:
"On a Tumbleweed system you need to run: systemctl enable
snapd.apparmor.service"
Ie, not only snapd service itself. With that bit, everything's working
as intended!
Maybe this is as far as it can go
I've tried disabling and enabling the snapd.service itself, but I still
need to restart manually after a reboot.
Additionally as an unrelated thing I also need to run the following after each
reboot now:
sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/*
Without that I get the same
Hello
On openSUSE the socket and other services are not started automatically.
You must install snapd and enable the socket yourself. Services are
managed with systemd presets that are in turn managed centrally for the
whole distribution.
--
You received this bug notification because you are a
Reproduce steps:
1. Install openSUSE 15.0
2. Online upgrade to Tumbleweed
https://en.opensuse.org/openSUSE:Tumbleweed_upgrade
3. Install snapd from https://software.opensuse.org/package/snapd -> Tumbleweed
-> Show experimental packages -> 1 Click install
4. Reboot (if wanted)
5. Observe
--
You
Reproduce steps:
1. Install openSUSE 15.0
2. Online upgrade to Tumbleweed
https://en.opensuse.org/openSUSE:Tumbleweed_upgrade
3. Install snapd from https://software.opensuse.org/package/snapd -> Tumbleweed
-> Show experimental packages -> 1 Click install
4. Reboot (if wanted)
5. Observe
**
Just bumped into this on freshly installed openSUSE Tumbleweed after
installing snapd. Rebooting did not help, but systemctl restart
snapd.service manually did help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Gustavo It worked for me. It also purged plasma-discover-snap-backend
along with snapd. After the purge I performed a autoremove and a clean,
following a reboot. On login I installed them again and had the exact
same error message. Starting the service manually, snapd can search and
install.
--
** Changed in: snapd
Status: New => Incomplete
--
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
systemctl start snapd.service
work for me
--
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
I tried again with:
sudo apt purge snapd (instead of just remove)
reboot
sudo apt install snapd
As the final message was:
"snapd.snap-repair.service is a disabled or a static unit, not starting it"
I did:
sudo systemctl start snapd.service
And it worked!
--
You received this bug
I got the same error in Ubuntu 18.04 updated from Ubuntu 16.04.
I tried:
sudo systemctl restart snapd.service
And I got:
Job for snapd.service failed because the control process exited with error
code.
See "systemctl status snapd.service" and "journalctl -xe" for details.
I tried:
was a about to file a bug regarding this.
error: cannot communicate with server: Post http://localhost/v2/login:
dial unix /run/snapd.socket: connect: no such file or directory
and I just followed @Bradley Jelinek then it fixed. Thanks!
--
You received this bug notification because you are a
I got the same problem,Windows 10 subsystem Ubuntu server 18 and docker
run ubuntu server 16, both get same problem.
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
same thing with manjaro 17.1 Xfce
systemctl restart snapd.service
fixed it
--
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
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631514
Running in a chroot, so I don't have systemctl available. Fixed this by
manually running /usr/lib/snapd/snapd.
--
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:
I get the same exact error also on Manjaro KDE
# snap install inkscape
error: cannot communicate with server: Post http://localhost/v2/snaps/inkscape:
dial unix /run/snapd.socket: connect: no such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs,
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset:
enabled)
Active: inactive (dead) (Result: exit-code) since пт 2017-04-21 20:02:12
EEST; 41min ago
Process: 829 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
Main
got the same error from this command:
sudo snap install --edge --devmode anbox
--
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
@Joseph, that looks like a different issue; could you file a new bug?
Include the output of “journalctl -u snapd.service” when you do. Thank
you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631514
I also get this issue with Snapd, but without all the errors in the
snapd log:
$ systemctl status snapd.service
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2017-03-16 17:07:19 UTC;
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
Manually install snapd_2.17.1_amd64.deb then upgrade to 2.20.1ubuntu1
cannot reproduce this.
snapd ran properly:
Jan 12 12:09:02 X230 /usr/lib/snapd/snapd[11593]: daemon.go:207: DEBUG: init
done in 831.812µs
Jan 12 12:09:11 X230 /usr/lib/snapd/snapd[11593]: daemon.go:172: DEBUG: uid=0;@
POST
Looking at your upgrade log I see:
"""
...
Setting up snapd (2.20.1ubuntu1) ...
snapd.service is a disabled or a static unit, not starting it.
...
"""
so it appears for some reason the dpkg systemd helper is confused. Is that
reproducable for you for upgrades from 2.17.1ubuntu1 to 2.20.1ubuntu1 ?
@mvo reboot few times, doesn't seems to see this again.
manually downgrade to 2.0.2 and then re-upgrade to 2.20.1ubuntu1 will
not able to reproduce this problem.
** Attachment added: "snapd-apt-full-upgrade.log.tar.xz"
@Yung Shen: that is interessting - could you please also attach
/var/log/apt/history.log and /var/log/apt/term.log ? I wonder if we can
find a clue there. It looks like your snapd was not (re)started on
upgrade. What if you reboot? Do you need to manually start it then as
well?
--
You received
happen to see the same error message on 16.04.1,
snapd v2.20.1ubuntu1
ubuntu-core v16.04.1 rev1357
systemctl status snapd.service
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; disabled; vendor preset:
enabled)
Active: inactive (dead) since Mon
happen to see the same error message on 16.04.1,
snapd v2.20.1ubuntu1
ubuntu-core v16.04.1 rev1357
systemctl status snapd.service
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; disabled; vendor preset:
enabled)
Active: inactive (dead) since Mon
Could you please attach the output of:
$ systemctl status snapd.service
to this bug?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
32 matches
Mail list logo
