• Before reporting problems with your board running Armbian, check the following:

    • 1. Check power supply, check SD card and check other people experiences   06/23/17

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information   06/24/17

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Chromium browser fails to launch
1 1

22 posts in this topic

Recommended Posts

Using Armbian 5.30 stable Ubuntu 16.04.2 LTS 3.4.113-sun8i
Linux orangepipc 3.4.113-sun8i #16 SMP PREEMPT Tue Jun 13 14:15:57 CEST 2017 armv7l armv7l armv7l GNU/Linux

 

Just updated my chromium from the pre-installed version 58.0.3029.110-0ubuntu0.16.04.1281 which worked fine to 59.0.3071.109-0ubuntu0.16.04.1289 which fails to start for some reason. You can see the window open up for a brief moment, then it crashes with the following error:

 

Received signal 4 <unknown> 0000b472df76
#0 0x0000b5381d12 base::debug::StackTrace::StackTrace()
#1 0x0000b5381952 base::debug::StackTrace::StackTrace()
#2 0x0000b5381ffc <unknown>
#3 0x0000b0783270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Received signal 4 <unknown> 0000b475ff76
#0 0x0000b53b3d12 base::debug::StackTrace::StackTrace()
#1 0x0000b53b3952 base::debug::StackTrace::StackTrace()
#2 0x0000b53b3ffc <unknown>
#3 0x0000b07b5270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.

 

Share this post


Link to post
Share on other sites

can you reproduce the error in a fresh build?? if not then it is not a software issue (bad sd card???)

 

reproduce the error on a fresh build using another GOOD sd card.

if you can reproduce the error, post logs, make of sd card, make of psu...so on

give the folks here the help they need to help you.

 

Share this post


Link to post
Share on other sites

Chromium for ARM has history of instability and lately it was working quite OK which was one of points that we start using it. I doubt it's related to any changes within Armbian. First we need to reproduce this error on other builds: Pine64, C2, ... than if the problem manifest there to, contact package maintainer. We don't have any intention or resources to fix Chromium bugs. 

If this is so, I would suggest rolling this package back or upgrade to fixed version when available.

 

Share this post


Link to post
Share on other sites

I have the same problem,
on the fresh Armbian the chrome-browser works OK
but after the apt update && apt upgrade I can't start chromium anymore

tested on OPI PC+ and on OPI Zero Plus H3

3 hours ago, Igor said:

If this is so, I would suggest rolling this package back

 

any clue how to do this "rolling back"?

 

thx

Share this post


Link to post
Share on other sites
7 hours ago, Bubba said:

can you reproduce the error in a fresh build??

Yes, I actually reported the problem only after doing a fresh install on another card first. So vanilla Armbian_5.30_Orangepipc_Ubuntu_xenial_default_3.4.113_desktop.img with single updated package as stated above.

 

7 hours ago, Bubba said:

if you can reproduce the error, post logs, make of sd card, make of psu...so on

give the folks here the help they need to help you.

Sure thing. What logs do you need, specifically? Nothing in syslog or systemd journal though. I'm not aware of any logging done by chromium, but I'm sure you can point me in the right direction there.

For the actual error message, see above. Card is a 16GB Sandisk Ultra UHC-I card I took from another SBC. PSU is the old Xunlong 3A one.

 

7 hours ago, Igor said:

If this is so, I would suggest rolling this package back or upgrade to fixed version when available.

How so? Apt-get tells me

E: Version '58.0.3029.110-0ubuntu0.16.04.1281' for 'chromium-browser' was not found

araczkowski likes this

Share this post


Link to post
Share on other sites

Hi,

I'm running a fairly fresh install of the desktop version of Armbian for the tinkerboard, and I'm running into a problem launching chromium-browser.  I have successfully downloaded and installed Firefox, but chromium is still defeating me. If I try to launch from the terminal I get;

     

