tatokis
commented
1 year ago Old alarm data is stored in GConf. This would be in ~/.gconf/apps/alarm-clock.
The new GTK3 version stores alarms using GSettings (with DConf typically as the backend), which is a fully binary format in ~/.config/dconf.
The application on first run tries to convert from GConf to GSettings. If you ran the application and then restored the backup, it wouldn't have detected it and marked the migration as "completed".
If you don't have any new alarms in the new GSettings backend (as they will most likely be overwritten), you can force a migration by running alarm-clock-applet-gconf-migration --force.
The version from the Debian/Ubuntu repositories has that binary in a separate package (alarm-clock-applet-gconf-migration), and unless you've told it to not install recommends, it should be installed automatically along with the alarm-clock-applet package.
Hope this helps.
Applets are new territory for me, that is how they work and where they store stuff. I Had an earlier Alarm-clock-applet version on my Ubuntu 18.04 system with a bunch of alarms set up. [I have no sense of time passing so with out them I have a lot of "What, What!" experiences.] I had both data and OS backups when the 2011 era laptop died. I have restored the data backup on this Ubuntu Studio 22.10 system, but my newly installed Alarm-clock-applet has retrieved none of my alarms. Much reading has not turned up possible $Paths, or file names for which to search, just more confusion on my part. If you can provide guidance, or at minimum supply old and new path and file names, assuming changes may have occurred with the port to GTK 3, I would be most appreciative.