search

flathub / com.google.Chrome

https://flathub.org/apps/details/com.google.Chrome
54 stars 26 forks source link

v.124.0.6367.60-1 does not launch #290

Open 8bitbuddhist opened 2 months ago

8bitbuddhist commented 2 months ago

I tried launching Chrome this morning after updating to the latest version, but only had a blank, non-rendering window appear. It was like Chrome was in the early stages of showing the browser window, then got stuck. CPU usage was higher than normal (6% on my laptop, which is about one full CPU thread).

I'm running on NixOS Unstable (24.05), Gnome 45.5, Flatpak 1.14.5.

Current workaround is to downgrade to 123.0.6312.122-1.

Logs:

$ flatpak run --branch=stable --arch=x86_64 --command=/app/bin/chrome --file-forwarding com.google.Chrome @@u %U @@                        ─╯
[0419/093810.496175:WARNING:chrome_main_linux.cc(80)] Read channel stable from /app/extra/CHROME_VERSION_EXTRA
[0419/093810.650370:WARNING:chrome_main_linux.cc(80)] Read channel stable from /app/extra/CHROME_VERSION_EXTRA
[2:2:0419/093811.453078:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not part of the idle inhibition specification: https://specifications.freedesktop.org/idle-inhibit-spec/latest/
Created TensorFlow Lite XNNPACK delegate for CPU.

After Ctrl-C:

[2:170:0419/093821.138883:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.                                                     
[2:44:0419/093821.138907:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
[2 preload-host-spawn-strategy] Dropping 0xc48002743c0 (3) because of connection closed
[0419/093821.139037:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
[2:39:0419/093821.139149:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
[2:36:0419/093821.139210:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
ecelia commented 2 months ago

Same here.

$ sudo flatpak update --commit=e133458c4e1b08c5225046826dc9e7139967d92b6f94ad07dac2c7d942892500 com.google.Chrome To rollback

cungureanu commented 2 months ago

I suspect you also have wayland flag enabled.

It seems that --ozone-platform-hint=wayland is borked upstream.

Passing --ozone-platform=wayland works fine.

refi64 commented 2 months ago

https://github.com/flathub/org.chromium.Chromium/issues/385

This is an upstream bug and specifically applies if you set the "Preferred Ozone platform" / ozone-platform-hint option. You should be able to run Chromium with --ozone-platform=wayland to work around it.

8bitbuddhist commented 2 months ago

Edit: Didn't mean to close this out 😅

That works, thanks @refi64 and @cungureanu!

For anyone who's not sure what to do, I edited the Chrome launcher using MenuLibre and added the preferred Ozone platform to the launch command: flatpak run --branch=stable --arch=x86_64 --command=/app/bin/chrome --file-forwarding com.google.Chrome --ozone-platform=wayland @@u %U @@

cungureanu commented 2 months ago

@8bitbuddhist a better solution is to just to drop the flag in ~/.var/app/com.google.Chrome/config/chrome-flags.conf

The .desktop file change will probably be overriden by an update. But not sure.