Description of problem:
If the clocks is shifted in another workspace, e.g. in below, the timer's timeout doesn't alarm, but after switching to that workspace, at time already expired.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set timer to 1 min
2. Shift clock to below workspace
3. After one minute no alarm (time exipred).
4. Switch to the worksapce, and you hear the alarm
No timeout alarm
Time out alarm even if clock is in another wprkspace
I can't reproduce this. Clocks (gnome-clocks-3.26.1-1.fc28.x86_64) just moved to another workspace still triggers the notification and the audible alarm in the current workspace.
Are you under wayland or X11 ? Can you try with the other one ?
I suppose to be in wayland. I'll try!
Just now, to be sure, repeated the problem. Setted 1 min on timer, launched, and moved it to below workspace. Waited three min, no alarm. Switched to below workspace and alarm triggered.
Another try: Opened the clock in a below workspace, launched after 1 min time-out setting. Switched focus to high workspace, no alarm triggered after expire. Switched again to below, and alarm was triggerd.
Sorry, my mistake, I mixed up Timer and Alarm. Reproduced with timer.
I'll try to chase this down.
Otherwise my pasta lunch overcooks! :-D
Filed an upstream bug with a proposed fix
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
FWIW an upstream fix for this landed in the clocks master branch released as 3.31.1, and currently built for rawhide. I don't think the fix will be coming for the older stable releases.