No more preinstalled snap on Ubuntu 19.04?

That would be an error.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/disco/ubuntu/+build/158805/+files/buildlog_ubuntu_disco_amd64_ubuntu_BUILDING.txt.gz
still shows each of these snaps being downloaded to /var/lib/snapd/seed/ in
the squashfs.

Note that the 20190309 image has not passed automated testing. If your
purpose is to install Ubuntu, please use the current image,
http://cdimage.ubuntu.com/daily-live/current/ (which presently is
20190305.1).

There also seems to have been a regression in the manifest generation of
images, because no snaps are listed in the .manifest for any of the recent
dailies. However, examining the image shows that the snaps are all present
in the livefs as expected, at /var/lib/snapd/seed/snaps, and
/var/lib/snapd/seed/seed.yaml is populated. How do you see that the snaps
are not preinstalled? Is this while running the ISO as a live environment,
or after installation?

1 Like

After installation on my desktop in a test partition

corrado@corrado-p6-dd-0309:~$ inxi -Fx
System:    Host: corrado-p6-dd-0309 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 
           Desktop: Gnome 3.31.92 Distro: Ubuntu 19.04 (Disco Dingo) 
Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: <root required> UEFI: American Megatrends 
           v: P1.10 date: 05/11/2017 
CPU:       Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 
           L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
           Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 
           direct render: Yes 
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 
           Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:4 
           Sound Server: ALSA v: k4.19.0-13-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
           IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 
Drives:    Local Storage: total: 931.51 GiB used: 6.50 GiB (0.7%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
Partition: ID-1: / size: 31.25 GiB used: 6.49 GiB (20.8%) fs: ext4 dev: /dev/sda6 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 34.5 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 210 Uptime: 4m Memory: 7.50 GiB used: 1.08 GiB (14.4%) Init: systemd Compilers: gcc: 8.3.0 
           Shell: bash v: 5.0.2 inxi: 3.0.32 
corrado@corrado-p6-dd-0309:~$
corrado@corrado-p6-dd-0309:~$ snap list
Name             Version          Rev   Tracking  Publisher   Notes
core             16-2.37.2        6405  stable    canonical✓  core
gnome-3-26-1604  3.26.0.20190228  82    stable/…  canonical✓  -
corrado@corrado-p6-dd-0309:~$

@jibel maybe you want to take a look?

Reported on https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1819427

1 Like

I downloaded today’s pending image (20190311), all the seeded snaps are there both in the live session and after installation.

Were snaps in manifest even a thing for desktop images? I think snaps were never listed there. Take cosmic for instance (https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/cosmic/ubuntu/+build/147957) and the manifest file doesn’t list it: https://launchpadlibrarian.net/393750371/livecd.ubuntu.manifest.

This is something we added for multi-layered images in disco (which ubuntu-desktop isn’t due to the pending ubuntu-cdimage and debian-cd MP), but not for “flat” images.
CPC and ubuntu-server-live have their own hook that were written I guess one or two cycles ago to add them (and wasn’t generalized apparently at the time, unfortunately).
Adding to flat image would be trivial though.

Installed from today ISO Ubuntu 19.04 “Disco Dingo” - Alpha amd64 (20190311) and I have no snap in the live session nor in the installed one

ubuntu@ubuntu:~$ snap list
No snaps are installed yet. Try 'snap install hello-world'.
ubuntu@ubuntu:~$ cat /cdrom/.disk/info
ubuntu@ubuntu:~$ 

corrado@corrado-p6-dd-0311:~$ snap list
Name             Version          Rev   Tracking  Publisher   Notes
core             16-2.37.2        6405  stable    canonical✓  core
gnome-3-26-1604  3.26.0.20190228  82    stable/…  canonical✓  -
corrado@corrado-p6-dd-0311:~$ cat /var/log/installer/media-info
Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190311)
corrado@corrado-p6-dd-0311:~$

Give it a few minutes and run snap list again. They don’t show up in the list right away after boot, there is some seeding work after first boot. First time I ran “snap list” in today’s image it only showed 2 snaps but within another minute or so they all showed up.

2 Likes

Perhaps snap list should inform the user that seeding is in progress? CC @chipaca and @pedronis

1 Like

