Not possible to close remider alarm on Ubuntu 21.10

When alarm is triggered (for example appointment), then Orage displays every second new reminder window or notify message. It is not possible to silence alarm, cliking to any reminder window button does not have any effect. Only way to silence alarm is to change alarm time in appointment window. I noticed this effect only on Ubuntu 21.10.

Isn't this a Wayland-specific problem, as in #2 (closed)?

Not sure. There are only GLib and GTK functions and nothing direct to X11. I try to check next weekend if there is any relations to Wayland.

Isn't there the possibility to switch between Wayland and X11 at login on Ubuntu? It seems to me that it was the case before.

Still same with X11, every second pop up new reminder window.

No problem to silence the alarm on Arch Linux - Xfce, but I get these warnings when it is triggered:

(orage:75068): GLib-CRITICAL **: 11:38:01.616: g_child_watch_add_full: assertion 'pid > 0' failed

** (orage:75068): WARNING **: 11:38:01.616: reminder: play failed (/opt/share/orage/sounds/Spo.wav) Failed to execute child process ?play? (No such file or directory)

Probably 'play' progam is not installed. If you remove sound alarm option then this message should go away.

Yes, but even then it shouldn't issue a warning, at least not a critical one. I'll take a look at it.

GLib-CRITICAL fixed in 15227cdc. We could also check for the optional presence of the play command (in sox?) during the configuration, but it is optional :) (and it's not sure it's a good idea to add another compiler switch for that)

I like the idea to checking 'play' or any other sound program during configuration and set default sound program accordingly. Sound command can be set from preferences anyway, so it is not essential.

mentioned in merge request !8 (closed)

mentioned in commit 15227cdc

changed milestone to %4.18.0

added 1. Crash / Freeze label

assigned to @erxus

mentioned in merge request !40 (merged)

removed milestone %4.18.0

Can't reproduce this bug anymore. Quite likely reset_orage_alarm_clock and orage_alarm_clock calls each other through timer callback (recursive calls). Probably the OS type, version and/or libraries likely contribute on this bug: I have seen similar behavior once under FreeBSD (repeat two times, not infinite) and never on Ubuntu 22.10. Tested with different git commits. Removing milestone, but leaving bug open.

unassigned @erxus

added 3. Need Info label