The only file in that location is .../gnucash/books/etsmoney.gnucash.gcm
I just ran each and every report with no problem - just ran it, then
closed it. No new files or folders created.
On 2/13/21 5:26 PM, David Carlson wrote:
If you still have a copy of your user prefs for 2.6 the .gcm file
If you still have a copy of your user prefs for 2.6 the .gcm file in the
books folder contains the configurations for any reports that were open
when the data file was last closed. This could help to create similar
reports in the new format.
On Sat, Feb 13, 2021 at 3:20 PM Elmar wrote:
> In the
In the absence of any follow-up, I am guessing that I'm hosed? Just
have to delete the saved-reports-2.4 and try to rebuild my reports from
scratch?
On 2/11/21 11:36 AM, Elmar wrote:
Running "/usr/bin/flatpak run --branch=stable --arch=x86_64
--command=gnucash --file-forwarding org.gnucash.Gn
I'm trying to edit and/or delete existing reports, not (yet) create new
ones. Or do you mean the trace file? In the command string I used
--logto=$HOME/gnucash.trace, and that file was created. It just had no
contents.
On 2/12/21 1:40 AM, Christopher Lam wrote:
You normally specify the name
You normally specify the name when Saving a report. What name did you use?
On Fri, 12 Feb 2021, 12:36 am Elmar, wrote:
> Running "/usr/bin/flatpak run --branch=stable --arch=x86_64
> --command=gnucash --file-forwarding org.gnucash.GnuCash
> --logto=$HOME/gnucash.trace" in a terminal window invok
Running "/usr/bin/flatpak run --branch=stable --arch=x86_64
--command=gnucash --file-forwarding org.gnucash.GnuCash
--logto=$HOME/gnucash.trace" in a terminal window invoked GC fine.
Opening the saved reports item, then trying to delete a report results
in this output in the terminal window:
Ok, the branch specification is probably important.
You can try as follows:
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=gnucash --file-
forwarding org.gnucash.GnuCash --logto="path-to-log-to-or-stdout"
My mail client splits this line up, but the command should be all on one line.
The menu item cals GC via "/usr/bin/flatpak run --branch=stable
--arch=x86_64 --command=gnucash --file-forwarding org.gnucash.GnuCash @@
%f @@"
And this is the first (and only) flatpak I have ever installed. I
installed Flatseal so GC could find my data files as well, of course.
On 2/11/21
In that case the first thing to do is to figure out how exactly your system
calls the flatpak version of gnucash. There are quite a few subtle details
that may affect this.
You can examine the menu entry to figure out what command is being run
exactly.
Out of curiosity have you been removing i
Trying "flatpak run org.GnuCash.gnucash --logto=$HOME/gnucash.trace"
does not invoke the program and instead gives me
"error: app/org.GnuCash.gnucash/x86_64/master not installed"
Which is very odd, since it runs from the menu system fine.
- Elmar
On 2/11/21 3:59 AM, Geert Janssens wrote:
The
Op donderdag 11 februari 2021 03:42:52 CET schreef Christopher Lam:
> Scheme backtraces are usually found at
> https://wiki.gnucash.org/wiki/Tracefile but if flatpak hides them somewhere
> obscure you can dump onto console via "gnucash --logto=stdout". See
> https://wiki.gnucash.org/wiki/Logging
>
Scheme backtraces are usually found at
https://wiki.gnucash.org/wiki/Tracefile but if flatpak hides them somewhere
obscure you can dump onto console via "gnucash --logto=stdout". See
https://wiki.gnucash.org/wiki/Logging
On Thu, 11 Feb 2021, 6:29 am Elmar, wrote:
> The sequence of events was tha
The sequence of events was that I had been running 3.8, but somehow it
started to fail badly, with CTD. So I uninstalled that one and
reinstalled the one from the Mint repository, which was 2.6.19. All
seemed well. I tried to reinstall 3.6 and then 3.8, then 3.11, but the
installs failed in w
Elmar,
Can I ask how you went from 2.6.19 to 4.4 flatpak? Did you just open your
version 2.6.19 file in the latest flatpak version 4.4 or did you update to
version 3 and then version 4 to convert your gnucash file correctly? I've
always understood you can't just go from 2.6.19 to 4.4, you have t
Thank all for the replies, but what are "scheme backtraces" and where do
I find them? and how do I "convert" my 2.4 reports to 4.4 compatible
ones? - Elmar
On 2/9/21 11:46 PM, John Ralls wrote:
Elmar,
A fair amount of Scheme API was deprecated in 3.x and removed in 4.x. Look
through the NEW
Thanks Geert, that makes sense.
Regards,
Adrien
On 2/10/21 3:24 AM, Geert Janssens wrote:
Op woensdag 10 februari 2021 06:08:21 CET schreef Adrien Monteleone:
Out of curiosity, is there something to explain the numbering scheme for
reports? Is there a reason they don't follow the GnuCash versi
Op woensdag 10 februari 2021 06:08:21 CET schreef Adrien Monteleone:
> Out of curiosity, is there something to explain the numbering scheme for
> reports? Is there a reason they don't follow the GnuCash version
> pattern? (we're in version 4.x of GnuCash but reports go in a 2.8 folder)
>
> This ca
Hi Adrien,
Am 10.02.21 um 06:08 schrieb Adrien Monteleone:
> Out of curiosity, is there something to explain the numbering scheme for
> reports? Is there a reason they don't follow the GnuCash version
> pattern? (we're in version 4.x of GnuCash but reports go in a 2.8 folder)
why changing the ver
Out of curiosity, is there something to explain the numbering scheme for
reports? Is there a reason they don't follow the GnuCash version
pattern? (we're in version 4.x of GnuCash but reports go in a 2.8 folder)
This can get quite confusing when discussing app versions vs. reports.
Regards,
Ad
Elmar,
A fair amount of Scheme API was deprecated in 3.x and removed in 4.x. Look
through the NEWS file for which ones. There should be Scheme backtraces in the
trace file that will help identify the source of the crash.
Regards,
John Ralls
> On Feb 9, 2021, at 3:01 PM, Elmar wrote:
>
> I j
I just took the 2.4 file, copied it (CTRL-C/CTRL-V) and renamed it to
2.8. Opened GC, tried to delete one report, and got a crash to
desktop. So no joy there, unless I have misunderstood what you suggested.
On 2/9/21 4:38 PM, David H wrote:
Elmar,
Since you say they seem to run, why don't y
Elmar,
Since you say they seem to run, why don't you try closing gnucash and then
copying your saved-reports-2.4 to saved-reports-2.8, re-opening Gnucash and
opening each saved report in turn and then if everything looks ok saving
the config of each of your reports ? I've upgraded over the years
Honestly, I don't know. Hopefully Geert or John or Chris will reply with
more authoritative answers.
-derek
On Tue, February 9, 2021 4:17 pm, Elmar wrote:
> Since they do run and do extract the correct data OK, can I simply
> resave them, or if not, trivially alter some aspect to save under a ne
Since they do run and do extract the correct data OK, can I simply
resave them, or if not, trivially alter some aspect to save under a new
name to avoid having to remember what I all tweaked in each of them?
On 2/9/21 4:02 PM, Derek Atkins wrote:
Hi,
It is certainly true that 2.6 reports are
Hi,
It is certainly true that 2.6 reports are not compatible with 4.4. So
yes, I would expect saved reports to not have made the transition.
-derek
On Tue, February 9, 2021 3:58 pm, Elmar wrote:
> Running the flatpak 4.4 on Linux Mint 19.3 - I've copied my version
> 2.6.19 reports into the gnuc
Running the flatpak 4.4 on Linux Mint 19.3 - I've copied my version
2.6.19 reports into the gnucash folder in
/home/ets/.var/app/org.gnucash.GnuCash/data/gnucash (saved reports
2.4). They al show up and run fine, BUT as soon as I try to delete one
of them, I get a CTD, a locked data file, and
26 matches
Mail list logo
