The second attempt worked, so it really looks like a race condition
where snapd is trying to install a snap while not fully initialized?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848658
Title:
I have just observed this when installing chromium-browser (which
installs the chromium snap) in a clean 20.04 VM.
ubuntu@focalvm:~$ LANG=C snap changes
ID Status Spawn Ready Summary
1Donetoday at 18:06 CET today at 18:07 CET Initialize system state
2Do
[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/1848658
T
It is possible, I don't know if there was a store outage during that
time, but it's possible. Without more detail it's hard to say though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848658
Title:
Ian, it looks like the error was transient, so unfortunately I doubt we'll find
out.
Could it be that the store was unreachable during a short window of time, at
the very moment Luis attempted to install chromium?
Luis, can you share the output of "snap changes" and "snap known
serial", as reque
I added a snapd task, as I'd like to hear snapd developers' opinion on
this "error: too early for operation, device not yet seeded or device
model not acknowledged".
** Summary changed:
- package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: el subproceso nuevo paquete
What does `snap changes` show here?
Also what does `snap known serial` show on this machine?
Typically that error is for when a device has not yet communicated with
the snap store to get a serial assertion, and thus can't install snaps.
Perhaps this device does not have network access to the stor
