On Thu, Apr 23, 2020 at 9:42 PM Jean-Florent Raymond
<j-florent.raym...@uca.fr> wrote:
>
> Hello,
>
> Did you try to rebuild since the upgrade?
> If you upgraded a package that sage needs, then sage might complain that
> it cannot find the version it was used to.
>
> It seems to be the case with libntl according to the crash report you
> attached:
> ImportError: libntl.so.35: cannot open shared object file: No such file
> or directory

indeed, this is to be expected - an OS update updates libraries your
application is built against, and so
it needs to be re-linked.


>
>
>
> Le 23/04/2020 à 15:10, Soufiane Lakhlifi a écrit :
> > Hello,
> >
> > Here is the report of a crash that happened while trying to lunch sage:
> >
> > -Operating system: Ubuntu 20.04 beta, upgraded from 19.10.
> > -Sage (8.9) was build  from the source under Ubuntu 19.10 and by following
> >  the instructions in this page
> > http://doc.sagemath.org/html/en/installation/source.html.
> >  No special flags were used except to change the build directory.
> > -The crash happened by lunching sage (with no arguments) from the terminal,
> >  it is worth noting that the crash happened just after I upgraded my Ubuntu
> > from
> >  19.10 to 20.10.
> >
> > Best regards,
> > Soufiane Lakhlifi.
> > Zone contenant les pièces jointes
> >
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-support+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/31ae06a6-0ace-d577-6d46-ce5e16ca7073%40uca.fr.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAAWYfq1tie20oSyrJXs3ddSzVfRE-UvaDg7TKWci8CX0ENL1Zg%40mail.gmail.com.

Reply via email to