tinker2much
Posts: 8
Joined: Wed Jun 20, 2018 12:38 am

chromium-browser *used* to work on a pi0w, not now

Wed Jun 20, 2018 1:07 am

I have been working off and on for months on a pi0w, formatting various data for Chromium to display in kiosk mode, and until "recently" it worked fine. Now, if I try to start chromium-browser, I get "Trace/breakpoint trap". I had been automatically starting it via an entry in autostart, but now it doesn't work when I try to invoke it from the command line either.

To get more data, I tried chromium-browser on another pi0w, two pi0, a pi2, a pi3, and even an original model b with 256MB memory (mad, I know). It only worked on the pi2 and the pi3. I can't remember when, if ever, I had last tried it on those other machines, but I swear on my copy of K&R that it was working on that particular W for months.

So, two questions:

1. assuming it really worked before, is there something in a recent update that could have broken chromium for a W?

2. assuming it wasn't supposed to work before on anything but a pi2 or pi3, what magic did I inadvertently do to get it going for a while? (I'm not doubting my sanity, but you might..)

Help!

LTolledo
Posts: 736
Joined: Sat Mar 17, 2018 7:29 am

Re: chromium-browser *used* to work on a pi0w, not now

Wed Jun 20, 2018 10:28 pm

Out of curiosity I tried tried running Chrome on my Kodi autoboot RPiZW, accessing via RealVNC.

1. With Kodi running on the background. Clicked on Chrome icon, CPU goes up to 100% for about 3secs but then goes back down again. Chrome did not start.
2. Exited Kodi, Clicked on Chrome icon, CPU goes up again to 100% but after about 3secs goes back down again. Chrome did not start.

Connected the RPiZW to monitor, connected a Keyboard and Trackpad combo
ran step 2 above. same results.

I happen to have an RPi A+ 256 which was last updated and upgraded Dec 27, 2017.
connected via VNC. Clicked Chrome icon.

Chrome browser STARTED! accessing webpage "painfully" slow as ever ;)
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

Lau2wr
Posts: 1
Joined: Mon Mar 07, 2016 6:15 pm

Re: chromium-browser *used* to work on a pi0w, not now

Thu Jun 21, 2018 5:47 pm

No help, but a bit more testing.

I just purchased a Pi0W and it got stuck in a boot loop. It seemed to get to the point where X should have started, then rebooted - endless loop. However, I got it running by cutting back to a reasonably beefy power supply (2A - I've run cheerfully on far less before) and running headless (after I had got the SD card into a state where it all worked on my older Pi0 without W).

No SD cards that worked fine on the Pi0 would work on the Pi0W.

Now I discover that chromium-browser won't run at all - on either Pi0 or Pi0W. It fails with "Trace/breakpoint trap". A --verbose flag doesn't really convey any more information. Epiphany works on the Pi0 and I'll try it on the Pi0W in a bit. I guess it will work.

I can't say I'm happy. I guess my spanking new Pi0W is fine, but I think something very suspect has found its way into the current RPi release. That release is now spamming my logs with "Under-voltage detected!" warnings every 30 seconds on my RPi3 for the last few days. That's a machine that has run totally solidly for years, with the same power supply, SD card and everything.

I built my latest SD using NOOBS - but the other SD card I've been testing with was a straight Debian image.

Rant over, for now.

mikerr
Posts: 2733
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: chromium-browser *used* to work on a pi0w, not now

Thu Jun 21, 2018 7:57 pm

This thread might help:
viewtopic.php?t=157049
Android app - Raspi Card Imager - download and image SD cards - No PC required !

tinker2much
Posts: 8
Joined: Wed Jun 20, 2018 12:38 am

Re: chromium-browser *used* to work on a pi0w, not now

Fri Jun 22, 2018 1:04 am

It's very interesting that chromium-browser worked on LTolledo's A+256, which hadn't been updated for a year and a half. All of my pi's had been updated recently.

My daughter has a number of different pi's, none updated recently; if she can find the time, perhaps she can try chromium-browser on all of hers.

tinker2much
Posts: 8
Joined: Wed Jun 20, 2018 12:38 am

Re: chromium-browser *used* to work on a pi0w, not now

Fri Jun 22, 2018 1:22 am

Following up on various points in the link in mikerr's post about modified/accelerated versions of chromium...

1. I often run headless, sometimes use VNC, and never intentionally do anything intensive graphically that would require lots of GPU-memory, because I want to leave as much memory as possible for the OS and those utilities that I run in a terminal. If I ever remember to change the GPU-memory amounts, it's to cut them down from the default.

2. I have only ever used the standard foundation repositories on my pi's. Whatever chromium I had working before, it was a standard version.

My kiosk application using Chromium doesn't do anything *graphically* intensive, in terms of complicated pages; it displays very simple information and updates it every minute. The refresh is accompanied by a big CPU spike, but it only lasts a few seconds, and then the system is idling until the next minute.

LTolledo
Posts: 736
Joined: Sat Mar 17, 2018 7:29 am

Re: chromium-browser *used* to work on a pi0w, not now

Fri Jun 22, 2018 10:41 am

tinker2much wrote:
Fri Jun 22, 2018 1:04 am
It's very interesting that chromium-browser worked on LTolledo's A+256, which hadn't been updated for a year and a half.
Well actually its just about half a year, unless it already 2019? ;) That RPiA 256 was used as a LED dot-matrix banner controller during the holidays and have shelved it after Jan 2, 2018.

