GNOME Bugzilla – Bug 692762
Shell startup is slow (hits a timeout) when network is unavailable
Last modified: 2021-07-05 14:11:12 UTC
It seems like GNOME Shell startup is slow - hits a timeout of around 25 seconds - when the network is down, on Fedora 18 with gnome-shell 3.6.2-6. Comparing console output from 'gnome-shell --replace &' with network up and down, I see this additional message when the network is down: JS LOG: Failed to add search provider "Files": Gio.IOErrorEnum: Error calling StartServiceByName for org.gnome.Nautilus.SearchProvider: Timeout was reached Trying to run nautilus with the network down seems to hit a similar timeout - it takes a long time to start, and shows a message 'Could not register the application: Timeout was reached' when run at a console. I have a WebDAV share stored as a bookmarked 'Place', which may affect this.
This seems to be a bug in nautilus: it should not timeout on start if network is not available. Also, the shell side of this is fixed in 3.7.*, because search providers are loaded fully asynchronously.
Still broken in shell 3.6.3.1-1 / nautilus 3.6.3-5 (F18).
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.