Guide: Chromium 51 on Raspbian Jessie

[Dis93]

Thanks, kusti8, that fixed it.

[Dr1Agon]

just recently did an update/upgrade, everything went well, chromium is still working, but when I want to watch something on youtube I get no sound via the RPi-youtube/omxplayerGUI, sound works normally anywhere else, just not there!

any help would be greatly appreciated!

[gkreidl]

just recently did an update/upgrade, everything went well, chromium is still working, but when I want to watch something on youtube I get no sound via the RPi-youtube/omxplayerGUI, sound works normally anywhere else, just not there!

any help would be greatly appreciated!

HDMI or analog audio?

[Dr1Agon]

Oops!

Sorry should have put that in;

Analog

Thanks

[gkreidl]

Oops!

Sorry should have put that in;

Analog

Thanks

Select the "analogaudio" preset (open omxplayerGUI frontend, click on "Settings", then click the preset button).

[gambrogi]

I tried to install Chromium 45, 48 and 51, via wget/dpkg or via ppa/apt-get install and all the installations gives me an chromium-browser that crashes with the only message illegal instruction, and no more messages. Just Illegal Instruction.
I have an RPi2 with Jessie and uname -a retrieves:

Code: Select all

Linux raspberrypi 4.4.20+ #909 Tue Sep 13 16:41:32 BST 2016 armv6l GNU/Linux

I read this thread and tried all the answers that gives a different installation.
Any can help me? Which is the problem? Thanks.

[Dr1Agon]

Thanks!, that's solved it!...

although i'm pretty sure i already tried that before posting without success, must not have...

oh well, working now!

[kusti8]

I tried to install Chromium 45, 48 and 51, via wget/dpkg or via ppa/apt-get install and all the installations gives me an chromium-browser that crashes with the only message illegal instruction, and no more messages. Just Illegal Instruction.
I have an RPi2 with Jessie and uname -a retrieves:

Code: Select all

Linux raspberrypi 4.4.20+ #909 Tue Sep 13 16:41:32 BST 2016 armv6l GNU/Linux

I read this thread and tried all the answers that gives a different installation.
Any can help me? Which is the problem? Thanks.

That is not a Pi2. There is an experimental version linked in the first post you can try.

[Icestar65]

Hi there, I am running into a strange issue with Chromium 51 running on Jessie. I run a dashboard with a tab-cycling plugin and after a few days, the browser will start to crash and cannot be reopened. When I try to reopen Chromium from the terminal, I get a "Segmentation Fault" and it does not open.

When I reboot the system, the browser will be able to start up again for a few hours, but it will ultimately crash again with Segmentation Fault until another restart. What is puzzling is that it runs stable for a few days until the first crash, and then it will crash much faster afterwards.

I've tried --disable-gpu, --no-sandbox, and --disable-pinch all to which does not resolve the issue. Any help would be appreciated. Thanks.

[kusti8]

Hi there, I am running into a strange issue with Chromium 51 running on Jessie. I run a dashboard with a tab-cycling plugin and after a few days, the browser will start to crash and cannot be reopened. When I try to reopen Chromium from the terminal, I get a "Segmentation Fault" and it does not open.

When I reboot the system, the browser will be able to start up again for a few hours, but it will ultimately crash again with Segmentation Fault until another restart. What is puzzling is that it runs stable for a few days until the first crash, and then it will crash much faster afterwards.

I've tried --disable-gpu, --no-sandbox, and --disable-pinch all to which does not resolve the issue. Any help would be appreciated. Thanks.

Is segmentation fault all that is printed? Can you add --enable-logging=stderr -v=1
To get all the logs.

[Icestar65]

Hi there, I am running into a strange issue with Chromium 51 running on Jessie. I run a dashboard with a tab-cycling plugin and after a few days, the browser will start to crash and cannot be reopened. When I try to reopen Chromium from the terminal, I get a "Segmentation Fault" and it does not open.

When I reboot the system, the browser will be able to start up again for a few hours, but it will ultimately crash again with Segmentation Fault until another restart. What is puzzling is that it runs stable for a few days until the first crash, and then it will crash much faster afterwards.

I've tried --disable-gpu, --no-sandbox, and --disable-pinch all to which does not resolve the issue. Any help would be appreciated. Thanks.

Is segmentation fault all that is printed? Can you add --enable-logging=stderr -v=1
To get all the logs.

Thanks for your reply, the error occurred again today and from the terminal I tried the logging command but I still only get Segmentation Fault. Is there any other way to gather the logs?

pi@raspberrypi:/var/log $ chromium-browser --enable-logging=stderr --v=1
Segmentation fault

Thanks!

[kusti8]

That's weird. I would try reinstalling a test image and see if it still works. Chromium does have issues with staying open for a few days just because it uses so much RAM, but it shouldn't cause a segmentation fault.

[Icestar65]

That's weird. I would try reinstalling a test image and see if it still works. Chromium does have issues with staying open for a few days just because it uses so much RAM, but it shouldn't cause a segmentation fault.

Sure thing, Ill try to install one of the Chromium test builds, I'm not too familiar with this, how would I be able to do that? Is it from apt-get? I see versions 51 to 45 in there. Thanks!

[kusti8]

That's weird. I would try reinstalling a test image and see if it still works. Chromium does have issues with staying open for a few days just because it uses so much RAM, but it shouldn't cause a segmentation fault.

Sure thing, Ill try to install one of the Chromium test builds, I'm not too familiar with this, how would I be able to do that? Is it from apt-get? I see versions 51 to 45 in there. Thanks!

No, just do the instructions at the top. The experimental builds will make no difference here.

[jakky567]

Hi, I've been using your browser and I'm having issues signing in with chrome sync (I use it for cloudprint a lot)

[kusti8]

Hi, I've been using your browser and I'm having issues signing in with chrome sync (I use it for cloudprint a lot)

You need to give way more info. What is the error and what are the issues and are you sure your network works right?

[jakky567]

The chrome sync sign in under settings is stating it cannot sign in, and to try again later. I'm not having issues with any other device. I'd rather use chromium because it handles network loss and reboots with grace.

[jakky567]

Unfortunately my network is running perfectly.

[Dis93]

With a version of Chromium being added to the official distro, what will happen to your Chromium project?
I haven't added the 'official' Chromium but I notice on screenshots that the 'official' version has a blue topbar inherited from the new Pixel desktop.

I'm also getting the sync failure triangle icon on my Chromium, despite signing in again.

[kusti8]

With a version of Chromium being added to the official distro, what will happen to your Chromium project?
I haven't added the 'official' Chromium but I notice on screenshots that the 'official' version has a blue topbar inherited from the new Pixel desktop.

I'm also getting the sync failure triangle icon on my Chromium, despite signing in again.

This chromium project I'm going to let die. I'm still working with the RPF to add some fixes to their version of Chromium.

Does the version in the official repos work with sync?

[Dis93]

Understandable, kusti8.
Thank you for your work on this project, it made my Pi experience on the 'net much better.
I'll uninstall your Chromium and try the official one, then see if the sync issue is resolved.

[cjan]

how to install official chromium?

[kusti8]

how to install official chromium?

sudo apt-get update
sudo apt-get install chromium-browser

[cjan]

how to install official chromium?

sudo apt-get update
sudo apt-get install chromium-browser

O..p, found official=51-Beta, why not .7001 OMG.

[jakky567]

Thank you very much for chromium on the pi's. It really is a very solid browser, plus, as a cloudprint solution, is slightly more robust than the headless options.