I do keep old backup images of my RPis (most of which were upgraded from Jessie to Stretch) I still have the jessie version prior to upgrade and the stretch version just after upgrade... just in case...

If you have old backups images, well probably half a year old version, of your RPiA then maybe you can burn it again on your microSD card so you can use Chrome again....

or get older Raspbian Stretch image (prior to Dec 2017, if it still exist), or older version NOOBs

....and on the RPiA, stick a note written in bold letters "DONT UPGRADE ME! I BEG YOU" :lol:
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

mikerr
Posts: 2733
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: chromium-browser *used* to work on a pi0w, not now

Fri Jun 22, 2018 9:39 pm

IIRC the changes mentioned in my linked thread above the ( to make chromium work on pi1/zero) were eventually put into the raspbian repos.

- maybe not applied for later versions of chromium....

Install earlier compatible version of chromium:

Code: Select all

 sudo apt-get install chromium-browser=60
Last edited by mikerr on Mon Jun 25, 2018 12:18 pm, edited 1 time in total.
Android app - Raspi Card Imager - download and image SD cards - No PC required !

tinker2much
Posts: 8
Joined: Wed Jun 20, 2018 12:38 am

Re: chromium-browser *used* to work on a pi0w, not now

Sat Jun 23, 2018 1:09 am

I last made changes to my own code on 15 May, and things were working then. The last time I made a full SD card backup was 18 April. I think I'll backup the current card and then restore to that April state (with any later personal program changes manually copied over). As you can see from the frequency of updates below, I like to keep current; I like new features and having the latest security updates, and I don't really want to revert to an older system, but this seems to be what I have to do just to be able to work again.

Here's what I see in /var/cache/apt/archives, listing when chromium-related packages have been installed.

[email protected]:/var/cache/apt/archives $ ls -alt *chro*
-rw-r--r-- 1 root root 9176842 Jun 6 10:15 rpi-chromium-mods_20180605_armhf.deb
-rw-r--r-- 1 root root 9170638 May 16 10:14 rpi-chromium-mods_20180516_armhf.deb
-rw-r--r-- 1 root root 44114046 May 16 09:59 chromium-browser_65.0.3325.181-0+rpt4_armhf.deb
-rw-r--r-- 1 root root 2693002 May 16 09:57 chromium-browser-l10n_65.0.3325.181-0+rpt4_all.deb
-rw-r--r-- 1 root root 1644282 May 16 09:57 chromium-codecs-ffmpeg-extra_65.0.3325.181-0+rpt4_armhf.deb
-rw-r--r-- 1 root root 9170940 May 10 07:00 rpi-chromium-mods_20180509_armhf.deb
-rw-r--r-- 1 root root 9170794 Apr 10 08:22 rpi-chromium-mods_20180409_armhf.deb
-rw-r--r-- 1 root root 9166738 Mar 14 01:37 rpi-chromium-mods_20180302_armhf.deb
-rw-r--r-- 1 root root 9200912 Feb 7 06:26 rpi-chromium-mods_20180207_armhf.deb
-rw-r--r-- 1 root root 9200544 Jan 25 05:03 rpi-chromium-mods_20180112_armhf.deb
-rw-r--r-- 1 root root 58358674 Dec 1 2017 chromium-browser_60.0.3112.89-0ubuntu0.14.04.1.1010+1_armhf.deb
-rw-r--r-- 1 root root 9199366 Nov 15 2017 rpi-chromium-mods_20171113_armhf.deb
-rw-r--r-- 1 root root 9198004 Oct 26 2017 rpi-chromium-mods_20171026_armhf.deb
-rw-r--r-- 1 root root 9195728 Oct 18 2017 rpi-chromium-mods_20171017_armhf.deb
-rw-r--r-- 1 root root 9197398 Sep 13 2017 rpi-chromium-mods_20170913_armhf.deb
-rw-r--r-- 1 root root 58358584 Aug 23 2017 chromium-browser_60.0.3112.89-0ubuntu0.14.04.1.1010_armhf.deb
-rw-r--r-- 1 root root 58428288 Aug 16 2017 chromium-browser_60.0.3112.89-0ubuntu0.14.04.1.1005_armhf.deb
-rw-r--r-- 1 root root 9193766 Aug 9 2017 rpi-chromium-mods_20170809_armhf.deb
-rw-r--r-- 1 root root 9191844 Jul 14 2017 rpi-chromium-mods_20170714_armhf.deb
-rw-r--r-- 1 root root 9193276 Jun 20 2017 rpi-chromium-mods_20170619_armhf.deb
-rw-r--r-- 1 root root 9191836 Jun 14 2017 rpi-chromium-mods_20170614_armhf.deb
-rw-r--r-- 1 root root 9189144 Apr 18 2017 rpi-chromium-mods_20170418_armhf.deb
-rw-r--r-- 1 root root 9184614 Mar 20 2017 rpi-chromium-mods_20170317_armhf.deb

This points to the chromium-browser_65 from May 16 as the one that is broken on the zero, zero W and other lesser pi models. Can anyone with more chromium or raspbian knowledge explain why this might be?

tinker2much
Posts: 8
Joined: Wed Jun 20, 2018 12:38 am

Re: chromium-browser *used* to work on a pi0w, not now

Sat Jun 23, 2018 1:12 am

To LTolledo: 2017 seems so far away to me ;-)

LTolledo
Posts: 736
Joined: Sat Mar 17, 2018 7:29 am

Re: chromium-browser *used* to work on a pi0w, not now

Sat Jun 23, 2018 11:43 am

just checked my other RPiA (#2) a 512MB version and clicked the Chromium icon. It started and I was able to get the version number

Version 60.0.3112.89 (Developer Build) Built on Ubuntu 14.04, running on Raspbian 9.4 (32-bit)

so I checked my other RPi's Chromium version by clicking About Chromium when the browser started

this is the Chromium version on the RPiA 256MB last updated Dec 2017
Version 51.0.2704.91 Built on Ubuntu 14.04, running on Raspbian 8.0
works fine

this is the version on my RPiZ (no WiFi model but with USB WiFi dongle, dont remember when this year it was updated)
Version 60.0.3112.89 (Developer Build) Built on Ubuntu 14.04, running on Raspbian 9.1 (32-bit)
-- works fine

below is the latest version running on my RPi3B+
Version 65.0.3325.181 (Official Build) Built on Raspbian , running on Raspbian 9.4 (32-bit)
-- works as expected

on my latest updated and upgraded RPiZW the browser would not start by clicking the Chromium icon so I checked via command line
$ chromium-browser --version
Chromium 65.0.3325.181 Built on Raspbian , running on Raspbian 9.4

when running the browser via command line: returns error
$ chromium-browser
--disable-quic --enable-tcp-fast-open --disable-gpu-compositing --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
Trace/breakpoint trap

my conclusion: Chromium will run on RPiZW (Broadcom BCM2835) if version is 60.0.3112.89 or below.
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

tinker2much
Posts: 8
Joined: Wed Jun 20, 2018 12:38 am

Re: chromium-browser *used* to work on a pi0w, not now

Sat Jun 23, 2018 8:08 pm

Does this seem like a problem that someone at the foundation ought to be made aware of? Simon Long maybe? But how would we do so? Or does someone watch the forum regularly enough that they'll naturally notice this thread on their own...

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5371
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: chromium-browser *used* to work on a pi0w, not now

Mon Jun 25, 2018 9:26 am

I've mentioned it and I think the answer is that chromium is not supported on the zero. You may have better luck with epiphany or firefox.

fruitoftheloom
Posts: 17838
Joined: Tue Mar 25, 2014 12:40 pm

Re: chromium-browser *used* to work on a pi0w, not now

Mon Jun 25, 2018 10:25 am

ShiftPlusOne wrote:
Mon Jun 25, 2018 9:26 am
I've mentioned it and I think the answer is that chromium is not supported on the zero. You may have better luck with epiphany or firefox.

firefox-esr browser is in the Raspbian Stretch repositories ;)
Adieu

