Boo! I thought you'd found an interesting one! :-)
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
snap list: unexpected fault address 0xf1f0
To manage notifications ab
Ok, doing a second intall of the same image onto a different SD card
comes up without problems. Closing as HW error.
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
So, not sure whether its the image or putting the image on that sd card.
But apt-get install --reinstall snapd fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
snap list: unexp
Any incantation of snap results in the same explosion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
snap list: unexpected fault address 0xf1f0
To manage notifications about thi
Should be more or less a "normal" raspi2, only that I enabled a little
LCD touchscreen and audio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
snap list: unexpected fault address 0xf
I wonder what happened to the traceback you clearly have in the
`systemctl status` you pasted in the description.
Anyway, is there anything special about this device?
Can you show us the output of `snap version`? what about `snap changes`?
--
You received this bug notification because you are a
Ok, again from cat without the cap:
-- Logs begin at Do 2016-02-11 16:28:01 UTC, end at Mi 2018-08-01 13:09:31 UTC.
--
Aug 01 11:52:47 ubuntu systemd[1]: Starting Snappy daemon...
Aug 01 11:52:48 ubuntu snapd[1045]: AppArmor status: apparmor is enabled and
all features are available
Aug 01 11:52
Here is the output, though it looks even less verbose:
sudo journalctl -u snapd
-- Logs begin at Do 2016-02-11 16:28:01 UTC, end at Mi 2018-08-01 13:07:25 UTC.
--
Aug 01 11:52:47 ubuntu systemd[1]: Starting Snappy daemon...
Aug 01 11:52:48 ubuntu snapd[1045]: AppArmor status: apparmor is enabled
Could you attach the output of 'journalctl -u snapd'? There's a
traceback in there, that's only partially visible in the 'status'
output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
Also looks to be causing the following service to fail:
● snapd.seeded.service - Wait until snapd is fully seeded
Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-08-01 11:52:49 UTC; 25min
ago
Main
10 matches
Mail list logo