Don't run gsettings-data-convert on startup
Submitted by Lucas Beeler
Assigned to Lucas Beeler
Link to original bug (#719042)
Description
---- Reported by lucas@yorba.org 2013-02-11 18:15:00 -0800 ----
Original Redmine bug id: 6369
Original URL: http://redmine.yorba.org/issues/6369
Searchable id: yorba-bug-6369
Original author: Lucas Beeler
Original description:
Shotwell versions 0.11.x through 0.13.x run the gsettings-data-convert tool every time Shotwell is invoked. While this might've made sense right after the transition from GConf to GSettings, that transition occurred 18 months ago. What's more, given tickets like #5983, it's clear that in some cases the current behavior causes glitches in the user experience for people. Since gsettings-data-convert is run by the operating system on login anyway, that should be enough to cover most users.
Related issues:
- related to shotwell - 5983: GSettings converter crashes harmlessly at startup on some... (Invalid)
- related to shotwell - 6252: Don't run GSettings before printing version or displaying... (Fixed)
- related to shotwell - 5027: [norepro] user can't change library location (Invalid)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Jim Nelson 9 months ago
Fixing this bug will also close #6252.
Comment 2
Updated by Lucas Beeler 9 months ago
- Status changed from Open to 5
Applied in changeset 921e0bd9.
Comment 3
Updated by Lucas Beeler 9 months ago
- Resolution set to fixed
Comment 4
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:59 UTC ---
This bug was previously known as bug 6369 at http://redmine.yorba.org/show_bug.cgi?id=6369
Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.14.0
Resolution: RESOLVED FIXED