mikerr
Posts: 2733
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: chromium-browser *used* to work on a pi0w, not now

Mon Jun 25, 2018 11:14 am

With a fresh install of the latest stretch image ( 28-04-18 ) chromium v60 works fine on all Pi (inc zero)

Code: Select all

apt-cache policy chromium-browser

Installed: 60.0.3112.89-0ubuntu0.14.04.1.1010+1
An apt-get upgrade will not actually upgrade chromium:

Code: Select all

sudo apt-get upgrade

The following packages have been kept back:
  chromium-browser rpi-chromium-mods
 

unless you do an apt-get dist-upgrade, or apt-get install chromium-browser that's when you end up with chromium v65 (fine on a pi3)
but which doesn't work on the zero

[edit] I suspect its actually rpi-chromium-mods which has the problem

I tried apt-get install chromium-browser from a fresh stretch install which brings in chromium v65 with no problems on Pi Zero.
Android app - Raspi Card Imager - download and image SD cards - No PC required !

tinker2much
Posts: 8
Joined: Wed Jun 20, 2018 12:38 am

Re: chromium-browser *used* to work on a pi0w, not now

Mon Jun 25, 2018 4:13 pm

I had gotten in the habit of doing "sudo apt-get dist-upgrade", so that explains how I got v65. (thinking that doing so would get me the very latest of everything, and thinking that would actually be a good thing.) It's good to know that I could start fresh, do "sudo apt-get upgrade" and stick with an earlier version of Chromium, at least for a while, but eventually Debian or the Foundation would release a shiny new version which would require a dist-upgrade?

I have another problem at the moment. I first made another backup of the card as it stood using dd and gzip as usual, then I tried to restore to that card from my April whole-card backup. The process started slow and got slower; I let it run overnight and got no farther than 5GB out of 16GB. I just restarted it and it's already unusably slow:

0+440 records in
0+439 records out
28770304 bytes transferred in 81.370223 secs (353573 bytes/sec)
0+472 records in
0+471 records out
30867456 bytes transferred in 138.592460 secs (222721 bytes/sec)
0+526 records in
0+525 records out
34406400 bytes transferred in 234.017186 secs (147025 bytes/sec)
0+844 records in
0+843 records out
55246848 bytes transferred in 795.956292 secs (69409 bytes/sec)

If I did the math correctly, that's over two and a half days at the latest rate. But, wait, it seems to be speeding up:

0+3313 records in
0+3312 records out
217055232 bytes transferred in 963.969224 secs (225168 bytes/sec)
0+4393 records in
0+4392 records out
287834112 bytes transferred in 987.879851 secs (291366 bytes/sec)
0+7536 records in
0+7535 records out
493813760 bytes transferred in 1052.179612 secs (469325 bytes/sec)

That would only be 9 or 10 hours. I guess we'll have to wait and see.

If restoring from backup doesn't work, I'll start out with a fresh install of the latest stretch, and should be happy with that. If I decide I need a later version of Chromium, I'll carefully follow in mikerr's steps.

But along the same theme of not being sure things will work until you try them, I THINK I wrote down all of the system tweaks and config changes I did to support my code working on that pi, but so far I've never tried getting the whole application working on a new card. Well, there's another learning experience...

ejolson
Posts: 2159
Joined: Tue Mar 18, 2014 11:47 am

Re: chromium-browser *used* to work on a pi0w, not now

Mon Jun 25, 2018 5:59 pm

ShiftPlusOne wrote:
Mon Jun 25, 2018 9:26 am
I've mentioned it and I think the answer is that chromium is not supported on the zero. You may have better luck with epiphany or firefox.
Is there a list of regressions in newer versions of Raspbian somewhere, particularly with respect to running on Pi Zero and Pi Zero W hardware?

I'm still stuck on an old kernel because of an MTU configuration bug that prevents the use of jumbo packets with the Zero and the USB Ethernet gadget.

