Blank page on Raspberry4

[matti157]

I followed these steps: 1) Installed raspberry4 from scratch using Raspberry Imager (raspberry os x64 no desktop enviroment) 2) sudo apt update-upgrade 3) Under / I created a folder "browservice" and gave chmod +777 4) Under /browservice I put the image app and gave chmod +777 5) Browservice starts but doesn't load pages, I just see a blank page. I also tried from ie5 on Windows 2000 as well as from my Windows 11 pc.

This is the command line ./browservice950.appimage --start-page=https://www.google.it --vice-opt-http-listen-addr=0.0.0.0:8080

Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.32-v8+ Architecture: arm64

[ttalvitie]

Interesting. Did not happen on my old installation of ARM64 Raspberry Pi OS with desktop environment (even after installing updates). Nor did it happen with a new installation without desktop environment. But then after installing updates, I got the same issue. This means that rendering is broken only when both of these happen at the same time:

• ARM64 Raspberry Pi OS is up-to-date
• No desktop environment is installed

Probably the libc update made some of the bundled graphics libraries behave weirdly, but these libraries are only used if they are not available on the host machine; I need to investigate this further.

I was able to work around the problem by adding the command line option --chromium-args=disable-gpu or --chromium-args=use-gl=disabled; however, these may result in reduced functionality. Please check whether these temporary workarounds work for you.

[ttalvitie]

I also tested this on ARM32; there I had the same issue also before installing updates. The same workarounds worked. I also found out that installing packages libegl1 and libgles2 (along with their dependencies) suffices for fixing the issue; didn't yet test with ARM64 but worth a try there as well. I still don't know what in Raspberry Pi OS updates have broken this.

[matti157]

I also tested this on ARM32; there I had the same issue also before installing updates. The same workarounds worked. I also found out that installing packages libegl1 and libgles2 (along with their dependencies) suffices for fixing the issue; didn't yet test with ARM64 but worth a try there as well. I still don't know what in Raspberry Pi OS updates have broken this.

It works!!! So it's okay to install libegl1 and libgles2 also on ARM64

[ttalvitie]

Ok, good to hear! I further narrowed down the set of required packages to just libx11-xcb1 (a dependency of libegl1). I'll see if bundling it to the AppImage helps.

[ttalvitie]

Bundling libx11-xcb1 in the AppImage indeed helped; thus this issue should no longer occur in v0.9.5.1.