Oh. I wondered what «stage» meant in the URL, and looked it up. Looks
like it's the staging (a.k.a proposed?) repo for upcoming releases, with
unstable chromium builds. Do not have any idea how that repo has been
added to my system. Anyway Removing it and re-installing chromium
did the trick.
Hi.
I'm having the same problem:
Chromium 59.0.3071.86 Built on Ubuntu , running on Ubuntu 16.04
This is the output from terminal:
Received signal 11 SEGV_MAPERR 0010
#0 0x7fb63985b425 base::debug::StackTrace::StackTrace()
#1 0x7fb63985b80b
#2 0x7fb639b86390
#3 0x5602ce752d68
#4 0x56
Sorry, #6 should be done before #4. Just tested it, and it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage notif
... I assumed you can have a fresh install since you're mentioning
"first boot".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
Hi. Could you try to:
1) on first boot, hold packages that breakes our system:
$ sudo apt-mark hold linux-raspi2 linux-image-raspi2 linux-headers-raspi2
2) Do an upgrade:
$ sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade
3) Reboot:
$ sudo reboot
4) Unhold the packages agai
Found it, in the system-boot partition. :) And it worked! Going to
unmark the 1040-kernel now on one of the cluster nodes now (easier to
just copy a node if something fails), to check if it boots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Can i ask where this config.txt file is located?
I experience this bug now, so I dont know if it's related to the topic
here, or if its a new one. Haven't installed the "broken" kernels (1038
or newer), and it have working flawlessly - until I rebooted yesterday.
Now I'm stuck in this loop.
But,
I'm running a cluster of 3 RPi3 and 2 RPi2. For what I'm aware of,
there's only troubles with the RPi2. Both of mine RPi2s boots as
expected, so is the RPi2 bug you're referring to related to something
else?
I agree to the ETA part, it's frustrating to wait for a fix - and don't even
know if it c
Guys. Remember that this is a community build, and not officially
supported by Ubuntu. We need to thank those who's doing this work, as it
helps out with further development of Ubuntu itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Unfortunately, all of mine have upgraded, but I only rebooted one of
them - and hoping the others will keep running until a fix is out. Or do
anyone know a step by step solution for this, that wont prevent further
updates later, ref: https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1652
Same with to kernel «1040» as well, I upgraded through «dist-upgrade»
today (11. january 2016). Tried to roll back by mounting the sd-card and
chroot (sudo proot -q qemu-arm -S /path/to/fs), then:
# ls /boot/
System.map-4.4.0-1009-raspi2 initrd.img
System.map-4.4.0-1040-raspi2 initr
11 matches
Mail list logo
