After doing some research I discovered I did not need or whant snaps at all.
They are like having repeat copies of OS portions loaded on disk and memory,
thus very slow and consumming.
Just purged snapd and put a block on them at this URL:
Hi @bitterhalt, can you try installing the snapd snap via `snap install
snapd` and then see if your system is still affected? As Alberto
mentioned, we do expect this to be fixed now with the aforementioned
commit.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in:
I installed Ubuntu 21.10 a week a go and I got this massive delay with
every reboot because of snap deamon hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
Snappy daemon reaches
I believe that this is the same issue as #1946656, which will be fixed
in snapd 2.53:
https://github.com/snapcore/snapd/commit/da1caa8b12c0f839320f29012b4565d1f702eb42
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd (Ubuntu)
snap
is
cancer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
Snappy daemon reaches 1min30s timeout during shutdown process
To manage notifications about this bug go to:
Further to my comment #32:
After a recent re-installation of 'impish' in late July (for reasons not
relevant here) using the same hardware and ISO image, and many reboots
later I haven't seen this delay before shutting down or rebooting at
all.
--
You received this bug notification because you
This bug affects me, on Ubuntu 21.10
$ snap --version
snap2.53+21.10ubuntu1
snapd 2.53+21.10ubuntu1
series 16
ubuntu 21.10
kernel 5.13.0-19-generic
$ snap list
Название Версия Правка Канал
ИздательПримечание
bare 1.0
This bug affects me, on Ubuntu 20.04.03 LTS.
>snap --version
snap2.51.4
snapd 2.51.4
series 16
ubuntu 20.04
kernel 5.11.0-27-generic
>snap list
Name Version RevTracking
Publisher Notes
core 16-2.51.4 11606
I have not seen this issue in my Focal installation for over a year now.
But the isse seems to be present in my 3-day old Impish installation.
Jul 05 18:21:31 n1687 systemd[1]: snapd.service: State 'stop-sigterm' timed
out. Killing.
Jul 05 18:21:31 n1687 systemd[1]: snapd.service: Killing
Well, I do still experience this bug. I was too optimistic, because it
happens less often than some time ago.
snapd 2.48.3 in Focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
This bug affects me, too, on Kubuntu 20.10:
snap2.48.3+20.10
snapd 2.48.3+20.10
series 16
ubuntu 20.10
kernel 5.8.0-43-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
I still experience this bug:
$ snap --version
snap2.48.2
snapd 2.48.2
series 16
ubuntu 20.04
kernel 5.4.0-64-generic
I looked at the service logs for snapd and everytime I have experienced this
issue it was due to this:
snapd[986]: autorefresh.go:467: Cannot prepare auto-refresh change
I realize that I do not experience this bug anymore. Any other feedback
?
$ snap --version
snap2.48.1
snapd 2.48.1
series 16
ubuntu 20.04
kernel 5.8.0-34-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nov 28 18:54:55 hostname systemd[1]: Started Snap Daemon.
Nov 28 18:55:06 hostname snapd[770]: main.go:155: Exiting on terminated signal.
Nov 28 18:55:06 hostname systemd[1]: Stopping Snap Daemon...
Nov 28 18:55:19 hostname snapd[770]: autorefresh.go:398: Cannot prepare
auto-refresh change due to
Happened now on a fresh install od ubuntu desktop 20.04.1.
It does not happen at every shutdown. It happened only at the 1st shutdown that
I did after 4 minutes of uptime. Could be snapd working for updating/upgrading
something?
--
You received this bug notification because you are a member of
It happens at a clean, fesh, new install (wiped disk) of Ubuntu 20.04
Budgie without any snap packages manually installed after first boot,
when I want to restart because updates were installed.
Do we actually need Snap Daemon if you avoid installing any Snap
packages? I never go for the Snap
I have this bug in 20.10 (upgraded from 20.04). On shutdown it always
waits for 90 seconds, then it times out and the shutdown proceeds
normally. I have the same log as in:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873550/comments/3
--
You received this bug notification because you
I still experience this bug in Focal (up to date). Happens at least 50%
of shutdowns, delayed between 30s and 1m33s limit.
-- Logs begin at Fri 2020-03-06 07:41:08 CET, end at Sat 2020-08-22 10:02:36
CEST. --
août 21 20:59:44 portable-fthx systemd[1]: Starting Snap Daemon...
août 21 20:59:44
Hi,
I'm facing the same issue with Ubuntu 18.04, at least to mention this annoying
issue does not impact only Ubuntu 20 users.
Here is the output of journalctl -e --no-pager -b -1 -u snapd:
-- Logs begin at Mon 2019-04-08 02:59:33 CEST, end at Sat 2020-08-22 09:40:26
CEST. --
août 22 00:58:54
Further to my comment #18 I haven't seen this issue for nearly two
months now so unsubscribing but changing status back to 'Confirmed' as
the information requested in comment #8 has been supplied and others
have since also said that they are affected by this issue.
** Changed in: snapd (Ubuntu)
Having the same issue here on a fresh 20.04 installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
Snappy daemon reaches 1min30s timeout during shutdown process
To manage
I did a fresh install of Ubuntu 20.04 a couple of days ago, however
today I started getting delayed shutdown due to this bug. I even tried
re-installing Ubuntu 20.04, but after the first system update itself the
shutdown was delayed.
$ snap --version
snap2.44.3+20.04
snapd 2.44.3+20.04
First report of timeout since April 29:
May 14 21:28:54 n1644 systemd[1]: Stopping Snap Daemon...
May 14 21:28:54 n1644 snapd[979]: main.go:155: Exiting on terminated signal.
May 14 21:29:19 n1644 snapd[979]: daemon.go:583: WARNING: cannot gracefully
shut down in-flight snapd API activity
Well, there was a timeout issue last night, snapd 2.45pre3...
The only change I made in the day before was installing gnome-3-34 stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
So far I did not have a timeout issue with snapd 2.45~pre2+.
3 or 4 shutdowns.
With 2.44.x, snapd or core, the bug was here.
PS: I installed a Focal VM with current files and, yes, snapd is
installed, not core. But I'm 100 % sure it was core in my some-weeks-old
Focal VM.
--
You received this
Timeout issue with core 16-2.45~pre1 (9160) too.
I try with candidate (snapd 2.44.5).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
Snappy daemon reaches 1min30s timeout during
Ian, Yes that is correct I only see this slowdown or timeout on this one
upgraded installation that doesn't have the snapd snap.
However, I rebooted immediately prior to replying here and no timeout. I
reboot most days due to kernel updates or needing to boot into another
Ubuntu installation but
There is a timeout issue for both snapd and core.
Initial bug report description was made with snapd installed.
I reverted to core beta channel, since I did not see at first that
candidate does not use snapd 2.45. I'll check that when I'll have time,
maybe tonight.
--
You received this bug
Sorry if I wasn't clear on this, but if you upgraded from 19.10 to 20.04
then AFAIK you will not have gotten the snapd snap at all. The snapd
snap will only automatically get installed with a fresh, recent,
installation. I don't have a more precise definition of "recent", other
than the released
Changed to candidate channel for core, sorry.
It seems that 9209 > 9160...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
Title:
Snappy daemon reaches 1min30s timeout during shutdown process
That's odd.
In a clean VM 20.04 installed maybe 3 weeks ago, I get (sorry for encoding
glitches) :
$ snap list
NomVersion R\u00e9vision Suivi
\u00c9diteur Notes
core 16-2.44.3 9066 latest/stable
canonical\u2713 core
I'm a little confused now as my "n1644" installation doesn't have the
snapd snap installed:
paul@n1644:~$ snap list
Name Version Rev Tracking
Publisher Notes
canonical-livepatch 9.5.5 95latest/stable
canonical✓ -
@paulw2u the logs suggest the snapd snap is either from beta or edge
channels, can you confirm?
Anyone experiencing the problem, can you try snapd from the beta
channel? `snap refresh --beta snapd`.
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
Ok I still experience this bug, roughly 75 % of shutdowns.
"snap changes" don't return anything relevant, just a void refresh this
morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873550
This issue does appear to be specific to using the snapd snap, since the
snapd.failure unit is the service that gets triggered after the snapd
service proper fails to exit gracefully.
If someone does hit this again, it would be useful to see output from
snap changes
ASAP after the slowdown
Well, I managed to install snaps like in native 20.04 and since that
moment I do not experience any 1m30s timeout issue. Maybe it's not the
solution, it has to be tested for some shutdowns.
In my Focal (19.10 upgrade) without any snap stuff installed:
First, obviously...:
apt install snapd
To
I noticed today a difference between 20.04 native and 19.10 upgrade.
Upgrade : snapd snap have to be installed to install snap-store
(ubuntu-20.04 channel). Native : snapd snap is not installed. Don't
know if it's related.
--
You received this bug notification because you are a member of Ubuntu
Hi Ian, I've shutdown and restarted several times since my comment above
and I'm not seeing any delays on shutting down or rebooting now. But
here are a some extracts from the last two weeks:
Apr 08 11:46:59 n1644 systemd[1]: Stopping Snap Daemon...
Apr 08 11:47:24 n1644 snapd[980]:
Hi, can you paste logs for snapd from an affected boot? i.e. run
journalctl -e --no-pager -b -1 -u snapd
if the issue happened for you on the previous boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing this too. It took me a while to realise that pressing the
'Escape' key would allow me to watch the count reach 1m30s after which
shutdown or reboot would proceed normally.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
40 matches
Mail list logo
