Never ending load if location requests are blocked
It seems like the development version (?) sometimes (?) gets stuck in a never ending load-loop if location requests are blocked in Settings > Privacy > Location Services. It does not always happen, and it doesn't log requests properly either. Not sure why.
This is the error message dumped in the console.
john@hydra:~$ flatpak run org.gnome.WeatherDevel
F: Ignoring D-Conf migrate-path setting /org/gnome/Weather/
Gtk-Message: 14:44:26.438: Failed to load module "canberra-gtk-module"
Gtk-Message: 14:44:26.449: Failed to load module "canberra-gtk-module"
Gjs-Message: 14:44:27.117: JS LOG: Failed to connect to GeoClue2 service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 1000
(org.gnome.WeatherDevel:2): GLib-GObject-WARNING **: 14:44:27.313: The property GTlsClientConnectionGnutls:use-ssl3 is deprecated and shouldn't be used anymore. It will be removed in a future version.
(org.gnome.WeatherDevel:2): Gjs-CRITICAL **: 14:44:27.835: JS ERROR: TypeError: info.location.get_timezone() is null
update@resource:///org/gnome/WeatherDevel/js/app/city.js:212:50
_onUpdate@resource:///org/gnome/WeatherDevel/js/app/city.js:336:24
set info/this._updateId<@resource:///org/gnome/WeatherDevel/js/app/city.js:312:22
main@resource:///org/gnome/WeatherDevel/js/app/main.js:268:32
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
@/app/bin/gnome-weather:6:17When access is turned on a dialog pops up, and giving access the app loads properly.
Proper operation of the app should not depend on the app being granted this right, as a lot of computers lacking proper location services, and some ISPs have networks that will not assign stable IP-addresses that can be used for this purpose. In my case I'm on a radio link with a tower covering half of Southern Norway, and may be assigned an IP that has been used anywhere within the area. And no, there is no other WiFi within range. Using the IP-address for location services is pure nonsense in this case.
If Geolocation is disabled, then the app should progress with asking for a location (it is there, perhaps the app crashes too early), or if that is already set then that location should be used.
Addition: There is a toggle for use of automatic loaded locations, it is «Automatisk lokasjon» in Norwegian, and if this is turned off (!) then I'm back to the bogus behavior. If it is turned off it also gets removed, so it can't be set again. To get back to normal behavior I must do rm -fr .var/app/org.gnome.WeatherDevel. If it is left on I can search for «Leirskogen kyrkje» and selecting it, not just hitting return, I do get the expected result. It is slightly weird…
This is the user interface in Norwegian with the toggle visible.