You are not logged in.

#1 2026-03-04 02:48:32

vbezhenar
Member
Registered: 2024-11-03
Posts: 6

Launching Chromium in GNOME displays progress indicator for seconds

I'm using GNOME with Wayland. I've installed Chromium from arch repository. When I click icon from the launcher, the application starts instantly, however if I move cursor to the GNOME top panel, it'll display progress indicator for like 10 seconds. This is confusing and does not happen with other GNOME apps.

I think that it started when Chromium switched to use wayland by default, few months ago. Before it used X11 and it worked differently.

Similar application to Chromium is OSS VS Code (package code). It's an electron application and also started to use wayland recently. But it doesn't have that problem. One difference in their desktop files is that Chromium uses StartupNotify=true, while VS Code uses StartupNotify=false. However GNOME Text Editor also uses StartupNotify=true yet works correctly.

I tried to understand the underlying issue but it seems to complicated for me. I thought about reporting bug to arch chromium repo, but it seems that registration is closed.

Maybe someone will make more sense out of this situation. Would be nice to eventually fix that bug somewhere.

Last edited by vbezhenar (2026-03-04 02:51:34)

Offline

#2 2026-03-04 08:25:36

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,450

Re: Launching Chromium in GNOME displays progress indicator for seconds

When I click icon from the launcher, the application starts instantly, however if I move cursor to the GNOME top panel, it'll display progress indicator for like 10 seconds

Ie. the launch/startup feedback (bouncing cursor) doesn't pick up the launch success.

I think that it started when Chromium switched to use wayland by default, few months ago.

Are we sure about that?
https://wiki.archlinux.org/title/Waylan … plications

What if you enforce wayland and gtk4?
https://wiki.archlinux.org/title/Chromi … nd_support
(You can put those into ~/.config/chromium-flags.conf)

Problem is likely around some transactional surface and window activation.

Offline

Board footer

Powered by FluxBB