debcrafters-packages team mailing list archive

[Simon Poirier <2071926@xxxxxxxxxxxxxxxxxx>]

I believe I was able to reproduce on 24.04.
For this to work you need multiple timers (e.g. 4s each), some of which have already completed.

Looking at dbus-monitor notifications, it gets absolutely clear that the
ring callback gets triggered multiple times, as not only the sound adds,
but notifications pile up too.

> Looking at the code, it has logic to only ring the bell once,

There could be some aliasing in the setup of timers.

** Changed in: gnome-clocks (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-clocks (Ubuntu)
       Status: Incomplete => Confirmed

** Changed in: gnome-clocks (Ubuntu)
       Status: Confirmed => Triaged

** Tags added: dcr-incoming

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to gnome-clocks in Ubuntu.
https://bugs.launchpad.net/bugs/2071926

Title:
  Timer sound repeatedly firing after the timer has ended

Status in GNOME Clocks:
  New
Status in gnome-clocks package in Ubuntu:
  Triaged

Bug description:
  Ubuntu release: 24.04 LTS
  gnome-clocks version: 46.0-1build1

  After starting and completing the timer, the timer completion sound
  continues to fire periodically. If multiple timers are started and
  completed, the amount of sounds increases. I haven't been able to
  verify this, but I suspect it happens at regular intervals coinciding
  with the timer's length, because when strting the same timer back-to-
  back (when cooking), I end up with clusters of "dings" happening
  roughly at the same time. This persists until the app is quit and
  restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-clocks/+bug/2071926/+subscriptions