/srv/irclogs.ubuntu.com/2018/11/03/#snappy.txt

mupPR snapcraft#2389 opened: repo: run `apt update` before `apt install` <Created by abitrolly> <https://github.com/snapcore/snapcraft/pull/2389>07:36
ackkhi, anyone that could help with a rpi3 issue with ubuntu core?09:22
ackkis there a tool to modify the uboot.env file?09:48
zygaackk: I'm here but I don't know enough about rpi3 to help11:51
zygaackk: the config system can toggle some options in the boot process11:51
zygaackk: but not sure what you really need11:51
ackkzyga, hi, so, I have rpi3 with ubuntu core, at some point it was rebooted and didn't come back. turns out the pi2 kernel snap was updated but the var in the uboot env wasn't, so it was trying to boot from a nonexistent kernel12:14
ackkzyga, I fixed that (I wonder if it's a ubuntu bug), but now the initramfs can't mount the root partition for some reason. it's ext4, but it fails after trying ext3 and ext2, saying there's some incompatibility12:14
ackkI can mount it fine on my pc12:14
mupPR snapd#6089 closed: tests: install dependencies during prepare <Simple 😃> <Created by sergiocazzolato> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/6089>12:43
ograackk, from the runninf system you can use fw_printenv and fw_setenv to modify uboot.env13:32
ogra*running13:32
ograand indeed you can manage uboot env from the uboot shell from the serial console like on all embedded boards we support13:33
ackkogra yeah I was looking for something to change it from my pc, found about uboot-go from mvo :)13:34
ograi have never seen it fail to set the vars though ... that would definitely be a bug if you didnt tinker with the card (not properly unmounting it or some such when you used it in a PC between boots)13:34
ackkogra, so it turns out the snaps for core and kerner were wrong in the env13:34
ackknot sure why they didn't get updated13:34
ograi have pi's here that run the same image since 2 years without ever failing13:34
ackkogra, yeah that's weird13:35
ograthe ext2/3/4 warnings are nroaml btw ... the ext4 driver loops over all possible extX versions it can support and pronts that nonsense13:36
ogra*prints13:36
ogra*normal13:36
ograif you can capture a full serial boot log and dump it to a pastebin i can take a look13:37
ackkogra, is it normal that the core snap is marked as disabled?13:41
ackkogra, (same for the pi2 kernel) https://paste.ubuntu.com/p/F2mrphCvfr/13:42
ograno, something is seriously broken13:46
ograwhat image was that originally ?13:46
ogracore kernel and gadget should never be marked as disabled on UC13:47
ackkogra, the official pi3 image13:48
ackkfor ubuntu core13:48
ograhmm, strange13:48
ackkogra, so I tried to enable core, it rebooted but didn't come back13:48
ograi still wonder how you got into that situation in the first place13:49
ackkogra, should the pi2-kernel be enaled on a pi3?13:49
ograyes13:49
ackkogra, it's my nextcloud box, it was just there running13:49
ackkogra, I had a power loss, maybe something broke there13:49
ograthe name is a bit confusing, it should be pi-kernel13:49
ograa power loss shouldnt cause this ... the system should recover13:50
ackknothing else happened13:50
ackksnap_core=core_4916.snap13:50
ackksnap_kernel=pi2-kernel_73.snap13:50
ackksnap_mode=13:50
ackksnap_try_core=core_5331.snap13:50
ackkthis looks better13:50
ogranot really ...13:50
ackkwhy?13:51
ograsndp should have unset snap_try_core after it verified the boot13:51
ackkwell it hasn't yet13:51
ogra*snapd13:51
ackkI just reenabled the snap13:51
ackklemme try to reboot13:52
ograechnically you should just have rebooted until the system fixed itself ... without touching anything13:52
ograif you touched any vars they might be out of sync with what snapd expects13:52
ackkogra, I did touch snap_core and snap_kernel as they were set to values that didn't exist and the pi wasn't booting13:53
ograi assume there is something wrong with the watchdog ... the system should have done this on its own (rebooting until it fxed itself)13:53
ogracould it be that your SD is/was full ?13:54
ackkogra, no13:54
ograwe dont really have protection against that yet13:54
ackkogra, I rebooted, but it's still on the old core13:54
ackkand the try is still there13:54
ograthats the only way i can imagine that the vars point to something non-existing13:54
ogratry "snap refresh core"13:54
ackkack@nextcloud:~$ df -h | grep mmc13:55
ackk/dev/mmcblk0p2  3.6G  964M  2.4G  29% /writable13:55
ackk/dev/mmcblk0p1  127M   38M   89M  30% /boot/uboot13:55
ackkogra, ^ fwiw13:55
ackkogra, ok it's downloading a newer core now13:55
ogralets see how that goes13:55
ackkrebooting now13:57
ogragood13:57
ackkwell, it's supposed to, it doesn't seem it is13:58
ograwhats on the console ?13:58
ackkok finally13:58
ackknothing13:58
ackkbut it's rebooting now13:58
ografinally ? you mean it booted ?13:58
ackkit's booting13:59
ograk13:59
ackkogra, ok, everything seems green now14:09
ograhow does the kernel look in snap list ?14:09
ograenable again ?14:09
ogra*enabled14:10
ackkpi2-kernel  4.4.0-1098.106  73    stable    canonical✓  kernel14:10
ackkyep, everything enabled14:10
ograok .. thats fine but outddated ...14:10
ograsnap refresh pi2-kernel14:10
ograthen you should be back up to date14:10
ogra(current stable is rev 74)14:11
ackkcool, thanks14:13
=== fayg0 is now known as gh0st^
=== gh0st^ is now known as fayg0
=== phoenix_firebrd is now known as murthy
mupBug #1600136 changed: App indicator does not show icon for Qt apps or with custom icons <isv> <patch> <snap-desktop-issue> <verification-done> <appmenu-qt5 (Ubuntu):Fix Released by 3v1n0> <libappindicator (Ubuntu):Fix Released by 3v1n0> <qtbase-opensource-src (Ubuntu):Fix Released by 3v1n0> <sni-qt22:20
mup(Ubuntu):Fix Released by 3v1n0> <appmenu-qt5 (Ubuntu Xenial):Fix Released> <libappindicator (Ubuntu Xenial):Fix Released> <qtbase-opensource-src (Ubuntu Xenial):Confirmed> <sni-qt (Ubuntu Xenial):Fix Released> <https://launchpad.net/bugs/1600136>22:20

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!