After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 765386 - Default Directory ignored
Default Directory ignored
Status: RESOLVED FIXED
Product: easytag
Classification: Other
Component: general
2.4.x
Other Windows
: Normal normal
: 2.4
Assigned To: EasyTAG maintainer(s)
EasyTAG maintainer(s)
: 749735 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-04-21 16:30 UTC by marcelrobitaille11
Modified: 2016-12-04 10:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description marcelrobitaille11 2016-04-21 16:30:55 UTC 
After I choose the default directory and reopen Easytag, it always goes back to C:\Users\<user>\Music\. This only happens on windows. On my Linux partition, it works fine.
Comment 1 David King 2016-04-22 07:38:13 UTC 
I rarely get the chance to test on Windows, but I guess that this is a problem with the GSettings integration on Windows (or rather, how EasyTAG installs the compiled schema cache, or some other problem with how the support files are installed). As such, it is unlikely that there will be a fix for this unless someone who runs EasyTAG on Windows figures out what the problem with the GSettings integration is.
Comment 2 David King 2016-11-16 13:12:41 UTC 
I tested this today, and it turns out to be a GLib bug with the encoding of strings when saved to (or loaded from, more importantly) the registry in the Windows GSettings backend. The good news is that GLib 2.48 and above work fine, but unfortunately those versions dropped support for Windows XP. I tried backporting just the GSettings registry backend changes to a version of GLib that supports Windows XP, but was unsuccessful, so the next stable version of EasyTAG will only support Windows Vista and above (but will correctly save and restore the default directory setting).
Comment 3 David King 2016-12-04 10:28:04 UTC 
*** Bug 749735 has been marked as a duplicate of this bug. ***