still no snap after 1 hour and reboot
corrado@corrado-p6-dd-0311:~$ snap list
Name Version Rev Tracking Publisher Notes
core 16-2.37.2 6405 stable canonical✓ core
gnome-3-26-1604 3.26.0.20190228 82 stable/… canonical✓ -
corrado@corrado-p6-dd-0311:~$ date
lun 11 mar 2019, 19:20:24, CET
corrado@corrado-p6-dd-0311:~$ cat /var/log/installer/media-info
Ubuntu 19.04 “Disco Dingo” - Alpha amd64 (20190311)corrado@corrado-p6-dd-0311:~$ inxi -SCIx
System:
Host: corrado-p6-dd-0311 Kernel: 5.0.0-7-generic x86_64 bits: 64
compiler: gcc v: 8.3.0 Desktop: Gnome 3.31.92
Distro: Ubuntu 19.04 (Disco Dingo)
CPU:
Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800
3: 800 4: 802
Info:
Processes: 234 Uptime: 23m Memory: 7.50 GiB used: 900.5 MiB (11.7%)
Init: systemd Compilers: gcc: 8.3.0 Shell: bash v: 5.0.2 inxi: 3.0.32
corrado@corrado-p6-dd-0311:~$

corrado@corrado-p6-dd-0311:~$ snap refresh
error: too early for operation, device not yet seeded or device model not acknowledged
corrado@corrado-p6-dd-0311:~$

That error from snap refresh shows there is a problem. @zyga-snapd any additional info we should look for to see why they snaps aren’t seeding on boot? It’s working fine for me in virtualbox with the same iso version

I’m not using virtualbox but a true install. let me know if you need more info.

What’s the output of journalctl -u snapd?

1 Like

We should collect logs of snapd.service, as Chipaca said above.

1 Like

corrado@corrado-p6-dd-0311:~$ journalctl -u snapd
– Logs begin at Mon 2019-03-11 18:15:42 CET, end at Tue 2019-03-12 09:42:37 CET
– No entries –

corrado@corrado-p6-dd-0311:~$ journalctl -b | grep snapd
mar 12 09:10:37 corrado-p6-dd-0311 /usr/lib/gdm3/gdm-x-session[1458]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop
mar 12 09:23:17 corrado-p6-dd-0311 org.gnome.Shell.desktop[2506]: (/usr/lib/firefox/firefox:4745): dconf-WARNING **: 09:23:17.983: Unable to open /var/lib/snapd/desktop/dconf/profile/user: Permission denied
mar 12 09:30:09 corrado-p6-dd-0311 org.gnome.Shell.desktop[2506]: (/usr/lib/firefox/firefox:5202): dconf-WARNING **: 09:30:09.377: Unable to open /var/lib/snapd/desktop/dconf/profile/user: Permission denied
corrado@corrado-p6-dd-0311:~$
1 Like

Ok, try this:

$ sudo systemctl edit snapd.service
[Service]
Environment=SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7
$ sudo systemctl restart snapd.service

and then, journalctl -u snapd again.

from sudo systemctl edit snapd.service … i see:
/etc/systemd/system/snapd.service.d/.#override.conf29adc235dded5904

corrado@corrado-p6-dd-0311:/etc/systemd/system$ cd snapd.service.d
corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$ ls
corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$ ls -a
.  ..  .#override.conf29adc235dded5904.save
corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$ cat .#override.conf29adc235dded5904.save
[Service]
Environment=SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7

corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$

that looks like you haven’t saved the file

corrado@corrado-p6-dd-0311:~$ cd /etc/systemd/system/snapd.service.d
corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$ cat override.conf
[Service]
Environment=SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7

corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$ sudo restart snapd.service
sudo: restart: command not found
corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$ sudo systemctl restart snapd.service
corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$ journalctl -u snapd
-- Logs begin at Mon 2019-03-11 18:15:42 CET, end at Tue 2019-03-12 12:42:57 CET. --
-- No entries --
corrado@corrado-p6-dd-0311:/etc/systemd/system/snapd.service.d$

I don’t know why you’ aren’t seeing logs, but let’s work around that for now. Try this:

sudo systemctl stop snapd.\*
sudo SNAPD_DEBUG=1 /usr/lib/snapd/snapd