[Bug 1696207] Re: Chromium crash
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696207 Title: Chromium crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696207] Re: Chromium crash
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 0x5602ce7555f6 #5 0x5602ce755d99 #6 0x5602ce7560e3 #7 0x7fb6398d6821 #8 0x7fb63985ceea base::debug::TaskAnnotator::RunTask() #9 0x7fb639885e90 base::MessageLoop::RunTask() #10 0x7fb63988797d base::MessageLoop::DeferOrRunPendingTask() #11 0x7fb6393d #12 0x7fb639889300 base::MessagePumpLibevent::Run() #13 0x7fb639884f15 base::MessageLoop::RunHandler() #14 0x7fb6398af628 base::RunLoop::Run() #15 0x7fb6398dbe36 base::Thread::ThreadMain() #16 0x7fb6398d6726 #17 0x7fb639b7c6ba start_thread #18 0x7fb62322b3dd clone r8: 002e r9: 5602d01a958c r10: r11: 7fb6232b8f50 r12: 7fb591ff8ff0 r13: 0008 r14: 0008 r15: 7fb591ff8eb0 di: si: 7fb591ff8eb0 bp: 7fb591ff8f00 bx: 7fb591ff8eb0 dx: 005e ax: cx: 5602d2aaf950 sp: 7fb591ff8e60 ip: 5602ce752d68 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. I've tried to install the suggested debug package, so I can't collect a better output either. It's complaining that I'm using an unmet version of Chromium. I'm not using a nightly build or any kind newer than the one available in the official repository - at least that I know of: $ sudo apt install chromium-browser-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: chromium-browser-dbgsym : Depends: chromium-browser (= 58.0.3029.110-0ubuntu0.16.04.1281) but 59.0.3071.86-0ubuntu0.16.04.1285 is to be installed E: Unable to correct problems, you have held broken packages. The only repo for chromium that I can find on my system is /etc/apt/sources.list.d/canonical-chromium-builds-ubuntu-stage- xenial.list: deb http://ppa.launchpad.net/canonical-chromium-builds/stage/ubuntu xenial main -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696207 Title: Chromium crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
... 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: 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 again: $ sudo apt-mark unhold linux-raspi2 linux-image-raspi2 linux-headers-raspi2 5) Repeat step 2. 6) Power off the device and change the config file, see: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/comments/31 https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/comments/32 https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/comments/33 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
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 to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
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 cant seem to find the config.txt file, but i can find /boot/config-4.4.0-1009-raspi2. But the variables you're referring to aren't in this file. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
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 comes. But the developer/maintainer explicitly note that the RPi3 isn't official, and by that we need to understand that the work on the project can stop whenever he decide to. He's not obligated to do any action to it. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
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 Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
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/1652270/comments/10. Thanks! -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
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 initrd.img-4.4.0-1009-raspi2
abi-4.4.0-1009-raspi2 initrd.img-4.4.0-1040-raspi2
abi-4.4.0-1040-raspi2 initrd.img.old
config-4.4.0-1009-raspi2 vmlinuz
config-4.4.0-1040-raspi2 vmlinuz-4.4.0-1009-raspi2
firmware vmlinuz-4.4.0-1040-raspi2
grub vmlinuz.old
# sudo apt-get purge linux-*-4.4.0-1040-raspi2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'linux-tools-4.4.0-1040-raspi2' for glob
'linux-*-4.4.0-1040-raspi2'
Note, selecting 'linux-headers-4.4.0-1040-raspi2' for glob
'linux-*-4.4.0-1040-raspi2'
Note, selecting 'linux-image-4.4.0-1040-raspi2' for glob
'linux-*-4.4.0-1040-raspi2'
Package 'linux-tools-4.4.0-1040-raspi2' is not installed, so not removed
The following package was automatically installed and is no longer required:
linux-raspi2-headers-4.4.0-1040
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
linux-headers-4.4.0-1040-raspi2* linux-headers-raspi2*
linux-image-4.4.0-1040-raspi2* linux-image-raspi2* linux-raspi2*
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 112 MB disk space will be freed.
Do you want to continue? [Y/n] y
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US",
LC_ALL = (unset),
LC_PAPER = "nb_NO.UTF-8",
LC_NUMERIC = "nb_NO.UTF-8",
LC_IDENTIFICATION = "nb_NO.UTF-8",
LC_MEASUREMENT = "nb_NO.UTF-8",
LC_NAME = "nb_NO.UTF-8",
LC_TELEPHONE = "nb_NO.UTF-8",
LC_ADDRESS = "nb_NO.UTF-8",
LC_MONETARY = "nb_NO.UTF-8",
LC_TIME = "nb_NO.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 78930 files and directories currently installed.)
Removing linux-raspi2 (4.4.0.1040.39) ...
Removing linux-headers-raspi2 (4.4.0.1040.39) ...
Removing linux-headers-4.4.0-1040-raspi2 (4.4.0-1040.47) ...
Removing linux-image-raspi2 (4.4.0.1040.39) ...
Removing linux-image-4.4.0-1040-raspi2 (4.4.0-1040.47) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-1040-raspi2
/boot/vmlinuz-4.4.0-1040-raspi2
update-initramfs: Deleting /boot/initrd.img-4.4.0-1040-raspi2
run-parts: executing /etc/kernel/postrm.d/zz-flash-kernel 4.4.0-1040-raspi2
/boot/vmlinuz-4.4.0-1040-raspi2
Ignoring old or unknown version 4.4.0-1040-raspi2 (latest is 4.4.0-1009-raspi2)
The link /boot/vmlinuz is a damaged link
Removing symbolic link vmlinuz
you may need to re-run your boot loader[grub]
The link /boot/initrd.img is a damaged link
Removing symbolic link initrd.img
you may need to re-run your boot loader[grub]
Purging configuration files for linux-image-4.4.0-1040-raspi2 (4.4.0-1040.47)
...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-1040-raspi2
/boot/vmlinuz-4.4.0-1040-raspi2
run-parts: executing /etc/kernel/postrm.d/zz-flash-kernel 4.4.0-1040-raspi2
/boot/vmlinuz-4.4.0-1040-raspi2
# exit
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
