DietPi-Software | Chromium: Fails to start on ARMv8 #5300
Comments
MichaIng
changed the title
|
Many thanks for your report. It seems to be a general bug in Chromium affecting many or all ARMv8 systems: |
|
Please let me know if there is anything you want me to test on an Odroid C4. |
MichaIng
added
Workaround available 🆗
|
I found a workaround: apt install chromium/bullseye chromium-common/bullseyeThis will downgrade Chromium from v98 (from Debian security repo) to v90 (from regular Debian repo). That one starts up without issues. Any next "apt upgrade" incl. "dietpi-update" will upgrade it again. To lock it: apt-mark hold chromium chromium-common
rm -Rf /{root,home/*}/.{cache,config}/chromiumI'll report this to the Debian bug tracker. |
|
This works for you as well guys? I'm not sure what to do about it. I reported it to Debian: https://bugs.debian.org/1006457 I think I'll wait with the decision until the final release, probably we get some helpful response on the Debian bug report until then. |
I'm away for a few weeks working on a client's site, as soon as I get back I'll fire up a machine and let you know.
I agree completely |
|
in my case, the chromium is opened, but not load the --homepage, but, if i press ctrl t (new tab) then load the page: test:
OUTPUT: |
|
@orlandozeta |
|
what could be the problem then? with Chromium 95.0.4638.78 Built on Debian , running on Debian 11 It works well, 32 rpi running ok, 2 with updated chromium to 98, not |
|
I have no idea, which is why I reported it to Debian. |
|
Hello everyone I've just updated an Odroid C4 to DietPi 8.2.2 and the full screen Chromium kiosk in Xinit is working again. Thanks to everyone that did all the hard work in the background. FYI I did play around with Firefox in the same situation, but it never quite did what Chromium did so easily. |
|
Strange, since there was not change regarding this, no Chromium package upgrade since this issue appeared the first time. I'll test on Odroid N2 as well, probably others here can test as well. If it is really resolved, then it was probably something with the X server or a dependency of Chromium which fixed it. I'll carefully watch all APT package upgrades on Odroid N2 as well 😄. |
Curious, the machine in question here updated from DietPi 7 to 8.2.2 and I'm sure I saw a Chromium package update at some point. But I can confirm that I did nothing else, other than update to 8.2.2 Good luck with the N2. Do you have a C4 machine? Would you like one? |
Okay, DietPi v7 is old, so of course there were many Chromium package updates since then. I hope before reporting here you tried first to upgrade to the latest Chromium package 😉. I tested it with the (still) latest package on Odroid N2 and faced the same issue there, two weeks ago. |
Yeah, fear not. I reported it after I had updated the machine to 8.1 (I think, whatever it was a few weeks ago) Today's machine was a "working / known to be good" image, that I just ran the |
|
I'm not sure what to do with the following information. Your guidance would be most welcome. A brand new eMMC with nothing but a fresh DietPI image on a C4, trying to get Chromium working, just fails with the same stack smashing issue. However. I have got Vivaldi working full screen, it just complains that it doesn't have HTML5 H.264 support loaded. I downloaded Debian Vivaldi from here and installed with it this then I edited the Chromium autostart file (because I wanted a template to work from) so that it looks like this I get Vivaldi at full screen (after editing dietpi.txt and setting the X and Y res correctly Anything you can do to help clean this up (if it needs it) or resolve the H.264 playback would be amazing. 😄 I'm just glad that I've got some kind of full screen browser again, I'll try it with the rest of my setup tomorrow. Thanks to everyone in advance. Does this help you in any way? Using Peter's reference to command line switches, I'll play around tomorrow and see if I can get a pure kiosk working |
|
Good morning Well this didn't take long at all. I just dropped Vivaldi onto my development machine Swapped any reference to Chromium to Vivaldi and it works for everything other than the video playback. Only Vivaldi forum post I could find with a comment from someone at the company - https://gist.github.com/ruario/bec42d156d30affef655 The command line that is being used to start Vivaldi is this
Note the Which isn't an issue in the closed environment that I'm working in, but I guess it is a big issue for those that pull content from the web. I would be delighted to hear about other people's results. One small detail that does confuse me.... I think Vivaldi is based on Chromium..... so why is this working? |
|
@MDAR does it have I may try this later sometime, coz I've made a rpi4 as kiosk. |
@kt1024 By the looks of it, that package isn't available However, the good people at Vivaldi suggest that the application should "download what it needs" on first boot. I'm waiting for a reply on their forum (as per link above) If you don't need video playback, Vivaldi certainly doing everything else I need it to, in full unattended kiosk mode, with WebSocket remote control. |
|
my bad, should be 2 packages, |
|
These are RPi-only packages from the RPi repository, responsible only for video decoding, not for startup, and on RPi the issue does not exist. |
|
@ruario https://gist.github.com/ruario/bec42d156d30affef655#gistcomment-4251813
It certainly enables h.264 playback, with user interaction, so for me that is >70% the way to a solution. I need to send F11 to the browser twice (even if it is full screen / kiosk) before the videos will autoplay. After that, everything works perfectly, I can use WebSockets to set the video file and start and stop playback. |
|
Hi I think there has been a breakthough I'm having an issue with a machine that is forcing me to update it to the very latest version of Debian. I didn't want to do this due to the Chromium issue. Can anyone else try this and let me know if the Chromium issue has been resolved, before I update this one ,machine? Thanks |
At least from DietPi side, we don't force anyone to update. We just notify user about available updates.
You could create a dietpi-backup and check if latest version of Chromium is working. If not, simply perform a restore. If you use SD card, you could create an offline close as well. |
You are absolutely correct, this is a third party app that is giving me trouble. But in fairness, that machine is still running DietPi V7
Yes, that is an option. My post was more to ask if someone independent of me and any mistakes I might have made, could confirm that Chromium V89.0.4389.114.1~deb10u1 was working for them. |
|
On Buster there was never any issue with Chromium. This issue is about non-RPi ARMv8 Bullseye systems only 😉. And based on the Chromium version, this system seems to be still a Buster system. |
DAM IT I'd forgotten about that detail. I must have picked up my only Buster based box..... I wonder how that missed the "great upgrade" |
|
Hehe, I'm not aware of any info/notification a system would get about this upgrade, but our MOTD 😉. |
MichaIng
added
Solution available 🥂
|
Finally the issue got solved with latest Kodi package on Bullseye: https://bugs.debian.org/1006457 |
|
What an absolute fabulous fella you are. Thank you so much for all your effort. When I get back to my office, I'll update my production machine and let you know how it goes. (I'm sure it'll be fine) 🎉🎊 |
|
Hello I can confirm that everything now works really well with a fresh install of DietPi V8.12.1 on Odroid C4 machines |
Creating a bug report/issue
Required Information
Additional Information (if applicable)
Steps to reproduce
Extra details
The text was updated successfully, but these errors were encountered: