[GNC] Error While Saving in GnuCash 3.5 on Win7-64

Fri Apr 5 22:00:58 EDT 2019

Well, Chris Graves, nvsoar,

I copied the original folders so I could make a test path exactly like the
path that causes the error, but with no ampersand, and I still get the the
same problem.

The path C:\Dropbox\My Docs\Thorough C and D\GnuCash\GnuCash Files\ fails
just like C:\Dropbox\My Docs\Thorough C & D\GnuCash\GnuCash Files\ fails.

A screen shot of the error
https://www.dropbox.com/s/gd8rlgj1kvv0ysn/2019-04-05_18-37-52.png?dl=0

All,

I copied the original folder so I could make a test path exactly like the
path that causes the error, but with no spaces in the folder names and no
ampersand, and I still get the same problem.  However, this time, when
gnucash tried to display the path in the error message, it got some of it
right.

A screen shot of that is here:
https://www.dropbox.com/s/e3p0agpdlkmzia4/2019-04-05_18-52-26.png?dl=0

Thanks for all the help, folks.
Kind regards,

Greg Feneis

On Fri, Apr 5, 2019 at 6:31 PM Greg Feneis <mfeneis at gmail.com> wrote:

> Adrien, Geert,
>
> From the gmail web interface, I hit reply to the latest email I received
> from this list and changed the subject line to be what I wanted, and
> deleted the entire body before typing up what I wanted to say.  I thought
> it was the subject text that directed emails into various conversations
> (threads).  It seems to in gmail.  Apparently there's some stuff in the
> email's headers that make the email appear to belong to another thread.
> Knowing this, from now on, I'll start threads using virgin emails.
>
> Kind regards,
>
> Greg
>
>
>
>
> On Fri, Apr 5, 2019 at 10:20 AM Adrien Monteleone <
> adrien.monteleone at lusfiber.net> wrote:
>
>> It threaded that way for me as well. But then once the first reply came
>> back, it somehow magically decoupled. I chalked it up to a Mail.app hiccup.
>> Now I’m intrigued as to how it got separated. Curious to see what the
>> Mailman archive page shows.
>>
>> Regards,
>> Adrien
>>
>> > On Apr 5, 2019, at 11:06 AM, Geert Janssens <geert.gnucash at kobaltwit.be>
>> wrote:
>> >
>> > Hi Greg,
>> >
>> > It was "hijacked" in the sense that you seem to have started it by
>> replying to
>> > John Ralls' reply on the "help lost data file" thread. So my mail
>> client did
>> > hide your message in that thread. Apparently that also happened for
>> Frank.
>> >
>> > Of course I can't *know* what you did exactly. It just *looks* like
>> this is
>> > what you did: take an existing message, hit reply (or reply to
>> list/all),
>> > change subject and body, send. That would cause such a message to end
>> up
>> > hidden in the original thread.
>> >
>> > In any case I also didn't immediately see your message.
>> >
>> > Regards,
>> >
>> > Geert
>> >
>> > Op vrijdag 5 april 2019 15:56:24 CEST schreef Greg Feneis:
>> >> Hi Frank,
>> >>
>> >> I started this thread. I've been driving this thread since I started
>> it.
>> >> What made you think I hijacked?
>> >>
>> >> I was aware of bugzilla, but it's not an email list.  I had some
>> concern
>> >> that the process had changed from when I last monitored this list many
>> >> months ago.  Previously an error like this gets discussed, and
>> someone, a
>> >> developer or person who works more closely with the project, asks the
>> >> reporter to log it to bugzilla.
>> >>
>> >> Kind regards,
>> >>
>> >> Greg Feneis <http://www.linkedin.com/in/electromechanical>
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Apr 4, 2019 at 10:43 PM Frank H. Ellenberger <
>> >>
>> >> frank.h.ellenberger at gmail.com> wrote:
>> >>> Am 04.04.19 um 17:28 schrieb Greg Feneis:
>> >>>> Is there some other gnucash list I should use to report program
>> errors?
>> >>>
>> >>> Yes, Greg,
>> >>> read https://wiki.gnucash.org/wiki/Bugzilla for the details.
>> >>>
>> >>> BTW: Next time instead of hijacking other threads start a new one. ;-)
>> >>>
>> >>> Regards frank
>> >>>
>> >>>> Kind regards,
>> >>>>
>> >>>> Greg Feneis <http://www.linkedin.com/in/electromechanical>
>> >>>>
>> >>>> On Tue, Apr 2, 2019 at 5:41 PM Greg Feneis <mfeneis at gmail.com>
>> wrote:
>> >>>>> Hi,
>> >>>>>
>> >>>>> I just upgraded to 3.5 from 2.6.21.
>> >>>>>
>> >>>>> I've been using 2.6.x for a few years, and never had trouble saving
>> to
>> >>>>> this directory, but after upgrading to 3.5, I tried to save and it
>> >>>
>> >>> gives me
>> >>>
>> >>>>> an error message.
>> >>>>>
>> >>>>> "You attempted to save in "can't be displayed" or a subdirectory
>> >>>
>> >>> thereof.
>> >>>
>> >>>>> This is not allowed as GnuCash reserves that director for internal
>> use.
>> >>>>>
>> >>>>> Please try again in a different directory."  (close)
>> >>>>>
>> >>>>>
>> >>>>> Here's a link to a screen shot of the error message:
>> >>>>>
>> https://www.dropbox.com/s/1opqys3wxuyw4rv/2019-04-02_17-05-34.png?dl=0
>> >>>>>
>> >>>>> Note that where I wrote "can't be displayed" is actually a strange
>> >>>
>> >>> graphic
>> >>>
>> >>>>> like when an emoji can't be displayed.  See the screen shot.
>> >>>>>
>> >>>>> It appears when the error message was generated, the file path
>> couldn't
>> >>>
>> >>> be
>> >>>
>> >>>>> parsed.  This makes me think GnuCash isn't capable of parsing the
>> save
>> >>>
>> >>> to
>> >>>
>> >>>>> path.  I suspect it's a path length issue.  I tried shorter paths
>> and
>> >>>>> it
>> >>>>> worked.  FSR, the new GnuCash seem like it can't save to the same
>> >>>>> length
>> >>>>> path that the old series was capable of.
>> >>>>>
>> >>>>> Sorry if this is already a known issue
>> >>>>>
>> >>>>> Kind regards,
>> >>>>>
>> >>>>> Greg Feneis <http://www.linkedin.com/in/electromechanical>
>>
>>
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at 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.
>>
>