shotwell 'lost' my settings on package update. Importantly, this includes the preference for photo library location, so if not noticed will silently start to import photos to the wrong location (and since paths are tracked in the db, the imported photos can't just be moved on the filesystem without correcting in the db too -- messy). Settings were also reset for the map widget and dark mode (the latter being what allowed me to spot the bug), perhaps other settings. I suspect the updates are reverting settings to their defaults. I note from release notes that shotwell 31 introduces 'profiles' for settings, and changes to dconf settings to comply with flatpaks. I also see shotwell 31 is the unstable branch; I'm not sure why Fedora is packaging this rather than the stable 30.x. I can't now revert back to the 30.x branch (e.g. via flatpak) due to db incompatibilities. I lost these settings on F31 after the update to shotwell-0.31.1-1 Then on upgrade to F32 I've moved to shotwell-0.31.2-1 and the settings have been cleared a second time.
As far as I can tell: Prior to 0.31.1 dconf preferences were in /org/yorba/shotwell/preferenes/ In 0.31.1 this moved to /org/yorba/shotwell/profiles/preferences/ In 0.31.2 this moved to /org/gnome/shotwell/profiles/preferences/ On each move existing preferences are not copied to the new location. (Given 0.31 is the unstable branch, this may be reasonable, and a migration fix planned before the 0.32 stable version. Although this would question the prudence of Fedora tracking the 31.x branch.)
Hi Kevin, I can answer the part of why Fedora is packaging the unstable branch: Fedora follows GNOME releases and at the time of Fedora 31 release, shotwell 0.31.0 was released as part of stable GNOME 3.34.x. This led to us including shotwell 0.31.0 in Fedora 31 and subsequent releases; the expectation from our side was that there's going to be a stable shotwell 0.32 release very soon. This has however not happened and we're still stuck on the unstable shotwell branch, sadly. As for the settings not being correctly migrated: can you ask upstream about that (https://gitlab.gnome.org/GNOME/shotwell)? I don't think we have anyone working on shotwell code here.
Thanks for the reply! (In reply to Kalev Lember from comment #2) > As for the settings not being correctly migrated: can you ask upstream about > that (https://gitlab.gnome.org/GNOME/shotwell)? Unfortunately it looks like I can't create a new bug report without an account, and there is no way to register a new account (other than via google etc. -- not great). "Please note that due to spam, new user registrations are disabled. Please use 3rd party logins for logging in if you don't have an existing account." I have an account on the old gnome bugzilla, but that seems to be long dead.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.