nick@tinkerboard:~$ chromium-browser
[4393:4435:0707/193722.332119:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction Proxy DB: 3
[4393:4428:0707/193722.500948:ERROR:zygote_host_impl_linux.cc(254)] Failed to adjust OOM score of renderer with pid 4451: Permission denied
Received signal 4 <unknown> 0000b6243f76
#0 0x0000b6e97d12 base::debug::StackTrace::StackTrace()
#1 0x0000b6e97952 base::debug::StackTrace::StackTrace()
#2 0x0000b6e97ffc <unknown>
#3 0x0000b228c270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[4393:4428:0707/193722.881072:ERROR:zygote_host_impl_linux.cc(254)] Failed to adjust OOM score of renderer with pid 4464: Permission denied
[4449:4449:0707/193724.605459:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process.
[4393:4430:0707/193724.616051:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[4393:4430:0707/193724.616265:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[4393:4430:0707/193724.616399:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[4393:4430:0707/193724.616523:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[4393:4430:0707/193724.616663:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
Received signal 4 <unknown> 0000b627af76
#0 0x0000b6eced12 base::debug::StackTrace::StackTrace()
#1 0x0000b6ece952 base::debug::StackTrace::StackTrace()
#2 0x0000b6eceffc <unknown>
#3 0x0000b22c3270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.

 

Background -

- I have been running an very old version of Armbian for tinkerboard which I downloaded from a nightly several months ago. That also failed to run chromium, but I didn't attempt to launch it from the terminal. 

- Tinkerboard is powered from the gpio pins 

- This build installed today using etcher to a good quality microSD. The image was downloaded via a torrent a week ago.

 

I'm not very good at diagnosis and fixing, but can follow instructions if more information is needed.

 

Thanks for reading.

Share this post


Link to post
Share on other sites
nick@tinkerboard:~$ uname -a
Linux tinkerboard 4.4.73-rockchip #10 SMP Fri Jun 23 20:34:42 CEST 2017 armv7l armv7l armv7l GNU/Linux

 

Share this post


Link to post
Share on other sites

It is definitely problem in the new chromium. 
But no fix/solution so far. The workaround that I'm using:
1. on the fresh armbian before apt update && apt upgrade
2. sudo apt install synaptic
3. in synaptic lock the current chromium version (58.0.3029.110-0ubuntu0.16.04.1281)

4. apt update && apt upgrade


 

synaptic.png

Share this post


Link to post
Share on other sites

So there's no way to downgrade once you have the broken version?

 

$ sudo apt-get install chromium-browser=58.0.3029.110-0ubuntu0.16.04.1281
E: Version '58.0.3029.110-0ubuntu0.16.04.1281' for 'chromium-browser' was not found

 

Do you have to change apt repositories for that to work?

Share this post


Link to post
Share on other sites

You can download the older deb

 

http://launchpadlibrarian.net/319181475/chromium-browser_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb

 

But it also requires the exact chromium-codecs-ffmpeg-extra package

 

I did somehting along the lines of this...

sudo apt remove chromium-browser

mkdir tempforinstall

cd tempforinstall

wget http://launchpadlibrarian.net/319181475/chromium-browser_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb

wget http://launchpadlibrarian.net/319181477/chromium-codecs-ffmpeg-extra_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb

sudo dpkg -i *.deb

sudo -s

echo chromium-browser hold | dpkg --set-selections

This removes the 59 version, downloads 58 versions, installs them and then locks the browser so it doesn't get upgraded. I'm sure someone could do this in less lines but it worked for me.

 

I don't get the Lock option in synaptic for some reason.

 

Share this post


Link to post
Share on other sites

From the Ubuntu forum...

 

1) Start Chromium on the command line with:

chromium-browser --disable-extensions

2) Type this into the address bar of Chromium:

chrome://flags

3) Press ctrl-F and Search for "media router", then set it to "Disabled".

Source: Ubuntu Bug 1702407 | Comment 19.

Share this post


Link to post
Share on other sites
Quote

This bug was fixed in the package chromium-browser - 59.0.3071.109-0ubuntu0.16.04.1291

---------------
chromium-browser (59.0.3071.109-0ubuntu0.16.04.1291) xenial; urgency=medium

  * debian/patches/fix-argument-evaluation-order.patch: added (LP: #1702407)

 -- Olivier Tilloy <email address hidden> Fri, 07 Jul 2017 10:53:25 +0200

 

Share this post


Link to post
Share on other sites

Friends, I downloaded the latest version of Armbian for Orange Pi Plus 2E desktop version 5.30, did the whole installation procedure without update and everything was working. I did an update and Chromium does not work anymore it tries to open and close. I upgraded to version 5.31 and continue with the same problem. Does anyone know what's going on?

Share this post


Link to post
Share on other sites

Rob Tieger's solution works - i tried it, and now chromium works with no problem.  The next post says the bug was fixed, but i have not tried that yet.  If anyone else knows that is true, let me know.   if this is the latest then the others who had the problem wouldn't have!

On 7/11/2017 at 6:30 AM, zador.blood.stained said:

This bug was fixed in the package chromium-browser - 59.0.3071.109-0ubuntu0.16.04.1291

 

Share this post


Link to post
Share on other sites
On 7/9/2017 at 9:42 AM, Rob Tìgeir said:

You can download the older deb

 

http://launchpadlibrarian.net/319181475/chromium-browser_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb

 

But it also requires the exact chromium-codecs-ffmpeg-extra package

 

I did somehting along the lines of this...


sudo apt remove chromium-browser

mkdir tempforinstall

cd tempforinstall

wget http://launchpadlibrarian.net/319181475/chromium-browser_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb

wget http://launchpadlibrarian.net/319181477/chromium-codecs-ffmpeg-extra_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb

sudo dpkg -i *.deb

sudo -s

echo chromium-browser hold | dpkg --set-selections

This removes the 59 version, downloads 58 versions, installs them and then locks the browser so it doesn't get upgraded. I'm sure someone could do this in less lines but it worked for me.

 

I don't get the Lock option in synaptic for some reason.

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

1 1

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.