Alarm Clock 0.9.18 - Shutdown -> alarms lost

Bug #419167 reported by uboot
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alarm-clock (Ubuntu)
Fix Released

Bug Description

Binary package hint: alarm-clock

Please update alarm-clock package to version > 1.0 for Jaunty AMD64

With the current v0.9.18, when shutting down the computer via Gnome System menu, Alarm Clock will not remember my alarms on next boot.

Only when I manually exit Alarm Clock before Shutdown, it will remember its settings...

The bug has been confirmed here:

Ryan Niebur (ryan52)
Changed in alarm-clock (Ubuntu):
status: New → Fix Committed
Revision history for this message
Ryan Niebur (ryan52) wrote : should be fixed in karmic+1

these bugs have most likely been fixed with newer upstream versions in
Debian, and the new version of the package will make it's way into the
release after karmic.

Ryan Niebur
<email address hidden>

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package alarm-clock - 1.2.4-1

alarm-clock (1.2.4-1) unstable; urgency=low

  * New Upstream Version
    - only change was already fixed in package,
      uploading anyway for updated email address
  * remove fix-duplicate-id patch, fixed upstream
  * update my email address and remove DMUA field

alarm-clock (1.2.3-2) unstable; urgency=low

  * don't do 'make check', it doesn't work right with quilt patches
  * add gtk-builder-proper-error-handling patch, used to debug LP 425163
  * add fix-duplicate-id, which fixes loading on Ubuntu (LP: #425163)

alarm-clock (1.2.3-1) unstable; urgency=low

  * New Upstream Version (LP: #400605, #419167)
    - has correct homepage link (LP: #375958)
  * add README.source
  * remove libglade2-dev from build deps, no longer needed
  * Debian Policy 3.8.3
  * fix some old ubuntu bugs in older versions (not yet synced) in the

alarm-clock (1.2.1-1) unstable; urgency=low

  * New Upstream Version
    - fixes simple counters (Closes: #537791)
  * patch to fix the autostart exec path (Closes: #537793)

alarm-clock (1.1-2) unstable; urgency=low

  * upload to unstable

alarm-clock (1.1-1) experimental; urgency=low

  * New Upstream Version
    - no longer uses glade (LP: #375952)
  * Debian Policy 3.8.2
  * remove patching
  * remove config.{log,status} in d/clean, and add lintain overrides for

alarm-clock (1.0~beta1-1) experimental; urgency=low

  * replace using the constantly changing ip address in debian/watch
    with using a script on my VPS
  * adopt packages (Closes: #521226)
  * New upstream release
  * remove all of the python and cdbs
    - this version is no longer in python
      (LP: #321795, #365079, #271489, #274121, #275090)
  * convert to dh7
  * convert to arch:any
  * add build deps and shlibs:depends
  * add a quilt patch to fix build
  * make changes to the menu and man page for the rename from alarm-
    clock to alarmclock
  * update man page, there is no longer any options
  * add DMUA header

 -- Ubuntu Archive Auto-Sync <email address hidden> Wed, 04 Nov 2009 01:45:04 +0000

Changed in alarm-clock (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.