Hello.
with Daily ubuntu.
with snap firefox_1%3a
The message is.
still unable to contact the Store. Trying for another 20 minutes.
after a message for continue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927071
Title:
Fresh install of chromium-browser during installer-like
I confirm this bug. It happens using desktop installer iso system (I
don't have any connectivity issue).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927071
Title:
Fresh install of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927071
** Changed in: chromium-browser (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927071
Title:
Fresh install of chromium-browser during installer-like process,
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not a container, this is the desktop installer iso system.
Yes, "snap list" returns something in the installer system but it is run in the
chrooted env.
"chroot /target snap list" is working too. It should not, is it right ?
As said in the previous issue, i want those snap to be
That looks like a slightly different issue: the preinst script is
detecting that snapd is usable by checking for the existence of
/run/snapd.socket in the container/chroot. In your case it appears that
the socket exists, meaning that snapd is installed and running. But it
fails to contact the snap
