I managed to replicate the error on Win7 and I've debugged into it a bit. The gibberish in the pathname is because a wide-character string returned from Windows is getting interpreted as a normal-character string. But that's not the only problem, the path to the user-config-dir is getting overwritten with the candidate storage path, and that's what's causing the error.
For some reason this doesn't happen on Win10, so a parallel debugging session there is next. Regards, John Ralls > On Apr 11, 2019, at 10:22 AM, Adrien Monteleone > <adrien.montele...@lusfiber.net> wrote: > > Nevermind. I got lost in the thicket. > > I see a message now that you already eliminated DropBox as the problem > because there are local paths that won’t save either. > > Sorry for the noise. > > Regards, > Adrien > >> On Apr 11, 2019, at 12:14 PM, Adrien Monteleone >> <adrien.montele...@lusfiber.net> wrote: >> >> Colin, >> >> This is what I understood as the point to test some messages ago. >> >> Greg, >> >> Several messages back someone mentioned needing to install the DropBox >> client to get real paths as opposed to some mapped paths. The reason for >> this is the mapped paths (which are displayed as real paths instead) are >> insanely longer than the real ones. (ostensibly using some sort of UUID in >> place of each path node) If you use the client, you’ll be using the real >> displayed paths that you see. The premise is that while DropBox is showing >> you what you think is the path, it is reporting something else to GnuCash. >> The path is being garbled by the error message because of non-standard >> characters in the mapped path from DropBox. >> >> So the problem *might* be resolved, (or at least pinpointed) by showing FULL >> paths, because that would show you the path you think you are accessing >> isn’t really that short, it is MUCH longer. >> >> Of course, this might not resolve the problem, but eliminating possibilities >> is part of chasing bugs. If you do have the desktop client installed, then >> you still have another problem, or you indeed found a bug. >> >> Regards, >> Adrien >> >> >>> On Apr 11, 2019, at 10:58 AM, Colin Law <clan...@gmail.com> wrote: >>> >>> And, to continue, I hit reply too soon. It is the actual path that >>> gnucash sees not the mirage, so potentially something in the actual >>> path is confusing GC. >>> >>> Colin >>> >>> On Thu, 11 Apr 2019 at 16:55, Colin Law <clan...@gmail.com> wrote: >>>> >>>> In that case I misunderstood. I thought the point was that Dropbox >>>> does some clever path mapping that makes it look as if the file is at >>>> the location you see in the browser, but actually that is a mirage. >>>> It is actually somewhere else entirely. >>>> >>>> Colin >>>> >> > > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
