search

flathub / org.gnome.clocks

https://flathub.org/apps/details/org.gnome.clocks
1 stars 8 forks source link

Integration with shell is not working #6

Closed dac73 closed 5 years ago

dac73 commented 5 years ago

On Fedora Silverblue integration with Top Bar is not working (no world clock under the calendar).

nedrichards commented 5 years ago

I believe this is due to:

(gnome-clocks:3): org.gnome.Clocks-WARNING **: 15:36:01.148: geocoding.vala:44: Failed to connect to GeoClue2 service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'org.gnome.clocks' disallowed, no agent for UID 1001

You'll note that the app-id has subtly different capitalization.

dac73 commented 5 years ago

I'd say this error (GeoClue2) is connected with automatic geolocation. If I run it with --devel it asks me to grant permission to access my location, after allowing it, it correctly sets my home time zone but it still doesn't integrate into Gnome top bar. (under the calendar, like on image). image

alice-mkh commented 5 years ago

mclasen told me before it's because gnome-shell tries to directly use Clocks' (and Weather's) gsettings and when you're running them in Flatpak, their schemas aren't visible to host.

dac73 commented 5 years ago

Then this is not an appropriate place for this kind of issue? Wondering then if this will be solved with https://github.com/flatpak/xdg-desktop-portal/issues/241 ? Or did I miss the problem completely?

alice-mkh commented 5 years ago

No, it's the other way around.

https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/js/ui/dateMenu.js#L98-103 gnome-shell should stop doing this, this setting effectively doesn't exist for host when the app is in flatpak, same as if it's not installed at all.

Ditto https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/js/misc/weather.js#L61-67 for Weather.

And look into the Util.AppSettingsMonitor implementation.

bilelmoussaoui commented 5 years ago

This was fixed in GNOME 3.34 & Gnome Clock 3.34

tukusejssirs commented 6 months ago

Update: Ignore this comment. I have open #50.

I’m not sure if you want me to create a new issue or not …

I experience a similar error (geocoding.vala:42: Failed to connect to GeoClue2 service: Start failed) using Clocks@45.0. Note that it has asked me whether I allow it to access location which I denied. Then I opened Timer and started the timer. Then it crashed.

I believe it should accept my decision of denied the location access.

I have noticed that geolocation in gsettings is set to true even after denying the location access, so I went and changed the value to false (using flatpak run --command=gsettings org.gnome.clocks set org.gnome.clocks geolocation false), however, it didn’t helped to work this issue around and it still crashes, but no GeoClue2 warning is returned.

So I installed org.gnome.Sdk/x86_64/45 and run the app using --devel (flatpak run --devel org.gnome.clocks) to find out why it crashes, however, it didn’t output any logs.

Even after resetting the app perms (using flatpak permission-reset org.gnome.clocks) and allowing the location access, the app fails, therefore, it looks like a totally different issue.

Note that I use Sway WM 1.8.1.