GNOME Bugzilla – Bug 774243
Clock timer does not notify if mimimized or in different workspace when running on Wayland
Last modified: 2017-10-24 15:46:46 UTC
I am running stock Arch Linux using GNOME on Wayland which is the default. When a GNOME clock timer expires you don't see or hear the alarm if the clock app was running in a different workspace, or was minimized, at the time the alarm expires. I created this new bug after my comments in bug 772819 and somebody else there confirmed the same bug observation. 1. Open the clock app, set a timer for 1 minute and start. 2. Move the app to another workspace, or move your focus to another workspace, or minimize the clock app. 3. So long as you are on another workspace to the app at the end of the minute, or it was mimimized, you will not hear the alarm. But you will hear the alarm the instant your open the overview. Works fine on using GNOME on Xorg, doesn't work when running on Wayland. Using gnome-clocks 3.22.0+2+g74a75f7-1.
Can confirm. The timer alarm does not sound while it is minimized. If the timer has passed 0:00 while minimized, the alarm sounds when the timer is opened. This is easily tested with the timer set to 1 or 2 seconds. I am running gnome clocks on Fedora 25 Wayland, Gnome 3.22.2.
I just found this bug raised by me long ago and noticed it was still open. Testing nowadays on stock Arch with gnome-shell 3.26.1+6+g78d58deb5-1 and gnome-clocks 3.26.0-1 I see the problem does not exist anymore. The alert is seen and heard regardless of whether the app was in a different workspace or was minimized. So you can make this bug as fixed.