OK. I understand that deleting the guile-2.0 libs is what fixed the problem. If 
you’re sure that there were no pre-compiled guile (foo.go) files left over from 
Ubuntu 14.04 then all that’s left is a serious bug in guile-2.2 that loads both 
the guile-2.0 and guile-2.2 ice-9 modules. That’s for the Guile guys to sort 
out, but distros could work around it by not allowing both to be installed.

Regards,
John Ralls


> On Oct 25, 2018, at 7:23 AM, Colin Law <clan...@gmail.com> wrote:
> 
> Not sure if there is a confusion here, it wasn't the cache that caused the 
> problem, I tried deleting the cache and it didn't help.  I had to uninstall 
> guile-2.0-libs to fix it.
> 
> Colin
> 
> On Thu, 25 Oct 2018 at 15:12, John Ralls <jra...@ceridwen.us 
> <mailto:jra...@ceridwen.us>> wrote:
> On the second machine you might try uninstalling GnuCash before doing the 
> upgrade, then check /usr/lib/gnucash/scm/ccache to make sure it has been 
> removed. (That path might be off a bit, I don’t remember if Ubuntu uses 
> /usr/lib/gnu-linux-x86_64/ or does its own /usr/lib specialization.)
> 
> You might also make sure that there’s no /home/colin/.caches/guile/2.0/ccache.
> 
> Regards,
> John Ralls
> 
> 
>> On Oct 25, 2018, at 1:06 AM, Colin Law <clan...@gmail.com 
>> <mailto:clan...@gmail.com>> wrote:
>> 
>> This was an Ubuntu 18.04 machine with 2.16.9 installed from the Ubuntu repo. 
>> I upgraded the machine to Ubuntu 18.10 and GC got upgraded to 3.3 from the 
>> repo.  The machine has a long history however so it is not possible to say 
>> how the guile libs were installed.
>> 
>> I do have another machine still running Ubuntu 18.04 and GC 2.6.19 and I see 
>> it has guile-2.0 installed and not guile-2.2.  I will be upgrading that one 
>> once I am happy that Ubuntu 18.10 does not have any major problems.
>> 
>> Colin
>> 
>> On Thu, 25 Oct 2018 at 01:10, John Ralls <jra...@ceridwen.us 
>> <mailto:jra...@ceridwen.us>> wrote:
>> Good detective work.
>> 
>> Guile is supposed to be able to handle having multiple versions installed 
>> and to link the right libraries, but I suppose if you had guile-2.0-compiled 
>> files in a guile cache and guile-2.2-compiled ones installed by the .deb it 
>> might get confused. Was this a clean install of Ubuntu or were you upgrading 
>> and using a GnuCash you’d built yourself before upgrading?
>> 
>> Regards,
>> John Ralls
>> 
>> 
>> > On Oct 24, 2018, at 9:40 AM, Colin Law <clan...@gmail.com 
>> > <mailto:clan...@gmail.com>> wrote:
>> > 
>> > Yes, that was the issue (two versions of boot-9.scm).  Having checked
>> > dependencies and so on, including doing a dry run remove to check it wasn't
>> > going to remove anything critical,  I uninstalled guile-2.0-libs and now it
>> > runs ok.
>> > 
>> > So is this a packaging bug?
>> > 
>> > Colin
>> > 
>> > On Wed, 24 Oct 2018 at 16:39, Colin Law <clan...@gmail.com 
>> > <mailto:clan...@gmail.com>> wrote:
>> > 
>> >> Further to this I see I have two files ice-9/boot-9.scm
>> >> /usr/share/guile/2.2/ice-9/boot-9.scm
>> >> /usr/share/guile/2.0/ice-9/boot-9.scm
>> >> Could it be picking up the wrong one, or is that a red herring?
>> >> 
>> >> Colin
>> >> 
>> >> On Wed, 24 Oct 2018 at 15:57, Colin Law <clan...@gmail.com 
>> >> <mailto:clan...@gmail.com>> wrote:
>> >> 
>> >>> Just upgraded my Ubuntu 18.04 to 18.10.  This upgraded GC from 2.6.19 (at
>> >>> least I think it was 19) to 3.3 and now GC crashes immediately on 
>> >>> startup.
>> >>> Starting in a terminal gives result below.  There is nothing in the trace
>> >>> file.  On another machine with a fresh install of 18.10 GC 3.3 runs fine 
>> >>> so
>> >>> I guess it is to with updated file locations or something.
>> >>> 
>> >>> Colin
>> >>> 
>> >>> $ gnucash
>> >>> Backtrace:
>> >>> In ice-9/boot-9.scm:
>> >>>  2994:20 19 (_)
>> >>>   2312:4 18 (save-module-excursion _)
>> >>>  3014:26 17 (_)
>> >>> In unknown file:
>> >>>          16 (primitive-load-path "gnucash/utilities" #<procedure 55…>)
>> >>> In utilities.scm:
>> >>>     28:0 15 (_)
>> >>> In ice-9/boot-9.scm:
>> >>>  3377:20 14 (process-use-modules _)
>> >>>   222:17 13 (map1 (((gnucash core-utils))))
>> >>>  3378:31 12 (_ ((gnucash core-utils)))
>> >>>  2800:17 11 (resolve-interface (gnucash core-utils) #:select _ # _ # …)
>> >>> In ice-9/threads.scm:
>> >>>    390:8 10 (_ _)
>> >>> In ice-9/boot-9.scm:
>> >>>  2726:13  9 (_)
>> >>> In ice-9/threads.scm:
>> >>>    390:8  8 (_ _)
>> >>> In ice-9/boot-9.scm:
>> >>>  2994:20  7 (_)
>> >>>   2312:4  6 (save-module-excursion _)
>> >>>  3014:26  5 (_)
>> >>> In unknown file:
>> >>>           4 (primitive-load-path "gnucash/core-utils" #<procedure 5…>)
>> >>> In core-utils.scm:
>> >>>     40:0  3 (_)
>> >>> In ice-9/boot-9.scm:
>> >>>  2071:24  2 (call-with-deferred-observers #<procedure 7f649fe8c2b8 …>)
>> >>>   260:13  1 (for-each #<procedure 55f6e50dd4e0 at ice-9/boot-9.scm…> …)
>> >>> In unknown file:
>> >>>           0 (scm-error misc-error #f "~A ~S" ("Undefined variab…" …) …)
>> >>> 
>> >>> ERROR: In procedure scm-error:
>> >>> Undefined variable: gnc-build-userdata-path
>> >>> 
>> >>> 
>> > _______________________________________________
>> > gnucash-user mailing list
>> > gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org>
>> > To update your subscription preferences or to unsubscribe:
>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user 
>> > <https://lists.gnucash.org/mailman/listinfo/gnucash-user>
>> > If you are using Nabble or Gmane, please see 
>> > https://wiki.gnucash.org/wiki/Mailing_Lists 
>> > <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.

Reply via email to