chromium-browser $website Always Fails
#28
Comments
|
I'm unable to reproduce the issue with any of the commands provided. Is there anything unusual about your setup? Is it an official Raspberry Pi OS image (non-lite)? Any details that would help reproduce the issue would be good. |
|
Hey hey, I'm using Raspberry Pi OS with desktop here: https://www.raspberrypi.com/software/operating-systems/ Specifically, 2022-01-28-raspios-bullseye-armhf. I retried it now with Raspiberry Pi 3b+ and a Raspiberry Pi W 0, and both experience the same issue. I've made a video of the issue: https://www.youtube.com/watch?v=0FpPnX6prZ0 It takes about 45-60 seconds for wikipedia to load. But then, |
|
Hey there, Running into the same issue after installing a new version of Raspbian using Raspberry Pi Imager. Using firefox for now but I'd like to help get this fixed. Hardware: Raspberry Pi 3 Model B Rev 1.2 Below is the stderr log without the --verbose flag.
My steps to reproduce are
I have verbose logs I'll attach here too. Same steps as above. Going to keep banging on it in the meantime. Can get more info if need be. |
|
The symptoms look similar to the issue we face: MichaIng/DietPi#5342 Solution is to enable KMS, but on Raspberry Pi OS Bullseye this should be enabled by default. @jordanreedy16 can you verify that you use KMS and not the legacy framebuffer driver, and that as well X11 uses the modesetting driver and not fbdev or fbturbo? |
|
Hey @MichaIng , the advice you suggested in the other thread worked like a charm! Specifically, I didn't check to see which drivers were in use prior to the change, but I did do a raspi-config, chose the Full KMS driver and rebooted. That initially did not fix the issue. Further testing indicates that changing the settings in raspi-config makes no difference. It works regardless at this point. Thanks again for the assist! |
AFAIK there is not really much downside (but upsides!) on any RPi model when using KMS, it is the default on RPi OS anyway, but I still wonder whether it is intended or expected that Chromium does not work with framebuffer driver anymore, or whether framebuffer driver support can be re-enabled somehow. |
|
Maybe I've missed some detail, but I'm still having trouble reproducing this on any official image with kms disabled. |
If you have a raspi v3B+, flash it's microsd with either 32bit or 64bit 2022-1-28 Desktop Raspi Official OS, simply run apt update;apt upgrade (don't do anything else), then try a REMOTE SSH login and type these commands: You should get output in the terminal similar to this: On the attached display, output should be similar to this (just hangs, NEVER loads google.com):
|
@MichaIng that fix works great, thank you! :) For anyone else reading this thread, as a regular user in the terminal (or bash script), just add sudo after the pipe: |
|
I can confirm @MichaIng 's fix, as well. seems to be sufficient. |
Actually it looks like EGL is tried to be used already at first, but failing due to missing On my latest test on RPi 2, even without explicitly defining |
|
@MichaIng On my raspi v3b+ it looks like having libgles2 installed (already, manually) makes no difference. If I REMOVE the logic you suggested adding to /etc/chromium.d/egl, it STILL hangs chromium even with libgles2 ALREADY installed (probably flagged as a manual install here from my automated bash script installing a crypto ticker, multiple browsers, and vulcan / mesa / related libraries): |
|
That said, MAYBE |
Definitely not. This is just a random filename (chosen to match the purpose), you can choose any other or add the flag to any other file within this directory. And no library is manipulating any other software's configuration files. But still confusing. On DietPi we add the following flags: --no-sandbox --test-type --disable-smooth-scrolling --disable-low-res-tiling --enable-low-end-device-mode --num-raster-threads=$(nproc) --disable-composited-antialiasingNo idea whether these somehow trigger EGL. However, while we do not fully understand these little differences, it doesn't matter much. With KMS enabled, using EGL with GLES makes sense, respectively is required, so good to add the flag explicitly. The more important question is whether it is intended and unavoidable to use KMS from Chromium now. Generally it makes sense and should provide better performance, but there are still some applications relying on features available via legacy framebuffer driver only, or other reasons why user might still want to use it, while keep using Chromium. |
Good to know. I'm using jquery transitions / animations, which seem to work MUCH better with hardware accelerated browsers. |
|
Is this still an issue? |
|
@XECDesign We're replacing a pi that uses this fix with one using Bookworm in the near future. I'll let you know if the fix is still necessary or not for our use case when we do. |
|
@XECDesign The problem still occurs on a Pi 3B using RaspberryPi OS Bookworm and |
|
Ah, that's a shame. Thanks for checking. I have just never seen the issue myself and have no idea how to reproduce it. You're just taking the latest 64-bit desktop Raspberry Pi OS image, running chromium through the cli and it's not working? |
|
I'm using the Raspberry Pi 64-bit OS image that Imager provides, did an /usr/bin/chromium-browser --app=<private url> --start-fullscreen --force-device-scale-factor=1.00The page loads, then fetches data, which refreshes the view. The initial load seems to work, but when the data gets fetched instead of the view updating, it goes white. I'll see about getting a repro with static files. |
|
@XECDesign https://towa-japan.github.io/RPi-Chromium-28/ exhibits the issue I'm having (on a raspberry Pi 3B). Using /usr/bin/chromium-browserI get a blank page, and the following error output: Using /usr/bin/chromium-browser --use-gl=eglI get the expected page, and the following error output: |
|
I'm seeing the reported behaviour under X11 and Wayfire, but it seems to work as expected under labwc. We'll be switching to labwc by default soon, so it may be worth checking if it solves your problem too. In raspi-config, you can go to advanced -> wayland and switch to labwc. |
|
Is that true for a 3B? I know the plan is to support older hardware on wayland, but last I checked, it'll only run on a pi4 or newer. |
|
It is definitely true for the 3B and I believe across the board for all devices. |
|
I'll try it out and get back to you, then. |
|
I was able to display the private url without adding any extra flags to the chromium-browser commandline. I do, however, run into the issue of a grayscreen when using vnc, so I'll wait a bit before making this change in production use. |
|
Closing since I believe this and the vnc issues are both resolved. |
|
Sorry, yes the vnc issue is resolved as discussed at the linked issue |
Hi,
Loading a website with
chromium-browser wikipedia.orgin the CLI, for instance, will never ever actually load the page, and it will be forever stuck in a network loop. This is also the case withchromium-browser --app=https://wikipedia.organdchromium-browser --kiosk wikipedia.org. Running it withinlxterminal, similarly, just fails.On the other hand,
firefox wikipedia.orgloads instantly, fast, and quite conveniently.I'm using the newest distro images.
The text was updated successfully, but these errors were encountered: