Chromium starts very slowly (30 seconds)

papabryce · 2023-12-08 02:38:39

I removed TLP and powertop. It seems like now I see the issue regardless of whether I am plugged in. Maybe a step in the right direction?

seth · 2023-12-08 08:04:24

https://wiki.archlinux.org/title/CPU_frequency_scaling
You could try to force the system into AC mode, but obviously this will shorten your battery-time.
https://wiki.archlinux.org/title/TLP#Fo … figuration (just use AC instead of BAT)

patriarch001 · 2024-05-12 00:24:20

I'm facing the same issue as well regardless of whether my laptop is charging or not. I'm using hyprland too.

seth · 2024-05-12 06:41:07

Is you CPU underclocked?
Do you have dbus/portal related errors in your system journal?
Is your dbus environment properly set?

See the head of this thread for some investigational steps - #meetoo generically slow is pointless here.

patriarch001 · 2024-05-15 16:04:19

seth wrote:

Is you CPU underclocked?
Do you have dbus/portal related errors in your system journal?
Is your dbus environment properly set?
See the head of this thread for some investigational steps - #meetoo generically slow is pointless here.

Will sure do! But meanwhile, here is some more specific details of the problem caused:

I've found out Chromium based browsers only launch late when the flag

"Preferred Ozone platform
Selects the preferred platform backend used on Linux. The default one is "X11". "Auto" selects Wayland if possible, X11 otherwise. – Linux"

is set to "Wayland".

Also, I'm using hyprland on Laptop.

seth · 2024-05-15 16:06:31

https://wiki.archlinux.org/title/Chromi … er_Wayland

chromium --ozone-platform=wayland

?

rarchrinux · 2024-06-10 23:14:21

Just wanted to chime in that I have had the exact same problem with chromium and electron apps for several months. Running Arch, Hyprland, and powertop. I have xdg-desktop-portal-hyprland and xdg-desktop-portal-gtk installed (no gnome, kde, etc). Setting —ozone-platform=wayland does not remove the delay, but it does affect whether the window appears immediately or after 30 seconds.

seth · 2024-06-11 07:12:41

seth wrote:

Is you CPU underclocked?
Do you have dbus/portal related errors in your system journal?
Is your dbus environment properly set?
See the head of this thread for some investigational steps - #meetoo generically slow is pointless here.

That includes testing a fresh profile and lowerign the dbus timeout - stracing a massive beast like chromium to figure what it's waiting for is gonna be a complete PITA

Arch Linux

#26 2023-12-08 02:38:39

Re: Chromium starts very slowly (30 seconds)

#27 2023-12-08 08:04:24

Re: Chromium starts very slowly (30 seconds)

#28 2024-05-12 00:24:20

Re: Chromium starts very slowly (30 seconds)

#29 2024-05-12 06:41:07

Re: Chromium starts very slowly (30 seconds)

#30 2024-05-15 16:04:19

Re: Chromium starts very slowly (30 seconds)

#31 2024-05-15 16:06:31

Re: Chromium starts very slowly (30 seconds)

#32 2024-06-10 23:14:21

Re: Chromium starts very slowly (30 seconds)

#33 2024-06-11 07:12:41

Re: Chromium starts very slowly (30 seconds)

Board footer