Installed Ubuntu (mainline) daily build yesterday, and this morning was going to install a few snap application and I get this message “error: too early for operation, device not yet seeded or device model not acknowledged” in both terminal and in GNOME Software.
snap changes
error: no changes found
What’s the output of journalctl -u snapd?
– Logs begin at Wed 2019-07-10 21:42:39 CDT, end at Thu 2019-07-11 06:17:48 CDT
Jul 10 21:43:06 Inspiron-3451 systemd[1]: Starting Snappy daemon…
Jul 10 21:43:10 Inspiron-3451 snapd[610]: AppArmor status: apparmor is enabled a
Jul 10 21:43:12 Inspiron-3451 snapd[610]: helpers.go:146: error trying to compar
Jul 10 21:43:12 Inspiron-3451 snapd[610]: daemon.go:379: started snapd/2.39.2+19
Jul 10 21:43:12 Inspiron-3451 systemd[1]: Started Snappy daemon.
Jul 10 21:43:19 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error
Jul 10 21:48:12 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error
Jul 10 21:50:17 Inspiron-3451 snapd[610]: 2019/07/10 21:50:17 Unsolicited respon
Jul 10 21:53:12 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error
Jul 10 21:58:12 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error
Jul 10 21:58:40 Inspiron-3451 snapd[610]: 2019/07/10 21:58:40 Unsolicited respon
Jul 11 05:10:27 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error
Jul 11 05:10:48 Inspiron-3451 snapd[610]: api.go:1079: Installing snap “brave” r
Jul 11 05:11:57 Inspiron-3451 snapd[610]: api.go:1079: Installing snap “brave” r
Jul 11 05:12:16 Inspiron-3451 snapd[610]: api.go:1079: Installing snap “brave” r
Jul 11 05:12:44 Inspiron-3451 snapd[610]: 2019/07/11 05:12:44 Unsolicited respon
Jul 11 05:14:48 Inspiron-3451 snapd[610]: api.go:1079: Installing snap "chromium
Jul 11 05:15:27 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error
Jul 11 05:16:19 Inspiron-3451 snapd[610]: main.go:147: Exiting on terminated sig
Jul 11 05:16:19 Inspiron-3451 systemd[1]: Stopping Snappy daemon…
Jul 11 05:16:24 Inspiron-3451 snapd[610]: cannot run daemon: cannot gracefully f
Jul 11 05:16:24 Inspiron-3451 systemd[1]: snapd.service: Main process exited, co
Jul 11 05:16:24 Inspiron-3451 systemd[1]: snapd.service: Failed with result 'exi
Jul 11 05:16:24 Inspiron-3451 systemd[1]: Stopped Snappy daemon.
Jul 11 05:16:24 Inspiron-3451 systemd[1]: snapd.service: Triggering OnFailure= d
Jul 11 05:16:58 Inspiron-3451 systemd[1]: Starting Snappy daemon…
Jul 11 05:16:58 Inspiron-3451 snapd[11838]: AppArmor status: apparmor is enabled
Jul 11 05:16:58 Inspiron-3451 snapd[11838]: daemon.go:379: started snapd/2.39.2+
Jul 11 05:16:58 Inspiron-3451 systemd[1]: Started Snappy daemon.
Jul 11 05:16:59 Inspiron-3451 snapd[11838]: stateengine.go:102: state ensure err
Jul 11 05:16:59 Inspiron-3451 snapd[11838]: stateengine.go:102: state ensure err
Jul 11 05:21:59 Inspiron-3451 snapd[11838]: stateengine.go:102: state ensure err
Jul 11 05:22:35 Inspiron-3451 systemd[1]: Stopping Snappy daemon…
Jul 11 05:22:36 Inspiron-3451 snapd[11838]: main.go:147: Exiting on terminated s
Jul 11 05:22:36 Inspiron-3451 systemd[1]: snapd.service: Succeeded.
Jul 11 05:22:36 Inspiron-3451 systemd[1]: Stopped Snappy daemon.
– Reboot –
Jul 11 05:23:12 Inspiron-3451 systemd[1]: Starting Snappy daemon…
Jul 11 05:23:16 Inspiron-3451 snapd[616]: AppArmor status: apparmor is enabled a
Jul 11 05:23:17 Inspiron-3451 snapd[616]: daemon.go:379: started snapd/2.39.2+19
Jul 11 05:23:18 Inspiron-3451 systemd[1]: Started Snappy daemon.
Jul 11 05:23:19 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 05:24:36 Inspiron-3451 snapd[616]: api.go:1079: Installing snap “brave” r
Jul 11 05:25:56 Inspiron-3451 snapd[616]: api.go:1079: Installing snap “brave” r
Jul 11 05:28:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 05:33:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 05:38:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 05:43:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 05:48:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 05:53:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 05:58:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 06:03:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 06:08:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
Jul 11 06:13:18 Inspiron-3451 snapd[616]: stateengine.go:102: state ensure error
The log is truncated. Can you use journalctl -u snapd --no-pager ?
Okay I will do that once I get home from work.
– Logs begin at Wed 2019-07-10 21:42:39 CDT, end at Thu 2019-07-11 16:25:39 CDT. –
Jul 10 21:43:06 Inspiron-3451 systemd[1]: Starting Snappy daemon…
Jul 10 21:43:10 Inspiron-3451 snapd[610]: AppArmor status: apparmor is enabled and all features are available
Jul 10 21:43:12 Inspiron-3451 snapd[610]: helpers.go:146: error trying to compare the snap system key: system-key missing on disk
Jul 10 21:43:12 Inspiron-3451 snapd[610]: daemon.go:379: started snapd/2.39.2+19.10ubuntu1 (series 16; classic) ubuntu/19.10 (amd64) linux/5.0.0-20-generic.
Jul 10 21:43:12 Inspiron-3451 systemd[1]: Started Snappy daemon.
Jul 10 21:43:19 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error: devicemgr: cannot proceed without seeding “core”
Jul 10 21:48:12 Inspiron-3451 snapd[610]: stateengine.go:102: state ensure error: devicemgr: cannot proceed without seeding “core”
Jul 10 21:50:17 Inspiron-3451 snapd[610]: 2019/07/10 21:50:17 Unsolicited response received on idle HTTP channel starting with “HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n
Is this a vanilla Ubuntu 19.10 system?
Can you provide the output of snap changes command and the contents of /var/lib/snapd/seed/seed.yaml?
Yes, no modification whatsoever.
snap changes
error: no changes found
cat /var/lib/snapd/seed/seed.yaml
snaps:
-
name: core18
channel: stable
file: core18_1049.snap
-
name: snapd
channel: stable
file: snapd_3646.snap
-
name: gnome-3-28-1804
channel: stable/ubuntu-19.10
file: gnome-3-28-1804_67.snap
-
name: gnome-calculator
channel: stable/ubuntu-19.10
file: gnome-calculator_406.snap
-
name: gnome-characters
channel: stable/ubuntu-19.10
file: gnome-characters_296.snap
-
name: gnome-logs
channel: stable/ubuntu-19.10
file: gnome-logs_61.snap
-
name: gnome-system-monitor
channel: stable/ubuntu-19.10
file: gnome-system-monitor_100.snap
-
name: gtk-common-themes
channel: stable/ubuntu-19.10
file: gtk-common-themes_1313.snapMainline as in using the mainline kernel?
Yes downloaded from http://cdimage.ubuntu.com/daily-live/current/.
I also noticed none of the snap GNOME apps are installed. I don’t have Calculator, Logs, System Monitor, etc.
that seed.yaml is broken, I suspect. To confirm, could you sudo snap info --verbose /var/lib/snapd/seed/snaps/*.snap | grep base: please?
summary: Runtime environment based on Ubuntu 18.04
type: base
base: core18
base: core18
base: core18
base: core18
base: core18
base: core18
So, the images are broken because they ship a broken seed.yaml. Please address this with the images authors if you can.
How would I do that?
wait, I was wrong, confused by the formatting. The first entry in seed.yaml is core18, so it’s not that. Hmm.
To reproduce this issue I need to know the exact iso you downloaded (“current” changes twice daily AFAICT). I’ll download one of the -11 images to see where the full name of it is.
As I understand it, this his one is missing core. Since there’s no other base for the model, we default to requiring core to be seeded.
To get the exact image you used, look at the cdrom: line in `/etc/apt/sources.list,
ah, indeed, that’s what cannot proceed without seeding core is about 
ok, i’ll point people at this image thing (already planned).
@motang to unblock you, apt purge snapd will remove snapd and the bogus seed.yaml, and then apt install snapd will get you back a pristine snapd without the seed. You can then manually install anything you want.
HTH, HAND.
