Upon further review:
After exploring the forum in more depth, extending back about 2 years, I
found a number of the established developers of gnucash voicing their doubts
as to the viability of pushing gnucash passed what is in the ubuntu
repository. In my case since I have had a muitple
David,
If the library files (*.go) are not present in
/usr/local/lib/gnucash/scm/ccache/2.0/gnucash then there is definitely a
problems with the build and install. They should also occur in
.../gnucash3.7/build/lib/gnucash/scm/ccache/2.0/gnucash as this is where
they are created in the build
Made another decision to this purge and retry to install idea - after three
of these efforts previously, I'm moving on to a different plan. i'm going
to download a LM19.2 iso and flash the SSD to zero and attempt to build this
tarball with a fresh LM19.2 install. If that fails, there must be
Thanks David
For the look see on this. I will give it another go tomorrow after I do
another clean out uninstall/purge. As to the make and make install
feedback, as I mentioned I had no errors nor any warnings what-so-ever in
the compile process. I had the full libsecret files with its
Tax season is over , now back to the original problem of having on 3.7
version on my LM 19.2 box and by necessity, a Windows 10 box. I reviewed
all of David Cousens notes and suggestions. I spent any series of hours
spanning days, rooting out all known locations where gnucash may have been
Hi Stephen,
Thanks for jumping here. Yes to confirm I attempted your 3.7 build on the
18.04/LM19.2 and failed in dependencies that I could never overcome. So
even after loading the common.deb and then the python.deb, that main program
failed and was basically broken in the machine. I did enjoy
On 9/28/19 4:50 PM, David Cousens wrote:
> David,
>
> The problem with Synaptic particularly with Linux Mint since it is tied to
> an even earlier Ubuntu version than even the current Ubuntu distrbutions and
> that it is often lagging the actual development cycle for packages
> considerably (not
Thanks David for that update,
I'm saving that information for the time to attempt to build this again.
Tricky is an understatement for cmake - totally unforgiving - if it's not
precisely tuned, it will spray files all over the place. I have no idea how
to proof the key cmaketxt files for the
David,
I take it you have been using the wiki pages on Building on Linux
(https://wiki.gnucash.org/wiki/Building_On_Linux). cmake is a little bit
tricky at first. I occasionally get the command syntax wrong if i haven't
done a build for a while. The tricky bit is getting the relative addressing
Thanks David for the reply
I have a few moments before I'm back at the grind. As to the history of
gnucash installs, I guess i date myself back to the 2014-2015 coming off the
Moneydance era (once removed from Quicken/Quickbooks). At the time all
tarballs were done with Autotools and installs
David
I am running GnuCash 3.7 built on Linux Mint 19.2 from the tarball download
and I don't experience any of the problems you are describing with editing
the Description or Memo fields in a transaction in an account register or
in the General Journal tab at all. They change and are saved and
Sorry John, tried to reply;
but lost in the maze of nabble vs user and got rejected. As mentioned
earlier, I've got tax season and really don't have time this week to debug
troubleshoot - maybe next month.
My comments are only to be viewed at the 20,000 foot level anyway - my
overall
As for further punishment, I unloaded via synaptic the old 2.16.19 version
and gave it a go with Ronal's idea of using the sickylife.ppa load out.
After cleaning, I loaded the ppa and installed - no problems - no errors.
3.7 still force closes on touching the files. Unload it, remove PPA,
Hi,
Thanks for the suggestions and some more definitions about QIF and CSV
importers. Bottom line for me on my LM 19.2, other than the QIF importer
none of the other techniques work on my Win or Linux machines. On my linux
box, the program itself did not work although I did get a clean cmake
> On Sep 25, 2019, at 3:19 PM, dmeece wrote:
>
> After a huge effort to install Gnucash 3.7 on a Win 10 machine and then on a
> production build (no errors- all dependencies met) of Gnucash 3.7 from
> tarball on a Linux box, I failed to get a working program. I was able to
> load GnuCash3.7
I've experienced 3.7 crashing to the desktop when attempting to insert
text into a journal transaction, no .csv imports involved.
But, I'm running Ubuntu 19.10 (pre-beta) and got 3.7 from the
sicklylife.ppa. Too many variables there to draw meaningful
conclusions.
The crashes weren't consistent,
Also there seems to be confusion.
CSV files and QIF files are quite different, and both have dedicated
importers.
Both may slow with large numbers of transactions to import, hence it's
always safer to import in chunks. Which ones are not functioning?
On Thu, 26 Sep 2019 at 09:06, dmeece wrote:
What is the source of your import files? Once the data in in a data file
it stays there and can be read by the next GnuCash release similar to a
document that can be read by a document editor. The import process would
only be a one-time thing.
David Carlson
On Thu, Sep 26, 2019 at 4:58 AM
This is unfortunate. Perhaps you could anonymize a sample qif file which
fails and attach into a bug report ? It's plain text, so easy to modify.
On Thu, 26 Sep 2019, 17:06 dmeece, wrote:
> After a huge effort to install Gnucash 3.7 on a Win 10 machine and then on
> a
> production build (no
After a huge effort to install Gnucash 3.7 on a Win 10 machine and then on a
production build (no errors- all dependencies met) of Gnucash 3.7 from
tarball on a Linux box, I failed to get a working program. I was able to
load GnuCash3.7 in the Win 10 box with Qif files that numbered over a
20 matches
Mail list logo
