By editing /target/etc/environment and setting SNAPD_DEBUG=1 etc before
rebooting into the new system, I get
http://paste.ubuntu.com/p/jTQb2YHhq3/
You can see there snapd coming up and seeding the system, and you can
also watch as pid 724 (snapd-seeded.service) polling, waiting for the
seeding to be done. Grep for pid=724 to follow this one.
That seeding gets marked as done on the line
Apr 11 12:04:29 ubuntu snapd[2115]: daemon.go:296: DEBUG:
pid=724;uid=0;socket=/run/snapd.socket; GET
/v2/snaps/system/conf?keys=seed.loaded 37.034783ms 200
and then 724 stops, as it should. Right after it you start getting
pid=3635 lines, which correspond to gnome-software (via a line in syslog
saying «gnome-software[3635]: disabled plugins: dpkg, dummy, repos,
epiphany»). gnome-software successfully queries snapd for featured and
installed snaps (and if you start the gui, they're right there).
However you can _also_ see a pid=1825. That pid corresponds to gnome-
initial-setup.
The single pid=1825 entry arrives _before snapd has seeded the system_,
and in particular just as snapd has scheduled a restart. I can only
assume that gnome-initial-setup gets back the list of snaps, then tries
to do a find for featured snaps and fails (because snapd is restarting),
and that is the point where it logs
Apr 11 12:03:46 ubuntu gnome-initial-s[1825]: Failed to get featured
snaps: Failed to read from snapd: Error receiving data: Connection reset
by peer
note that this is racy, and gnome-initial-setup could just as well have logged
'Failed to get installed snaps' when the initial query fails, but succeeded to
get the featured snaps (and then would go on to break in interesting ways as it
tries to look things up in a nil container).
In any case, two solutions:
1. retry queries when you get an error from querying snapd (as opposed
to an error response). This is what the 'snap' client does: retries
every 250ms for up to 5s.
2. wait for snapd to be loaded
even with (2), (1) should probably be done anyway (but it'll be harder
to hit).
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-initial-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1824188
Title:
Software tab is empty on clean 19.04 install
Status in gnome-initial-setup package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Invalid
Bug description:
Did a clean install of Ubuntu 19.04.
Rebooted into the new installation.
Started using it, and after a short while the gnome initial setup appeared.
I went through each step, but the final one "You're ready to go!" should have
some software listed from the snap store, but doesn't.
I have a working internet connection (I'm filing list bug from it)
See screenshot
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-initial-setup 3.32.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 17:13:41 2019
InstallationDate: Installed on 2019-04-10 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1824188/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