hippy
Posts: 4020
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: chromium-browser *used* to work on a pi0w, not now

Mon Jun 25, 2018 8:47 pm

ShiftPlusOne wrote:
Mon Jun 25, 2018 9:26 am
I've mentioned it and I think the answer is that chromium is not supported on the zero.
Is it just 'not the Zero' or everything BCM2835 based ?

I always wondered when we'd hit the 'Wintel problem' of perfectly good hardware being effectively obsoleted because the software one wants to use refuses to run on older hardware :(

That's always annoyed me because high level languages were meant to make it possible to compile everything to run on anything the compiler supported, albeit maybe slower, and not having enough memory to run a moderately acceptable show-stopper.

It seems to me to take a special kind of nastiness to deliberately code something so it won't work with a particular CPU architecture or OS when it otherwise could.

hippy
Posts: 4020
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: chromium-browser *used* to work on a pi0w, not now

Mon Jun 25, 2018 8:59 pm

mikerr wrote:
Mon Jun 25, 2018 11:14 am
With a fresh install of the latest stretch image ( 28-04-18 ) chromium v60 works fine on all Pi (inc zero)
Though finding Chromecasts to cast to is broken in version 60 if one wants that, which creates a bit of a Catch 22 as the fix is in 65 (maybe 61-64). Seems 51 is the version previous to use, but then one loses anything which came later.

viewtopic.php?t=177268

nes_pi
Posts: 20
Joined: Mon Jun 25, 2018 1:35 am

Re: chromium-browser *used* to work on a pi0w, not now

Tue Jun 26, 2018 7:57 am

Vivaldi blows away chromium for me on latest raspbian, some pages that would hang and crash the browser in chromium are loading with decent speed for how loaded they are in Vivaldi.

fruitoftheloom
Posts: 17838
Joined: Tue Mar 25, 2014 12:40 pm

Re: chromium-browser *used* to work on a pi0w, not now

Tue Jun 26, 2018 8:52 am

nes_pi wrote:
Tue Jun 26, 2018 7:57 am
Vivaldi blows away chromium for me on latest raspbian, some pages that would hang and crash the browser in chromium are loading with decent speed for how loaded they are in Vivaldi.

LMFTFY

https://vivaldi.com/blog/vivaldi-for-raspberry-pi/
Adieu

mikerr
Posts: 2733
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: chromium-browser *used* to work on a pi0w, not now

Tue Jun 26, 2018 10:25 am

I've found the culprit really is rpi-chromium-mods, not chromium itself.

The fix to get a working chromium v65 back is:

Downgrade rpi-chromium-mods package to the last compatible version, and then put a hold on it to stop it upgrading again:

Code: Select all

sudo apt-get install rpi-chromium-mods=20180302
sudo apt-mark hold rpi-chromium-mods
Android app - Raspi Card Imager - download and image SD cards - No PC required !

DirkS
Posts: 9478
Joined: Tue Jun 19, 2012 9:46 pm
Location: Essex, UK

Re: chromium-browser *used* to work on a pi0w, not now

Tue Jun 26, 2018 10:38 am

mikerr wrote:
Tue Jun 26, 2018 10:25 am
Downgrade rpi-chromium-mods package to the last compatible version, and then put a hold on it to stop it upgrading again:

Code: Select all

sudo apt-get install rpi-chromium-mods=20180302
sudo apt-mark hold rpi-chromium-mods
Strange... AFAICT the 20180302 version is actually the latest one. See http://archive.raspberrypi.org/debian/p ... mium-mods/

mikerr
Posts: 2733
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: chromium-browser *used* to work on a pi0w, not now

Tue Jun 26, 2018 10:57 am

No, latest problematic one is 20180605:

Code: Select all

 sudo apt-cache policy rpi-chromium-mods
rpi-chromium-mods:
  Installed: 20180605
  Candidate: 20180605
  Version table:
 *** 20180605 500
        500 http://archive.raspberrypi.org/debian stretch/ui armhf Packages
        100 /var/lib/dpkg/status
     20180302 500
        500 http://archive.raspberrypi.org/debian stretch/main armhf Packages
Android app - Raspi Card Imager - download and image SD cards - No PC required !

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5371
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: chromium-browser *used* to work on a pi0w, not now

Tue Jun 26, 2018 11:05 am

Interesting. I wonder if flash is the problem.

Return to “Raspbian”