This is a discussion topic for the following Common Issue:
You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.
If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.
Please see the Common Issue for solution/workarounds:
Will this fix be eventually be back ported to Fedora 40 ? Or will I need to upgrade to Fedora 41 to use the alarm clock of gnome clocks ?
@onebrocoli I can’t reproduce this problem on Fedora 40. Are you sure you’re seeing this particular issue? Please describe the problem that you see on your system.
Yes, exact same symptoms as described on the common issue post.
I set alarm, close the window, time comes nothing happens, I click on the notification nothing happens. I kill gnome clock, and re-launch it and it starts ringing.
I’m on Fedora 40 Silverblue if that matters at all.
Hey ! So I looked a bit and if this is right then GTK4 hasn’t been updated since August 8th.
So has it been broken since august and no-one noticed until recently ? Or is GTK4 not at fault, but somehow updating it fix the issue ? Now I’m curious how all of that work
I tested again on F40 Silverblue this time, fully updated, and it works just fine for me. Which means your issue must have a different cause than the one described in the common issue. Create a new topic in Ask Fedora and somebody might help you debug it (collect logs, etc). Or try to switch to F41, if that helps. You can always go back, if needed, on an immutable system.
Yeah, maybe I’m cursed. I ended up succesfully upgrading to Sivlerblue 41, and gnome clocks works just fine. I still have Silverblue 40 pinned, but I don’t think I’ll go back to it.
Either way thanks a lot for trying to help me !!