When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome beta version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-beta" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

The latest version introduced a duplicate .desktop entry (google-chrome-beta.desktop and com.google.Chrome.beta.desktop) with the latter including the following block at the end:

# This is the same as google-chrome-beta.desktop except NoDisplay=true prevents
# duplicate menu entries. This is required to match the application ID
# used by XDG desktop portal, which has stricter naming requirements.
# The old desktop file is kept to preserve default browser settings.
NoDisplay=true

However, this block is placed in the wrong section, resulting in the .desktop file still being shown as duplicate. This can be verified with desktop-file-validate:

$ desktop-file-validate /usr/share/applications/com.google.Chrome.beta.desktop
/usr/share/applications/com.google.Chrome.beta.desktop: error: file contains key "NoDisplay" in group "Desktop Action new-private-window", but keys extending the format should start with "X-"

Being placed at the end of the file, it's inside the section called [Desktop Action new-private-window]. Putting it at the beginning (e.g. before all the GenericName keys) makes it work as expected and solves the issue.

@UncleRuckus I had a similar issue. I went to chrome://settings/fonts and manually set my fonts. This seems to have fixed it for now. Below is an error that gave me an idea on for what to try.

[41988:1:0825/115210.255237:ERROR:third_party/blink/renderer/core/css/remote_font_face_source.cc:357] NOTREACHED hit. 

140.0.7339.24-1 seems fine on a fresh install but for some reason updating my existing install on my laptop is having the same problem as the last version and I cant seem to find a reason why.

@UncleRuckus I'm seeing the same problems of empty text boxes and cut off texts.

beta 140.0.7339.16-1 seems broken, getting lots of graphical glitches and text not being displayed propertly. beta 140.0.7339.5-1 was fine.

The latest release (135.0.7049) is giving me some weird graphic issue. The window is not rendered properly: the custom GTK theme is being applied, but not in the Close/Minimize/Maximize buttons, selection overlay is not blue but grey and it doesn't show the text under it, and there's a few pixel empty line between the tabs/URL/Bookmarks section and the website one (had similar issue in the past with Electron and Ozone, might be related).

The screenshots in this link (first is previous version for comparison) may help visualizing the problems (the only one missing is the latest one, because it's not "capturable" through a screenshot, aka when captured it's just black, while live it's transparent and glitchy and it shows the window behind).

Also, AltGr is not recognized (I'm using it-IT layout, and I cannot input square/curly brackets, at, hash, etc).

Chrome without disabling hwdec would generate an immediate core dump. Disabling hddec (vulkan backend) would let chrome function correctly.

GPU: 
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon HD 7800 Series (radeonsi, pitcairn, ACO, DRM 3.57, 6.9.7-x64v2-xanmod1-MANJARO) (0x6818)
    Version: 24.3.0
    Accelerated: yes
    Video memory: 2048MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

Chrome 125 works for me too. But all 5 releases of Chrome 124 just didn't.

For me google-chrome-beta (125.0.6422.4) shows up normally and as wayland surface (without any switch/config needed), maybe next release will fix this white screen issue ...

Newer version doesn't solve the issue. I'm still facing it.