GNOME Bugzilla – Bug 772819
Alarms won't work when the app is closed
Last modified: 2017-08-24 20:39:18 UTC
I've never used clocks for alarms but when I needed I set it to notify everyday at an specific time, I use my computer everyday, all day long so I thought I was gonna be notified about a medicine I had to take at that specific time but it didn't because the app was closed. I hope you implement alarm notifications when the app is closed.
It's worse than that. This bit me the first time I ever set a timer so today I set another timer and just put the running timer in another workspace but when it expired again there was no alarm (until I went to that workspace or I go to the overview). So I tried again, this time minimizing the timer in the current workspace but again, no alarm. So it turns out the timer must be left in the foreground, and in the current workspace, before it alarms at the correct time. This is a terribly poor design. This is on up to date Arch Linux with gnome-clocks 3.22.0+2+g74a75f7-1. Burned my wife's cookies :(
duplicate of bug 735869
(In reply to Mohammed Sadiq from comment #2) > duplicate of bug 735869 if this is a duplicated bug, why you didn't close it?
Also, that bug 735869 is about not getting a notification if the app is closed but as I comment just above the bug is actually much worse than that. Can the OP change the title to "Alarms won't work when the app is minimized or on another workspace"?
(In reply to Ricardo Ramos from comment #3) > if this is a duplicated bug, why you didn't close it? I'm not a developer. So I don't have the rights to do that. You (or some developer) will have to do this. (In reply to Mark Blakeney from comment #4) > Also, that bug 735869 is about not getting a notification if the app is > closed but as I comment just above the bug is actually much worse than that. In bug 735869 you can see that Bug 689082 is marked as its duplicate, which is exactly this same issue. > > Can the OP change the title to "Alarms won't work when the app is minimized > or on another workspace"? I can't reproduce this. Alarm works here when minimized or when on another workspace. Thanks
Ok, here's the simple procedure I can reproduce every time. 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). 3. So long as you are on another workspace to the app at the end of the minute, you will not hear the alarm. But you will hear the alarm the instant your open the overview. Stock GNOME on up to date Arch.
(In reply to Mark Blakeney from comment #6) > 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). > 3. So long as you are on another workspace to the app at the end of the > minute, you will not hear the alarm. But you will hear the alarm the instant > your open the overview. Works fine here on Debian testing gnome-clocks 3.22.1
@Mohammed, I disabled all my extensions but still happens. I am using Wayland (as stock GNOME on Arch now does) if that matters.
Logged out and back in with GNOME on Xorg and the timer works fine. So is a Wayland related issue.
(In reply to Mark Blakeney from comment #9) > Logged out and back in with GNOME on Xorg and the timer works fine. So is a > Wayland related issue. Hm.. Yeah. I can too reproduce this on wayland.
You should create a separate bug about that issue with wayland because this bug I posted includes both Xorg and wayland.
Created bug 774243.
*** This bug has been marked as a duplicate of bug 735869 ***