Comment 3 for bug 1511435

Revision history for this message
Joachim Bauch (fancycode) wrote :

Also happens with non-sideloaded snaps:

● ubuntu-snappy.firstboot.service - Run snappy firstboot setup
   Loaded: loaded (/lib/systemd/system/ubuntu-snappy.firstboot.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2015-10-30 11:13:25 UTC; 1min 6s ago
  Process: 806 ExecStart=/usr/bin/snappy firstboot (code=exited, status=1/FAILURE)
 Main PID: 806 (code=exited, status=1/FAILURE)

Oct 30 11:13:24 localhost.localdomain systemd[1]: Starting Run snappy firstboot setup...
Oct 30 11:13:25 localhost.localdomain snappy[806]: config failed with: 'aa-exec: ERROR: profile 'spreed-webrtc.longsleep_snappy-config_0.24.8-4' does not exist
Oct 30 11:13:25 localhost.localdomain snappy[806]: ' (exit status 1)
Oct 30 11:13:25 localhost.localdomain systemd[1]: ubuntu-snappy.firstboot.service: main process exited, code=exited, status=1/FAILURE
Oct 30 11:13:25 localhost.localdomain systemd[1]: Failed to start Run snappy firstboot setup.
Oct 30 11:13:25 localhost.localdomain systemd[1]: Unit ubuntu-snappy.firstboot.service entered failed state.
Oct 30 11:13:25 localhost.localdomain systemd[1]: ubuntu-snappy.firstboot.service failed.