Open tukusejssirs opened 6 months ago
Hello,
Is this issue uniquely reproducible with the flatpak build of Clocks? If not, please open an issue upstream at https://gitlab.gnome.org/GNOME/gnome-clocks.
This repository is uniquely for the flatpak distribution of the app. Unless the issue is specifically related to how the app is distributed (i.e. fixable here), it should go upstream.
Using dnf
, I could install gnome-clocks-44.0-1.fc38.x86_64
(i.e. not v45.0
, unfortunately) and that version works as expected. I would need to upgrade to Fedora 39 in order to test v45
installed.
However, I have downgraded the Flatpak package to v44
(specifically to commit 199ebc66cd65750ccec14b26b76770ca3e8a5aa71e71aa9eb91ea6a01431160d
) and it works without any issues, therefore, I presume it boils down to incompatible org.gnome.Platform
(Gnome) versions (v44
vs v45
), however, I am unable to prove that.
Is there a way to prove that? :thinking:
You can try to use GNOME Builder (from flathub too) and build a local build of the app using a commit or tag of your choosing.
Please ping me at https://matrix.to/#/#clocks:gnome.org if you have any questions.
Originally posted by @tukusejssirs in https://github.com/flathub/org.gnome.clocks/issues/6#issuecomment-1999882261
The app crashes when a timer or stopwatch is started. I tried to run the app on Fedora 38 with Sway WM 1.8.1. I used
Clocks@45.0
.At first, I’ve thought it was related to a
GeoClue2
warning, however, it seems to be unrelated. No other log is output, even after installingorg.gnome.Sdk/x86_64/45
and run the app using--devel
(flatpak run --devel org.gnome.clocks
).However, I think that when a user denies the geolocation permission to the app, it should set
org.gnome.clocks geolocation
ingsettings
tofalse
.