Nope, Debian Testing on machine with 12 cores and 32GB of RAM and 3GB/s M.2 drive.
And my systemd-analyze says graphical.target reached after 5.690s in userspace. Most of which is network manager waiting for online status, mounting filesystems, and timesyncd waiting clock update.
Sounds like you have a borked dbus or is using the GTK_USE_PORTAL env variable, 20 second timeouts are gtks standard way of dealing with something it doesn’t like. Firefox should take < 1 second to start fresh and takes < 3s for me, restoring hundreds of tabs
Nope, Debian Testing on machine with 12 cores and 32GB of RAM and 3GB/s M.2 drive.
And my
systemd-analyzesaysgraphical.target reached after 5.690s in userspace.Most of which is network manager waiting for online status, mounting filesystems, andtimesyncdwaiting clock update.Sounds like you have a borked dbus or is using the GTK_USE_PORTAL env variable, 20 second timeouts are gtks standard way of dealing with something it doesn’t like. Firefox should take < 1 second to start fresh and takes < 3s for me, restoring hundreds of tabs
Hm, interesting idea. Any suggestion how I can check/reset this?