Re: [sage-support] Re: Sage Crash Report

[Isuru Fernando]

This is an ABI incompatibility with clang 14 and 15 where givaro was
compiled with 14 and sage was compiled with 15.
I suggest downgrading to clang 14 or set flags like
https://github.com/conda-forge/sagelib-feedstock/blob/5542b278f642b772ae243b323c7cbc7a170a5f9a/recipe/build.sh#L21-L25
until we rebuild givaro with clang 15.

Isuru

On Wed, May 31, 2023 at 2:01 PM Matthias Goerner  wrote:

> I am focusing on the Sage 9.8 issue of the missing symbol
> __ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNSC_8RandIterENS_19FFPACK_CHARPOLY_TAGEm
>
> Demangled with c++filt, the missing symbol is:
> Givaro::Poly1Dom,
> Givaro::Dense>::Element&
> FFPACK::CharPoly,
> Givaro::Dense> >(Givaro::Poly1Dom,
> Givaro::Dense> const&, Givaro::Poly1Dom void>, Givaro::Dense>::Element&, unsigned long,
> Givaro::Poly1Dom,
> Givaro::Dense>::Domain_t::Element_ptr, unsigned long,
> Givaro::Poly1Dom,
> Givaro::Dense>::Domain_t::RandIter&, FFPACK::FFPACK_CHARPOLY_TAG, unsigned
> long)
>
> I expect this to be in ffpack, so I made sure that ffpack is indeed picked
> up from the dedicated conda environment:
>
> lsof -p 70202 | grep -i ffpack
> python3.1 70202 matthias  txt  REG   1,15  1132624 5917685
> /Users/matthias/anaconda3/envs/sage98-py311/lib/libffpack.1.dylib
>
> I then looked whether similar symbols are available in ffpack with the
> following command:
> nm /Users/matthias/anaconda3/envs/sage98-py311/lib/libffpack.1.dylib |
> grep
> __ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEm
>
> Which gave:
> 0004f17c T
> __ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmNS_19FFPACK_CHARPOLY_TAGEm
> 0004ec10 T
> __ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNS7_8Domain_t8RandIterENS_19FFPACK_CHARPOLY_TAGEm
>
> which demangled gives:
> Givaro::Poly1Dom,
> Givaro::Dense>::Element&
> FFPACK::CharPoly,
> Givaro::Dense> >(Givaro::Poly1Dom,
> Givaro::Dense> const&, Givaro::Poly1Dom void>, Givaro::Dense>::Element&, unsigned long,
> Givaro::Poly1Dom,
> Givaro::Dense>::Domain_t::Element_ptr, unsigned long,
> FFPACK::FFPACK_CHARPOLY_TAG, unsigned long)
> Givaro::Poly1Dom,
> Givaro::Dense>::Element&
> FFPACK::CharPoly,
> Givaro::Dense> >(Givaro::Poly1Dom,
> Givaro::Dense> const&, Givaro::Poly1Dom void>, Givaro::Dense>::Element&, unsigned long,
> Givaro::Poly1Dom,
> Givaro::Dense>::Domain_t::Element_ptr, unsigned long,
> Givaro::Poly1Dom,
> Givaro::Dense>::Domain_t::RandIter&, FFPACK::FFPACK_CHARPOLY_TAG, unsigned
> long)
>
> And then I got confused: the latter demangled method has the same
> signature as the missing one.
>
> In other words: from a C++ perspective, the missing method is there, it is
> just that the way the name and signature get mangled is different between
> linbox_flint_interface.cpython-311-darwin.so and libffpack.1.dylib
>
> So it seems it is an ABI problem where we get two different managled names
> for the same function signature.
>
> I am not sure what to make out of this and have only two explanations:
> 1. It is a bug in the C++ compiler.
> 2. The two libraries were compiled with different C++ compilers or with
> different compiler options.
>
> On Wednesday, May 31, 2023 at 11:01:20 AM UTC-7 Matthias Goerner wrote:
>
> Sorry for the late reply. Here are the details about my conda environment.
> I am not exactly sure what other information is useful to debug this. I am
> familiar with the linux tools, but am struggling with otool and vmmap to
> figure out what is going on here and see whether I am picking up any
> library from something that is not in the dedicated conda environment.
>
> On Friday, May 26, 2023 at 8:05:04 AM UTC-7 Matthias Koeppe wrote:
>
> config.log please
>
> On Wednesday, May 24, 2023 at 3:16:25 PM UTC-7 Matthias Goerner wrote:
>
> Hi!
>
> I can't get sage to work when installing it with conda on a new MacBook
> Pro with M2 chip and Ventura 13.3.
>
> I tried
> conda -n sage create sage=9.X python=3.Y
> for (X,Y) = (5,10), (8,10), (8,11).
> With Sage 9.5, I get the attached crash report.
> With Sage 9.8, I get the following linking error below.
>
> Cheers,
> Matthias
>
> (sage-py310) matthias@matthiass-air-2 ~ % sage
> ┌┐
> │ SageMath version 9.8, Release Date: 2023-02-11 │
> │ Using Python 3.10.11. Type "help()" for help.  │
> └┘
> ┏┓
> ┃ Warning: sage.all is not available; this is a limited REPL.┃
> ┗┛
> sage: import sage.all
> 

[sage-support] Re: Sage Crash Report

[Matthias Goerner]

I am focusing on the Sage 9.8 issue of the missing symbol 
__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNSC_8RandIterENS_19FFPACK_CHARPOLY_TAGEm

Demangled with c++filt, the missing symbol is:
Givaro::Poly1Dom, 
Givaro::Dense>::Element& 
FFPACK::CharPoly, 
Givaro::Dense> >(Givaro::Poly1Dom, 
Givaro::Dense> const&, Givaro::Poly1Dom, Givaro::Dense>::Element&, unsigned long, 
Givaro::Poly1Dom, 
Givaro::Dense>::Domain_t::Element_ptr, unsigned long, 
Givaro::Poly1Dom, 
Givaro::Dense>::Domain_t::RandIter&, FFPACK::FFPACK_CHARPOLY_TAG, unsigned 
long)

I expect this to be in ffpack, so I made sure that ffpack is indeed picked 
up from the dedicated conda environment:

lsof -p 70202 | grep -i ffpack
python3.1 70202 matthias  txt  REG   1,15  1132624 5917685 
/Users/matthias/anaconda3/envs/sage98-py311/lib/libffpack.1.dylib

I then looked whether similar symbols are available in ffpack with the 
following command:
nm /Users/matthias/anaconda3/envs/sage98-py311/lib/libffpack.1.dylib | grep 
__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEm

Which gave:
0004f17c T 
__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmNS_19FFPACK_CHARPOLY_TAGEm
0004ec10 T 
__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNS7_8Domain_t8RandIterENS_19FFPACK_CHARPOLY_TAGEm

which demangled gives:
Givaro::Poly1Dom, 
Givaro::Dense>::Element& 
FFPACK::CharPoly, 
Givaro::Dense> >(Givaro::Poly1Dom, 
Givaro::Dense> const&, Givaro::Poly1Dom, Givaro::Dense>::Element&, unsigned long, 
Givaro::Poly1Dom, 
Givaro::Dense>::Domain_t::Element_ptr, unsigned long, 
FFPACK::FFPACK_CHARPOLY_TAG, unsigned long)
Givaro::Poly1Dom, 
Givaro::Dense>::Element& 
FFPACK::CharPoly, 
Givaro::Dense> >(Givaro::Poly1Dom, 
Givaro::Dense> const&, Givaro::Poly1Dom, Givaro::Dense>::Element&, unsigned long, 
Givaro::Poly1Dom, 
Givaro::Dense>::Domain_t::Element_ptr, unsigned long, 
Givaro::Poly1Dom, 
Givaro::Dense>::Domain_t::RandIter&, FFPACK::FFPACK_CHARPOLY_TAG, unsigned 
long)

And then I got confused: the latter demangled method has the same signature 
as the missing one.

In other words: from a C++ perspective, the missing method is there, it is 
just that the way the name and signature get mangled is different 
between linbox_flint_interface.cpython-311-darwin.so and libffpack.1.dylib

So it seems it is an ABI problem where we get two different managled names 
for the same function signature.

I am not sure what to make out of this and have only two explanations:
1. It is a bug in the C++ compiler.
2. The two libraries were compiled with different C++ compilers or with 
different compiler options.

On Wednesday, May 31, 2023 at 11:01:20 AM UTC-7 Matthias Goerner wrote:

Sorry for the late reply. Here are the details about my conda environment. 
I am not exactly sure what other information is useful to debug this. I am 
familiar with the linux tools, but am struggling with otool and vmmap to 
figure out what is going on here and see whether I am picking up any 
library from something that is not in the dedicated conda environment.

On Friday, May 26, 2023 at 8:05:04 AM UTC-7 Matthias Koeppe wrote:

config.log please

On Wednesday, May 24, 2023 at 3:16:25 PM UTC-7 Matthias Goerner wrote:

Hi!

I can't get sage to work when installing it with conda on a new MacBook Pro 
with M2 chip and Ventura 13.3.

I tried
conda -n sage create sage=9.X python=3.Y
for (X,Y) = (5,10), (8,10), (8,11).
With Sage 9.5, I get the attached crash report.
With Sage 9.8, I get the following linking error below.

Cheers,
Matthias

(sage-py310) matthias@matthiass-air-2 ~ % sage
┌┐
│ SageMath version 9.8, Release Date: 2023-02-11 │
│ Using Python 3.10.11. Type "help()" for help.  │
└┘
┏┓
┃ Warning: sage.all is not available; this is a limited REPL.┃
┗┛
sage: import sage.all
---
ImportError   Traceback (most recent call last)
Cell In[1], line 1
> 1 import sage.all

File 
~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/all.py:168
166 from sage.modules.allimport *
167 from sage.monoids.allimport *
--> 168 from sage.algebras.all   import *
169 from sage.modular.allimport *
170 from sage.sat.allimport *

File 
~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/all.py:21
  5 

[sage-support] Re: Sage Crash Report

[Matthias Goerner]

Sorry for the late reply. Here are the details about my conda environment. 
I am not exactly sure what other information is useful to debug this. I am 
familiar with the linux tools, but am struggling with otool and vmmap to 
figure out what is going on here and see whether I am picking up any 
library from something that is not in the dedicated conda environment.

On Friday, May 26, 2023 at 8:05:04 AM UTC-7 Matthias Koeppe wrote:

> config.log please
>
> On Wednesday, May 24, 2023 at 3:16:25 PM UTC-7 Matthias Goerner wrote:
>
>> Hi!
>>
>> I can't get sage to work when installing it with conda on a new MacBook 
>> Pro with M2 chip and Ventura 13.3.
>>
>> I tried
>> conda -n sage create sage=9.X python=3.Y
>> for (X,Y) = (5,10), (8,10), (8,11).
>> With Sage 9.5, I get the attached crash report.
>> With Sage 9.8, I get the following linking error below.
>>
>> Cheers,
>> Matthias
>>
>> (sage-py310) matthias@matthiass-air-2 ~ % sage
>> ┌┐
>> │ SageMath version 9.8, Release Date: 2023-02-11 │
>> │ Using Python 3.10.11. Type "help()" for help.  │
>> └┘
>> ┏┓
>> ┃ Warning: sage.all is not available; this is a limited REPL.┃
>> ┗┛
>> sage: import sage.all
>>
>> ---
>> ImportError   Traceback (most recent call 
>> last)
>> Cell In[1], line 1
>> > 1 import sage.all
>>
>> File 
>> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/all.py:168
>> 166 from sage.modules.allimport *
>> 167 from sage.monoids.allimport *
>> --> 168 from sage.algebras.all   import *
>> 169 from sage.modular.allimport *
>> 170 from sage.sat.allimport *
>>
>> File 
>> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/all.py:21
>>   5 
>> #*
>>   6 #   Copyright (C) 2005 William Stein 
>>   7 #
>>(...)
>>  17 #  http://www.gnu.org/licenses/
>>  18 
>> #*
>>  19 from sage.misc.lazy_import import lazy_import
>> ---> 21 import sage.algebras.catalog as algebras
>>  23 from .quatalg.all import *
>>  24 from .steenrod.all import *
>>
>> File 
>> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/catalog.py:84
>>   1 r"""
>>   2 Catalog of Algebras
>>   3
>>(...)
>>  80   `
>>  81 """
>>  83 from sage.algebras.free_algebra import FreeAlgebra as Free
>> ---> 84 from sage.algebras.quatalg.quaternion_algebra import 
>> QuaternionAlgebra as Quaternion
>>  85 from sage.algebras.steenrod.steenrod_algebra import 
>> SteenrodAlgebra as Steenrod
>>  86 from 
>> sage.algebras.finite_dimensional_algebras.finite_dimensional_algebra import 
>> FiniteDimensionalAlgebra as FiniteDimensional
>>
>> File 
>> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra.py:68
>>  61 from operator import itemgetter
>>  63 from .quaternion_algebra_element import (
>>  64 QuaternionAlgebraElement_abstract,
>>  65 QuaternionAlgebraElement_generic,
>>  66 QuaternionAlgebraElement_rational_field,
>>  67 QuaternionAlgebraElement_number_field)
>> ---> 68 from . import quaternion_algebra_cython
>>  70 from sage.modular.modsym.p1list import P1List
>>  72 from sage.misc.cachefunc import cached_method
>>
>> File 
>> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra_cython.pyx:1,
>>  
>> in init sage.algebras.quatalg.quaternion_algebra_cython 
>> (build/cythonized/sage/algebras/quatalg/quaternion_algebra_cython.cpp:6484)()
>> > 1 # distutils: language = c++
>>   2 # distutils: libraries = gmp m NTL_LIBRARIES
>>   3 # distutils: extra_compile_args = NTL_CFLAGS
>>
>> File 
>> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/matrix/matrix_integer_dense.pyx:1,
>>  
>> in init sage.matrix.matrix_integer_dense 
>> (build/cythonized/sage/matrix/matrix_integer_dense.cpp:59322)()
>> > 1 # -*- coding: utf-8 -*-
>>   2 # distutils: extra_compile_args = NTL_CFLAGS M4RI_CFLAGS
>>   3 # distutils: libraries = iml NTL_LIBRARIES gmp m CBLAS_LIBRARIES
>>
>> ImportError: 
>> dlopen(/Users/matthias/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/libs/linbox/
>> linbox_flint_interface.cpython-310-darwin.so, 0x0002): symbol not found 
>> in flat namespace 
>> 

[sage-support] Re: Sage Crash Report

[Matthias Koeppe]

config.log please

On Wednesday, May 24, 2023 at 3:16:25 PM UTC-7 Matthias Goerner wrote:

> Hi!
>
> I can't get sage to work when installing it with conda on a new MacBook 
> Pro with M2 chip and Ventura 13.3.
>
> I tried
> conda -n sage create sage=9.X python=3.Y
> for (X,Y) = (5,10), (8,10), (8,11).
> With Sage 9.5, I get the attached crash report.
> With Sage 9.8, I get the following linking error below.
>
> Cheers,
> Matthias
>
> (sage-py310) matthias@matthiass-air-2 ~ % sage
> ┌┐
> │ SageMath version 9.8, Release Date: 2023-02-11 │
> │ Using Python 3.10.11. Type "help()" for help.  │
> └┘
> ┏┓
> ┃ Warning: sage.all is not available; this is a limited REPL.┃
> ┗┛
> sage: import sage.all
> ---
> ImportError   Traceback (most recent call last)
> Cell In[1], line 1
> > 1 import sage.all
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/all.py:168
> 166 from sage.modules.allimport *
> 167 from sage.monoids.allimport *
> --> 168 from sage.algebras.all   import *
> 169 from sage.modular.allimport *
> 170 from sage.sat.allimport *
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/all.py:21
>   5 
> #*
>   6 #   Copyright (C) 2005 William Stein 
>   7 #
>(...)
>  17 #  http://www.gnu.org/licenses/
>  18 
> #*
>  19 from sage.misc.lazy_import import lazy_import
> ---> 21 import sage.algebras.catalog as algebras
>  23 from .quatalg.all import *
>  24 from .steenrod.all import *
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/catalog.py:84
>   1 r"""
>   2 Catalog of Algebras
>   3
>(...)
>  80   `
>  81 """
>  83 from sage.algebras.free_algebra import FreeAlgebra as Free
> ---> 84 from sage.algebras.quatalg.quaternion_algebra import 
> QuaternionAlgebra as Quaternion
>  85 from sage.algebras.steenrod.steenrod_algebra import 
> SteenrodAlgebra as Steenrod
>  86 from 
> sage.algebras.finite_dimensional_algebras.finite_dimensional_algebra import 
> FiniteDimensionalAlgebra as FiniteDimensional
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra.py:68
>  61 from operator import itemgetter
>  63 from .quaternion_algebra_element import (
>  64 QuaternionAlgebraElement_abstract,
>  65 QuaternionAlgebraElement_generic,
>  66 QuaternionAlgebraElement_rational_field,
>  67 QuaternionAlgebraElement_number_field)
> ---> 68 from . import quaternion_algebra_cython
>  70 from sage.modular.modsym.p1list import P1List
>  72 from sage.misc.cachefunc import cached_method
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra_cython.pyx:1,
>  
> in init sage.algebras.quatalg.quaternion_algebra_cython 
> (build/cythonized/sage/algebras/quatalg/quaternion_algebra_cython.cpp:6484)()
> > 1 # distutils: language = c++
>   2 # distutils: libraries = gmp m NTL_LIBRARIES
>   3 # distutils: extra_compile_args = NTL_CFLAGS
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/matrix/matrix_integer_dense.pyx:1,
>  
> in init sage.matrix.matrix_integer_dense 
> (build/cythonized/sage/matrix/matrix_integer_dense.cpp:59322)()
> > 1 # -*- coding: utf-8 -*-
>   2 # distutils: extra_compile_args = NTL_CFLAGS M4RI_CFLAGS
>   3 # distutils: libraries = iml NTL_LIBRARIES gmp m CBLAS_LIBRARIES
>
> ImportError: 
> dlopen(/Users/matthias/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/libs/linbox/
> linbox_flint_interface.cpython-310-darwin.so, 0x0002): symbol not found 
> in flat namespace 
> '__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNSC_8RandIterENS_19FFPACK_CHARPOLY_TAGEm'
>

-- 
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/8654bcee-0e10-49f5-842e-42b49cacde0bn%40googlegroups.com.

[sage-support] Re: Sage Crash Report

[Matthias Goerner]

9.7 with python 3.10 seems to work on Ventura 13.3 on a M2.

On Wed, May 24, 2023 at 3:16 PM Matthias Goerner  wrote:

> Hi!
>
> I can't get sage to work when installing it with conda on a new MacBook
> Pro with M2 chip and Ventura 13.3.
>
> I tried
> conda -n sage create sage=9.X python=3.Y
> for (X,Y) = (5,10), (8,10), (8,11).
> With Sage 9.5, I get the attached crash report.
> With Sage 9.8, I get the following linking error below.
>
> Cheers,
> Matthias
>
> (sage-py310) matthias@matthiass-air-2 ~ % sage
> ┌┐
> │ SageMath version 9.8, Release Date: 2023-02-11 │
> │ Using Python 3.10.11. Type "help()" for help.  │
> └┘
> ┏┓
> ┃ Warning: sage.all is not available; this is a limited REPL.┃
> ┗┛
> sage: import sage.all
> ---
> ImportError   Traceback (most recent call last)
> Cell In[1], line 1
> > 1 import sage.all
>
> File
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/all.py:168
> 166 from sage.modules.allimport *
> 167 from sage.monoids.allimport *
> --> 168 from sage.algebras.all   import *
> 169 from sage.modular.allimport *
> 170 from sage.sat.allimport *
>
> File
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/all.py:21
>   5
> #*
>   6 #   Copyright (C) 2005 William Stein 
>   7 #
>(...)
>  17 #  http://www.gnu.org/licenses/
>  18
> #*
>  19 from sage.misc.lazy_import import lazy_import
> ---> 21 import sage.algebras.catalog as algebras
>  23 from .quatalg.all import *
>  24 from .steenrod.all import *
>
> File
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/catalog.py:84
>   1 r"""
>   2 Catalog of Algebras
>   3
>(...)
>  80   `
>  81 """
>  83 from sage.algebras.free_algebra import FreeAlgebra as Free
> ---> 84 from sage.algebras.quatalg.quaternion_algebra import
> QuaternionAlgebra as Quaternion
>  85 from sage.algebras.steenrod.steenrod_algebra import
> SteenrodAlgebra as Steenrod
>  86 from
> sage.algebras.finite_dimensional_algebras.finite_dimensional_algebra import
> FiniteDimensionalAlgebra as FiniteDimensional
>
> File
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra.py:68
>  61 from operator import itemgetter
>  63 from .quaternion_algebra_element import (
>  64 QuaternionAlgebraElement_abstract,
>  65 QuaternionAlgebraElement_generic,
>  66 QuaternionAlgebraElement_rational_field,
>  67 QuaternionAlgebraElement_number_field)
> ---> 68 from . import quaternion_algebra_cython
>  70 from sage.modular.modsym.p1list import P1List
>  72 from sage.misc.cachefunc import cached_method
>
> File
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra_cython.pyx:1,
> in init sage.algebras.quatalg.quaternion_algebra_cython
> (build/cythonized/sage/algebras/quatalg/quaternion_algebra_cython.cpp:6484)()
> > 1 # distutils: language = c++
>   2 # distutils: libraries = gmp m NTL_LIBRARIES
>   3 # distutils: extra_compile_args = NTL_CFLAGS
>
> File
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/matrix/matrix_integer_dense.pyx:1,
> in init sage.matrix.matrix_integer_dense
> (build/cythonized/sage/matrix/matrix_integer_dense.cpp:59322)()
> > 1 # -*- coding: utf-8 -*-
>   2 # distutils: extra_compile_args = NTL_CFLAGS M4RI_CFLAGS
>   3 # distutils: libraries = iml NTL_LIBRARIES gmp m CBLAS_LIBRARIES
>
> ImportError:
> dlopen(/Users/matthias/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/libs/linbox/
> linbox_flint_interface.cpython-310-darwin.so, 0x0002): symbol not found
> in flat namespace
> '__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNSC_8RandIterENS_19FFPACK_CHARPOLY_TAGEm'
>

-- 
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/CALB88e_PNuw90EAx82nPA21EJakeRFQFEsYvKLBNpVi72OgGjA%40mail.gmail.com.

[sage-support] Re: Sage Crash Report

[domingo.domingogo...@gmail.com]

That was the problem. I copy the files and now everything works.

Many thanks for spotting the problem.

On Saturday, 30 July 2022 at 15:25:54 UTC+2 Marc Culler wrote:

> The reason it works for one user and not for the other is because 
> libgsl.25.dylib 
> exists within one user's.conda/envs/sage/lib directory but it does not 
> exist within the other user's .conda/envs/sage/lib directory.
>
> On Saturday, July 30, 2022 at 4:53:36 AM UTC-5 domingo.do...@gmail.com 
> wrote:
>
>> Dear Developers,
>>
>> I am using a MacOs Monterrey v.12.4 on a chip M2.
>> Sage was install using anaconda, with mamba.
>>
>> The funny thing is that I install in two different accounts, one 
>> administrator and one regular user.
>> Sage conda environment in the administrator account works fine. 
>> In the regular user account it crash.
>> The command that triggers the crash are: mamba activate sage && sage
>>
>

-- 
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/e1040d2f-370e-4810-a1ea-61fee9925ef6n%40googlegroups.com.

[sage-support] Re: Sage Crash Report

[Marc Culler]

The reason it works for one user and not for the other is because 
libgsl.25.dylib 
exists within one user's.conda/envs/sage/lib directory but it does not 
exist within the other user's .conda/envs/sage/lib directory.

On Saturday, July 30, 2022 at 4:53:36 AM UTC-5 
domingo.domingogo...@gmail.com wrote:

> Dear Developers,
>
> I am using a MacOs Monterrey v.12.4 on a chip M2.
> Sage was install using anaconda, with mamba.
>
> The funny thing is that I install in two different accounts, one 
> administrator and one regular user.
> Sage conda environment in the administrator account works fine. 
> In the regular user account it crash.
> The command that triggers the crash are: mamba activate sage && sage
>

-- 
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/803fc3b4-232d-4f42-9fba-c4a022fe7d67n%40googlegroups.com.

[sage-support] Re: Sage Crash Report. -- help please !

[Bharathwaj Palvannan]

Hi, 

Thank you, everyone. Sorry for my late response: I wasn't sure how things 
worked and I hadn't realized that I needed to check the google groups page. 

I managed to install Sage on my laptop, but I am not really sure what 
worked. It was just a lot of trial and error and going through the ASKSAGE 
StackExchange. Honestly, I don't think I would be able to repeat the 
successful installation again. 

If I remember correctly, the instructions given here
 https://doc.sagemath.org/html/en/installation/conda.html
really helped. And this seems to match the suggestion of Samuel Lelièvre. 
Thank you! 

Regarding my 2017 question, it was not answered, but I don't remember the 
motivation behind that question anymore, so in a way it's okay now! 

Thanks again. 

On Friday, March 4, 2022 at 6:38:02 PM UTC+5:30 Marc Culler wrote:

> In case this problem has not been addressed ... at the bottom of your 
> crash report it says:
> '/usr/lib/libgfortran.5.dylib' (no such file)
>
> That means that you are using an early prelease version of the SageMath 
> app for M1 systems.  This problem was fixed in the release version.  So 
> just download and installing the dmg file for the released version will 
> prevent this crash.
>
> - Marc 
>
> On Tuesday, February 15, 2022 at 8:43:20 PM UTC-6 Bharathwaj Palvannan 
> wrote:
>
>> Hi, 
>>
>>  
>>
>> Please help me! I am unable to get Sagemath working and I really don’t 
>> know what’s happening. I recently got a new laptop. This is a macOS 
>> operating system (Version 12.1 Monterey). I installed SageMath using the 
>> dmg file on the Sagemath website. I had already sent a crash report some 
>> weeks ago but I received no response. I literally just typed in sage on the 
>> mac terminal and the app crashed. 
>>
>>  
>>
>> Thank you.
>>
>> Best regards
>>
>>  
>>
>>  
>>
>

-- 
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/a81501f1-f225-4c69-b16e-c22d4a1e5c93n%40googlegroups.com.

[sage-support] Re: Sage Crash Report. -- help please !

[Marc Culler]

In case this problem has not been addressed ... at the bottom of your crash 
report it says:
'/usr/lib/libgfortran.5.dylib' (no such file)

That means that you are using an early prelease version of the SageMath app 
for M1 systems.  This problem was fixed in the release version.  So just 
download and installing the dmg file for the released version will prevent 
this crash.

- Marc 

On Tuesday, February 15, 2022 at 8:43:20 PM UTC-6 Bharathwaj Palvannan 
wrote:

> Hi, 
>
>  
>
> Please help me! I am unable to get Sagemath working and I really don’t 
> know what’s happening. I recently got a new laptop. This is a macOS 
> operating system (Version 12.1 Monterey). I installed SageMath using the 
> dmg file on the Sagemath website. I had already sent a crash report some 
> weeks ago but I received no response. I literally just typed in sage on the 
> mac terminal and the app crashed. 
>
>  
>
> Thank you.
>
> Best regards
>
>  
>
>  
>

-- 
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/f7b63087-0f67-4450-88e6-d806170bbefdn%40googlegroups.com.

[sage-support] Re: Sage Crash Report. -- help please !

[slelievre]

2022-02-16, 02:43:20 UTC, Bharathwaj Palvannan:

> I had already sent a crash report some weeks ago
> but I received no response.

This question of yours from 2017 was not answered:

  https://groups.google.com/g/sage-support/c/0dgWgFGxYQU

(hopefully you managed to solve that problem since then?)
but for your recent crash report there were two responses:

https://groups.google.com/g/sage-support/c/BadgRDXNSbY 

To install Sage on your Mac, I suggest using the
"sagemath-forge" Conda distribution, following
the steps described here:

https://groups.google.com/g/sage-devel/c/NiP5jIfHusI/m/JDODj8lfAgAJ

-- 
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/a57c5f3c-5197-4bcf-aad2-431bd9acd77bn%40googlegroups.com.

[sage-support] Re: Sage Crash report (again...)

[Emmanuel Charpentier]

I’m in trouble:

The previous steps (make giac-clean && make fricas-clean && make 
sagelib-clean && make) failed ; I reverted to (make distclean && make) … 
which failed.

Repeatedly…

I’ll report and post logs in sage-release, which seems te “right place” for 
an installation problem occurring on a previously-working system.

Thank you for your attention.
​
Le samedi 18 décembre 2021 à 10:44:07 UTC+1, Emmanuel Charpentier a écrit :

> Same circumstances as in the previous case : on Debian testing running on 
> core i7 + 16 GB RAM, after upgrading Sage 9.5.beta7 compiled from a git 
> tree  to 9.5.beta8, Sage crashes at startup. Crash report enclosed
>
> I'll try the same steps as in the last occurrence...
>
> --
> Emmanuel Charpentier
>
>

-- 
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/a44974fb-75c1-4afa-a315-e90531c3f7edn%40googlegroups.com.

Re: [sage-support] Re: Sage crash report

[Emmanuel Charpentier]

Now, at the *end* of a Sage session, I get :

sage: quit
Exiting Sage (CPU time 0m5.63s, Wall time 97m53.10s).

/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/cysignals/signals.cpython-39-x86_64-linux-gnu.so(+0x7e1b)[0x7fe106cabe1b]
/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/cysignals/signals.cpython-39-x86_64-linux-gnu.so(+0x7ec9)[0x7fe106cabec9]
/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/cysignals/signals.cpython-39-x86_64-linux-gnu.so(+0xafa3)[0x7fe106caefa3]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x138e0)[0x7fe1099888e0]
/usr/lib/x86_64-linux-gnu/libflint-2.8.2.so(_fmpz_cleanup_mpz_content+0x6a)[0x7fe0b651279a]
/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/libs/flint/flint.cpython-39-x86_64-linux-gnu.so(+0x2e29)[0x7fe0a2a71e29]
python3[0x52326b]
python3(_PyEval_EvalFrameDefault+0x53d1)[0x5149c1]
python3[0x50e2d1]
python3(_PyFunction_Vectorcall+0x3db)[0x525f3b]
python3(_PyEval_EvalFrameDefault+0x53d1)[0x5149c1]
python3[0x50e2d1]
python3(_PyFunction_Vectorcall+0x3db)[0x525f3b]
python3[0x63a580]
python3[0x6287ad]
python3(Py_FinalizeEx+0x4d)[0x62841d]
python3(Py_RunMain+0x170)[0x61eff0]
python3(Py_BytesMain+0x29)[0x606df9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7fe1097d5e4a]
python3(_start+0x2a)[0x606cfa]

Attaching gdb to process id 174166.
Cannot find gdb installed
GDB is not installed.
Install gdb for enhanced tracebacks.

Unhandled SIGSEGV: A segmentation fault occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.

Segmentation fault

Both from a terminal session and from emacs‘s sage_shell_mode. I don’t see 
anything when I stop-and-close a Jupyter notebook.

Thoughts ?
​
Le vendredi 10 décembre 2021 à 16:39:53 UTC+1, Emmanuel Charpentier a 
écrit :

> make giac-clean && make did it !
>
> (*Alla cinese*) 10^4 thanks !
> ​
> Le vendredi 10 décembre 2021 à 11:56:00 UTC+1, dim...@gmail.com a écrit :
>
>> Everything that depends on updated Debian libs has to be rebuilt - looks 
>> like 
>>
>> make giac-clean 
>>
>> is needed too, for sure. 
>>
>> On Fri, Dec 10, 2021 at 10:36 AM Emmanuel Charpentier 
>>  wrote: 
>> > 
>> > 
>> > 
>> > Le vendredi 10 décembre 2021 à 01:04:33 UTC+1, Matthias Koeppe a écrit 
>> : 
>> >> 
>> >> "make sagelib-clean" will fix this 
>> > 
>> > 
>> > Nope. `make sagelib-clean` succeeds, but the following `make` fails at 
>> documentation ; attempting `make doc-clean && make also fails, *with the 
>> very same error*... : 
>> > 
>> > ``` 
>> > [sagemath_doc_html-none] cd /usr/local/sage-9 && ./sage --docbuild 
>> --no-pdf-links reference/libs inventory --no-prune-empty-dirs 
>> > [sagemath_doc_html-none] Warning: Could not import sage.libs.giac 
>> libgsl.so.25: cannot open shared object file: No such file or directory 
>> > [sagemath_doc_html-none] 
>> /usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py:1066:
>>  
>> DeprecationWarning: the module sage.libs.ratpoints is deprecated; use 
>> pari.ellratpoints or pari.hyperellratpoints instead 
>> > [sagemath_doc_html-none] See http://trac.sagemath.org/24531 for 
>> details. 
>> > [sagemath_doc_html-none] __import__(module_name) 
>> > [sagemath_doc_html-none] [libs ] building [inventory]: targets for 39 
>> source files that are out of date 
>> > [sagemath_doc_html-none] [libs ] updating environment: [new config] 39 
>> added, 0 changed, 0 removed 
>> > [sagemath_doc_html-none] [libs ] WARNING: autodoc: failed to import 
>> module 'giac' from module 'sage.libs'; the following exception was raised: 
>> > [sagemath_doc_html-none] [libs ] libgsl.so.25: cannot open shared 
>> object file: No such file or directory 
>> > [sagemath_doc_html-none] [libs ] The inventory files are in 
>> local/share/doc/sage/inventory/en/reference/libs. 
>> > [sagemath_doc_html-none] Error building the documentation. 
>> > [sagemath_doc_html-none] Traceback (most recent call last): 
>> > [sagemath_doc_html-none] File "/usr/lib/python3.9/runpy.py", line 197, 
>> in _run_module_as_main 
>> > [sagemath_doc_html-none] return _run_code(code, main_globals, None, 
>> > [sagemath_doc_html-none] File "/usr/lib/python3.9/runpy.py", line 87, 
>> in _run_code 
>> > [sagemath_doc_html-none] exec(code, run_globals) 
>> > [sagemath_doc_html-none] File 
>> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
>>  
>> line 2, in  
>> > [sagemath_doc_html-none] main() 
>> > [sagemath_doc_html-none] File 
>> 

Re: [sage-support] Re: Sage crash report

[Emmanuel Charpentier]

make giac-clean && make did it !

(*Alla cinese*) 10^4 thanks !
​
Le vendredi 10 décembre 2021 à 11:56:00 UTC+1, dim...@gmail.com a écrit :

> Everything that depends on updated Debian libs has to be rebuilt - looks 
> like
>
> make giac-clean
>
> is needed too, for sure.
>
> On Fri, Dec 10, 2021 at 10:36 AM Emmanuel Charpentier
>  wrote:
> >
> >
> >
> > Le vendredi 10 décembre 2021 à 01:04:33 UTC+1, Matthias Koeppe a écrit :
> >>
> >> "make sagelib-clean" will fix this
> >
> >
> > Nope. `make sagelib-clean` succeeds, but the following `make` fails at 
> documentation ; attempting `make doc-clean && make also fails, *with the 
> very same error*... :
> >
> > ```
> > [sagemath_doc_html-none] cd /usr/local/sage-9 && ./sage --docbuild 
> --no-pdf-links reference/libs inventory --no-prune-empty-dirs
> > [sagemath_doc_html-none] Warning: Could not import sage.libs.giac 
> libgsl.so.25: cannot open shared object file: No such file or directory
> > [sagemath_doc_html-none] 
> /usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py:1066:
>  
> DeprecationWarning: the module sage.libs.ratpoints is deprecated; use 
> pari.ellratpoints or pari.hyperellratpoints instead
> > [sagemath_doc_html-none] See http://trac.sagemath.org/24531 for details.
> > [sagemath_doc_html-none] __import__(module_name)
> > [sagemath_doc_html-none] [libs ] building [inventory]: targets for 39 
> source files that are out of date
> > [sagemath_doc_html-none] [libs ] updating environment: [new config] 39 
> added, 0 changed, 0 removed
> > [sagemath_doc_html-none] [libs ] WARNING: autodoc: failed to import 
> module 'giac' from module 'sage.libs'; the following exception was raised:
> > [sagemath_doc_html-none] [libs ] libgsl.so.25: cannot open shared object 
> file: No such file or directory
> > [sagemath_doc_html-none] [libs ] The inventory files are in 
> local/share/doc/sage/inventory/en/reference/libs.
> > [sagemath_doc_html-none] Error building the documentation.
> > [sagemath_doc_html-none] Traceback (most recent call last):
> > [sagemath_doc_html-none] File "/usr/lib/python3.9/runpy.py", line 197, 
> in _run_module_as_main
> > [sagemath_doc_html-none] return _run_code(code, main_globals, None,
> > [sagemath_doc_html-none] File "/usr/lib/python3.9/runpy.py", line 87, in 
> _run_code
> > [sagemath_doc_html-none] exec(code, run_globals)
> > [sagemath_doc_html-none] File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
>  
> line 2, in 
> > [sagemath_doc_html-none] main()
> > [sagemath_doc_html-none] File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
>  
> line 1815, in main
> > [sagemath_doc_html-none] builder()
> > [sagemath_doc_html-none] File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
>  
> line 822, in _wrapper
> > [sagemath_doc_html-none] getattr(DocBuilder, build_type)(self, *args, 
> **kwds)
> > [sagemath_doc_html-none] File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
>  
> line 133, in f
> > [sagemath_doc_html-none] runsphinx()
> > [sagemath_doc_html-none] File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
>  
> line 323, in runsphinx
> > [sagemath_doc_html-none] sys.stderr.raise_errors()
> > [sagemath_doc_html-none] File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
>  
> line 258, in raise_errors
> > [sagemath_doc_html-none] raise OSError(self._error)
> > [sagemath_doc_html-none] OSError: WARNING: autodoc: failed to import 
> module 'giac' from module 'sage.libs'; the following exception was raised:
> > [sagemath_doc_html-none]
> > [sagemath_doc_html-none] Note: incremental documentation builds 
> sometimes cause spurious
> > [sagemath_doc_html-none] error messages. To be certain that these are 
> real errors, run
> > [sagemath_doc_html-none] "make doc-clean" first and try again.
> > [sagemath_doc_html-none] make[6]: *** [Makefile:20 : 
> doc-inventory--reference-libs] Erreur 1
> > [sagemath_doc_html-none] make[5]: *** [Makefile:37 : 
> doc-inventory-reference] Erreur 2
> > make[4]: *** [Makefile:2789 : sagemath_doc_html-SAGE_DOCS-no-deps] 
> Erreur 2
> > make[3]: *** [Makefile:2789 : 
> /usr/local/sage-9/local/var/lib/sage/installed/sagemath_doc_html-none] 
> Erreur 2
> > make[2]: *** [Makefile:2332 : all-start] Erreur 2
> > make[2] : on quitte le répertoire « /usr/local/sage-9/build/make »
> >
> > real 18m33,136s
> > user 29m24,260s
> > sys 1m6,712s
> > ***
> > Error building Sage.
> >
> > The following package(s) may have failed to build (not necessarily
> > during this run of 'make all-start'):
> >
> > It is safe to 

Re: [sage-support] Re: Sage crash report

[Dima Pasechnik]

Everything that depends on updated Debian libs has to be rebuilt - looks like

make giac-clean

is needed too, for sure.

On Fri, Dec 10, 2021 at 10:36 AM Emmanuel Charpentier
 wrote:
>
>
>
> Le vendredi 10 décembre 2021 à 01:04:33 UTC+1, Matthias Koeppe a écrit :
>>
>> "make sagelib-clean" will fix this
>
>
> Nope. `make sagelib-clean` succeeds, but the following `make` fails at 
> documentation ; attempting `make doc-clean && make also fails, *with the very 
> same error*... :
>
> ```
> [sagemath_doc_html-none] cd /usr/local/sage-9 && ./sage --docbuild 
> --no-pdf-links reference/libs inventory --no-prune-empty-dirs
> [sagemath_doc_html-none] Warning: Could not import sage.libs.giac 
> libgsl.so.25: cannot open shared object file: No such file or directory
> [sagemath_doc_html-none] 
> /usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py:1066:
>  DeprecationWarning: the module sage.libs.ratpoints is deprecated; use 
> pari.ellratpoints or pari.hyperellratpoints instead
> [sagemath_doc_html-none] See http://trac.sagemath.org/24531 for details.
> [sagemath_doc_html-none]   __import__(module_name)
> [sagemath_doc_html-none] [libs ] building [inventory]: targets for 39 
> source files that are out of date
> [sagemath_doc_html-none] [libs ] updating environment: [new config] 39 
> added, 0 changed, 0 removed
> [sagemath_doc_html-none] [libs ] WARNING: autodoc: failed to import 
> module 'giac' from module 'sage.libs'; the following exception was raised:
> [sagemath_doc_html-none] [libs ] libgsl.so.25: cannot open shared object 
> file: No such file or directory
> [sagemath_doc_html-none] [libs ] The inventory files are in 
> local/share/doc/sage/inventory/en/reference/libs.
> [sagemath_doc_html-none] Error building the documentation.
> [sagemath_doc_html-none] Traceback (most recent call last):
> [sagemath_doc_html-none]   File "/usr/lib/python3.9/runpy.py", line 197, in 
> _run_module_as_main
> [sagemath_doc_html-none] return _run_code(code, main_globals, None,
> [sagemath_doc_html-none]   File "/usr/lib/python3.9/runpy.py", line 87, in 
> _run_code
> [sagemath_doc_html-none] exec(code, run_globals)
> [sagemath_doc_html-none]   File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
>  line 2, in 
> [sagemath_doc_html-none] main()
> [sagemath_doc_html-none]   File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
>  line 1815, in main
> [sagemath_doc_html-none] builder()
> [sagemath_doc_html-none]   File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
>  line 822, in _wrapper
> [sagemath_doc_html-none] getattr(DocBuilder, build_type)(self, *args, 
> **kwds)
> [sagemath_doc_html-none]   File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
>  line 133, in f
> [sagemath_doc_html-none] runsphinx()
> [sagemath_doc_html-none]   File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
>  line 323, in runsphinx
> [sagemath_doc_html-none] sys.stderr.raise_errors()
> [sagemath_doc_html-none]   File 
> "/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
>  line 258, in raise_errors
> [sagemath_doc_html-none] raise OSError(self._error)
> [sagemath_doc_html-none] OSError: WARNING: autodoc: failed to import module 
> 'giac' from module 'sage.libs'; the following exception was raised:
> [sagemath_doc_html-none]
> [sagemath_doc_html-none] Note: incremental documentation builds sometimes 
> cause spurious
> [sagemath_doc_html-none] error messages. To be certain that these are 
> real errors, run
> [sagemath_doc_html-none] "make doc-clean" first and try again.
> [sagemath_doc_html-none] make[6]: *** [Makefile:20 : 
> doc-inventory--reference-libs] Erreur 1
> [sagemath_doc_html-none] make[5]: *** [Makefile:37 : doc-inventory-reference] 
> Erreur 2
> make[4]: *** [Makefile:2789 : sagemath_doc_html-SAGE_DOCS-no-deps] Erreur 2
> make[3]: *** [Makefile:2789 : 
> /usr/local/sage-9/local/var/lib/sage/installed/sagemath_doc_html-none] Erreur 
> 2
> make[2]: *** [Makefile:2332 : all-start] Erreur 2
> make[2] : on quitte le répertoire « /usr/local/sage-9/build/make »
>
> real18m33,136s
> user29m24,260s
> sys1m6,712s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> It is safe to delete any log files and build directories, but they
> contain information that is helpful for debugging build problems.
> WARNING: If you now run 'make' again, the build directory of the
> same version 

[sage-support] Re: Sage crash report

[Emmanuel Charpentier]

Le vendredi 10 décembre 2021 à 01:04:33 UTC+1, Matthias Koeppe a écrit :

> "make sagelib-clean" will fix this
>

Nope. `make sagelib-clean` succeeds, but the following `make` fails at 
documentation ; attempting `make doc-clean && make also fails, *with the 
very same error*... :

```
[sagemath_doc_html-none] cd /usr/local/sage-9 && ./sage --docbuild 
--no-pdf-links reference/libs inventory --no-prune-empty-dirs
[sagemath_doc_html-none] Warning: Could not import sage.libs.giac 
libgsl.so.25: cannot open shared object file: No such file or directory
[sagemath_doc_html-none] 
/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py:1066:
 
DeprecationWarning: the module sage.libs.ratpoints is deprecated; use 
pari.ellratpoints or pari.hyperellratpoints instead
[sagemath_doc_html-none] See http://trac.sagemath.org/24531 for details.
[sagemath_doc_html-none]   __import__(module_name)
[sagemath_doc_html-none] [libs ] building [inventory]: targets for 39 
source files that are out of date
[sagemath_doc_html-none] [libs ] updating environment: [new config] 39 
added, 0 changed, 0 removed
[sagemath_doc_html-none] [libs ] WARNING: autodoc: failed to import 
module 'giac' from module 'sage.libs'; the following exception was raised:
[sagemath_doc_html-none] [libs ] libgsl.so.25: cannot open shared 
object file: No such file or directory
[sagemath_doc_html-none] [libs ] The inventory files are in 
local/share/doc/sage/inventory/en/reference/libs.
[sagemath_doc_html-none] Error building the documentation.
[sagemath_doc_html-none] Traceback (most recent call last):
[sagemath_doc_html-none]   File "/usr/lib/python3.9/runpy.py", line 197, in 
_run_module_as_main
[sagemath_doc_html-none] return _run_code(code, main_globals, None,
[sagemath_doc_html-none]   File "/usr/lib/python3.9/runpy.py", line 87, in 
_run_code
[sagemath_doc_html-none] exec(code, run_globals)
[sagemath_doc_html-none]   File 
"/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__main__.py",
 
line 2, in 
[sagemath_doc_html-none] main()
[sagemath_doc_html-none]   File 
"/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
 
line 1815, in main
[sagemath_doc_html-none] builder()
[sagemath_doc_html-none]   File 
"/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
 
line 822, in _wrapper
[sagemath_doc_html-none] getattr(DocBuilder, build_type)(self, *args, 
**kwds)
[sagemath_doc_html-none]   File 
"/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/__init__.py",
 
line 133, in f
[sagemath_doc_html-none] runsphinx()
[sagemath_doc_html-none]   File 
"/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
 
line 323, in runsphinx
[sagemath_doc_html-none] sys.stderr.raise_errors()
[sagemath_doc_html-none]   File 
"/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage_docbuild/sphinxbuild.py",
 
line 258, in raise_errors
[sagemath_doc_html-none] raise OSError(self._error)
[sagemath_doc_html-none] OSError: WARNING: autodoc: failed to import module 
'giac' from module 'sage.libs'; the following exception was raised:
[sagemath_doc_html-none] 
[sagemath_doc_html-none] Note: incremental documentation builds 
sometimes cause spurious
[sagemath_doc_html-none] error messages. To be certain that these are 
real errors, run
[sagemath_doc_html-none] "make doc-clean" first and try again.
[sagemath_doc_html-none] make[6]: *** [Makefile:20 : 
doc-inventory--reference-libs] Erreur 1
[sagemath_doc_html-none] make[5]: *** [Makefile:37 : 
doc-inventory-reference] Erreur 2
make[4]: *** [Makefile:2789 : sagemath_doc_html-SAGE_DOCS-no-deps] Erreur 2
make[3]: *** [Makefile:2789 : 
/usr/local/sage-9/local/var/lib/sage/installed/sagemath_doc_html-none] 
Erreur 2
make[2]: *** [Makefile:2332 : all-start] Erreur 2
make[2] : on quitte le répertoire « /usr/local/sage-9/build/make »

real18m33,136s
user29m24,260s
sys1m6,712s
***
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

It is safe to delete any log files and build directories, but they
contain information that is helpful for debugging build problems.
WARNING: If you now run 'make' again, the build directory of the
same version of the package will, by default, be deleted. Set the
environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.

make[1]: *** [Makefile:39 : all-start] Erreur 1
make[1] : on quitte le répertoire « /usr/local/sage-9 »
make: *** [Makefile:13 : all] Erreur 2
```

Suggestions ?

 

> On Thursday, December 9, 2021 at 12:18:02 PM UTC-8 Emmanuel Charpentier 
> 

[sage-support] Re: Sage crash report

[Matthias Koeppe]

"make sagelib-clean" will fix this

On Thursday, December 9, 2021 at 12:18:02 PM UTC-8 Emmanuel Charpentier 
wrote:

> A recent upgrade of Debian testing seems to have broken Sage, which does 
> not find libgsl.so.25 Crash report attached.
>
> An attempt at make -b also fails (see attached install.log).
>
> The worse is :
>
> charpent@zen-book-flip:/usr/local/sage-9$ locate libgsl.so
>
> /usr/lib/x86_64-linux-gnu/libgsl.so
>
> /usr/lib/x86_64-linux-gnu/libgsl.so.25
>
> /usr/lib/x86_64-linux-gnu/libgsl.so.25.0.0
>
> charpent@zen-book-flip:/usr/local/sage-9$ dpkg -l "*libgsl*"
>
> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
>
> | 
> État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=att>
>
> |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
>
> ||/ NomVersion  Architecture Description
>
> +++-==---==>
>
> ii  libgsl-dev 2.7.1+dfsg-3 amd64GNU Scientific Library (GSL) 
> ->
>
> un  libgsl0  (aucune description n'est 
> disp>
>
> un  libgsl0-dev  (aucune description n'est 
> disp>
>
> un  libgsl0ldbl  (aucune description n'est 
> disp>
>
> un  libgsl2  (aucune description n'est 
> disp>
>
> un  libgsl23 (aucune description n'est 
> disp>
>
> ii  libgsl27:amd64 2.7.1+dfsg-3 amd64GNU Scientific Library (GSL) 
> ->
>
> ii  libgslcblas0:amd64 2.7.1+dfsg-3 amd64GNU Scientific Library (GSL) 
> ->
>
>
> I'm a bit at loss...
>
>

-- 
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/a250b849-5ff2-4298-be15-4238fad2e560n%40googlegroups.com.

[sage-support] Re: Sage Crash Report

[Gaël Cousin]

I solved the problem. I think the blender ppa came with a strange 
version of libgivaro9 and libgivaro-dev. I downgraded them and 
reinstalled Sage. Now it works!


Blender also seems to work!


Best,

G

Le 16/08/2021 à 17:08, Gaël Cousin a écrit :


Ubuntu 20.04 Focal Fossa


Dear all,

Here follows attached a sage crash report. I think the sage install 
was broken by installation of Blender.



Sage was installed this way on my fresh Ubuntu 20.04 Focal Fossa:
sudo apt install sagemath sagetex- texlive-latex-base- sagemath-jupyter- 
pari-doc- sagemath-doc-

(afterwards I did

sudo apt install jupyter

and

sudo apt install sagemath-jupyter

everything was working fine)


Today I installed Blender

   sudo add-apt-repository ppa:savoury1/ffmpeg4

   sudo add-apt-repository ppa:savoury1/blender

   sudo apt-get update

   sudo apt-get upgrade && sudo apt-get dist-upgrade

   sudo apt-get install blender


Afterwards

I tried the command
|maxima('plotdf([-y,-x],[x,y],[x,-2,2],[y,-2,2])') |

in the jupyter notebook and I got a missing Kernel error

afterwards the kernel would not restart successfully and I restarted 
my computer.



Then I run

sage

in the terminal, which generated this crash report.

Currently, Sage is not working anymore on my computer.


There are strange things about python and numpy written in Blender's 
ppa description. I attach this description too (see lines 23 and 43).


I checked the result of python3 --version in the terminal and got

Python 3.8.10


Any hint towards the resolution of this sad situation is welcome.

Thanks fo your work on Sage.


Best,

Gaël Cousin.






--
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/6a172e8d-704e-6bb2-8306-8c6473e30e07%40gmail.com.

[sage-support] Re: Sage Crash Report

[Zachary Scherr]

Glad I can help.  This is another reason why these virtual environments are 
really useful! I have one environment for sage which I never try to update 
since I know that everything works.  Separately, I have my "main" 
environment that I update regularly, which will occasionally break things. 
 I broke ipython in that environment and then stumbled 
on https://github.com/ipython/ipython/issues/12740 which tracks this 
problem.

You can also feel free to experiment without fear of breaking things using 
conda.  For example, I see that you have sage installed with python 3.8. 
 If you wanted to try sage with python 3.9 without any fear you could do 
something like

conda create -n sage_python3.9 sage=9.2 python=3.9 -c conda-forge

and then you would have a new environment with sage 9.2 and python 3.9.  

Given how often Mac's new operating systems break everything, it's kind of 
amazing that conda has been so stable.  A lot of credit goes to Isuru 
Fernando and the work that he puts in on maintaining sage on conda forge.

On Monday, January 4, 2021 at 12:58:09 PM UTC-5 maciek...@gmail.com wrote:

> ad. 1. It turned out that indeed I had installed the most recent version 
> of jedi. Installing 0.17.2 fixed the problem - thank you very much!
>
> ad. 2. I see - I am new to conda and I only used it to install sage; 
> thanks for your explanation.
>
> On Monday, January 4, 2021 at 6:38:01 PM UTC+1 zsc...@gmail.com wrote:
>
>> 1.  Did you by any chance accidentally update the jedi package? This is 
>> not really a sage problem, but ipython 7.19.0 is incompatible with the most 
>> recent version of jedi 0.18.0.  In your sage environment you can run "conda 
>> list" to see what packages you have installed.  If jedi 0.18.0 is listed 
>> then you can run "conda install jedi==0.17.2".
>>
>> 2.  That's kinda the whole point behind anaconda/miniconda.  You can put 
>> different python projects into different environments so that their 
>> dependencies don't contaminate one another.  If you want to have your sage 
>> environment always loaded you can activate it in your .zshrc file or you 
>> can do something like 
>>
>> >> alias sage="whatever your path to the conda sage binary is".
>>
>> On Monday, January 4, 2021 at 8:48:28 AM UTC-5 maciek...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> I encountered the following problems with sage:
>>>
>>> 1. It crashes when I am using tab auto completion - report attached.
>>> 2. Each time I want to use sage (by command 'sage') after restarting the 
>>> system I need to type 'conda activate sage'. Otherwise command sage is 
>>> not recognized ('-bash: sage: command not found').
>>>
>>> I run Sage 9.2 on MacOS Big Sur 11.1 (Macbook Pro) which was installed 
>>> by Conda.
>>>
>>> Best,
>>> Maciek
>>>
>>

-- 
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/d261b6be-8ca6-417e-bcdc-0647ac9a53cdn%40googlegroups.com.

[sage-support] Re: Sage Crash Report

[Maciek D]

ad. 1. It turned out that indeed I had installed the most recent version of 
jedi. Installing 0.17.2 fixed the problem - thank you very much!

ad. 2. I see - I am new to conda and I only used it to install sage; thanks 
for your explanation.

On Monday, January 4, 2021 at 6:38:01 PM UTC+1 zsc...@gmail.com wrote:

> 1.  Did you by any chance accidentally update the jedi package? This is 
> not really a sage problem, but ipython 7.19.0 is incompatible with the most 
> recent version of jedi 0.18.0.  In your sage environment you can run "conda 
> list" to see what packages you have installed.  If jedi 0.18.0 is listed 
> then you can run "conda install jedi==0.17.2".
>
> 2.  That's kinda the whole point behind anaconda/miniconda.  You can put 
> different python projects into different environments so that their 
> dependencies don't contaminate one another.  If you want to have your sage 
> environment always loaded you can activate it in your .zshrc file or you 
> can do something like 
>
> >> alias sage="whatever your path to the conda sage binary is".
>
> On Monday, January 4, 2021 at 8:48:28 AM UTC-5 maciek...@gmail.com wrote:
>
>> Hi,
>>
>> I encountered the following problems with sage:
>>
>> 1. It crashes when I am using tab auto completion - report attached.
>> 2. Each time I want to use sage (by command 'sage') after restarting the 
>> system I need to type 'conda activate sage'. Otherwise command sage is 
>> not recognized ('-bash: sage: command not found').
>>
>> I run Sage 9.2 on MacOS Big Sur 11.1 (Macbook Pro) which was installed by 
>> Conda.
>>
>> Best,
>> Maciek
>>
>

-- 
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/47d05f44-1757-422d-87e5-6c5998580ea9n%40googlegroups.com.

[sage-support] Re: Sage Crash Report

[Zachary Scherr]

1.  Did you by any chance accidentally update the jedi package? This is not 
really a sage problem, but ipython 7.19.0 is incompatible with the most 
recent version of jedi 0.18.0.  In your sage environment you can run "conda 
list" to see what packages you have installed.  If jedi 0.18.0 is listed 
then you can run "conda install jedi==0.17.2".

2.  That's kinda the whole point behind anaconda/miniconda.  You can put 
different python projects into different environments so that their 
dependencies don't contaminate one another.  If you want to have your sage 
environment always loaded you can activate it in your .zshrc file or you 
can do something like 

>> alias sage="whatever your path to the conda sage binary is".

On Monday, January 4, 2021 at 8:48:28 AM UTC-5 maciek...@gmail.com wrote:

> Hi,
>
> I encountered the following problems with sage:
>
> 1. It crashes when I am using tab auto completion - report attached.
> 2. Each time I want to use sage (by command 'sage') after restarting the 
> system I need to type 'conda activate sage'. Otherwise command sage is 
> not recognized ('-bash: sage: command not found').
>
> I run Sage 9.2 on MacOS Big Sur 11.1 (Macbook Pro) which was installed by 
> Conda.
>
> Best,
> Maciek
>

-- 
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/f7acfe71-e5ea-4a46-afee-cc333f371222n%40googlegroups.com.

[sage-support] Re: Sage Crash Report: `TypeError` upon startup (Sage 9.0.0)

[Matthias Koeppe]

Problems with the Ubuntu packaging should be reported as an Ubuntu bug.

On Sunday, August 2, 2020 at 11:31:57 PM UTC-7, Samuel Tang wrote:
>
> Hi,
>
> Thanks for your quick response. I am running on Ubuntu 20.04, and 
> installed Sagemath via `sudo apt-get install sagemath`.
> From what I recorded, it was Sage 9.0 on Python 3.8.2 since I've installed 
> Ubuntu (in early July The version are consistent on Sage and Python when I 
> referred just now:
>
> ```
> $ sage --version
> SageMath version 9.0, Release Date: 2020-01-01
>
> $ python --version
> Python 3.8.2
> ```
>
> Since I was using Sage in a daily basis in the previous week, so I think 
> I've triggered something lately causing the problem.
> Moreover I found an entry from /var/log/dpkg.log.1 that may cause the 
> problem (unsure about that).
>
> ```
> 2020-07-30 11:52:47 upgrade python3-distupgrade:all 1:20.04.21 1:20.04.23
> 2020-07-30 11:52:47 status half-configured python3-distupgrade:all 
> 1:20.04.21
> 2020-07-30 11:52:47 status unpacked python3-distupgrade:all 1:20.04.21
> 2020-07-30 11:52:47 status half-installed python3-distupgrade:all 
> 1:20.04.21
> 2020-07-30 11:52:48 status unpacked python3-distupgrade:all 1:20.04.23
> ```
>
> Should I downgrade my Python version to see if Sage could start up 
> properly? Thanks much!
> slelievre在 2020年8月3日星期一下午1:57:05 [UTC+8]寫道：
>
>> Le lundi 3 août 2020 05:31:01 UTC+2, Samuel Tang a écrit :
>>>
>>> Hi team,
>>>
>>> This issue happened to me just one day ago.
>>>
>>> I am aware of https://trac.sagemath.org/ticket/18492 and
>>>
>> https://www.mail-archive.com/debian-b...@lists.debian.org/msg1671690.html 
>>> 
>>>
>> as they have the same TypeError, but I think that is not my case.
>>>
>>> Thanks for the help in advance!
>>>
>>
>> Hi Samuel,
>>
>> Did you just install Sage? Probably not or you would have installed
>> either Sage 9.1 or Sage 9.2.beta7.
>>
>> More likely, did you have Sage installed on your computer for a while,
>> via some package manager, and working well, and did you just upgrade
>> the system Python from Python 3.7.x to Python 3.8.x?
>>
>> Python 3.8.x is not supported yet, we're slowly getting there, see:
>>
>> - Sage Trac ticket 27754
>>   Upgrade: Python 3.8.5
>>   https://trac.sagemath.org/ticket/27754
>>
>> For more support, what is your OS and how did you install Sage?
>>
>>

-- 
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/879f29ad-61bf-428b-be67-7712af401720o%40googlegroups.com.

[sage-support] Re: Sage Crash Report: `TypeError` upon startup (Sage 9.0.0)

[Samuel Tang]

Hi,

Thanks for your quick response. I am running on Ubuntu 20.04, and installed 
Sagemath via `sudo apt-get install sagemath`.
>From what I recorded, it was Sage 9.0 on Python 3.8.2 since I've installed 
Ubuntu (in early July The version are consistent on Sage and Python when I 
referred just now:

```
$ sage --version
SageMath version 9.0, Release Date: 2020-01-01

$ python --version
Python 3.8.2
```

Since I was using Sage in a daily basis in the previous week, so I think 
I've triggered something lately causing the problem.
Moreover I found an entry from /var/log/dpkg.log.1 that may cause the 
problem (unsure about that).

```
2020-07-30 11:52:47 upgrade python3-distupgrade:all 1:20.04.21 1:20.04.23
2020-07-30 11:52:47 status half-configured python3-distupgrade:all 
1:20.04.21
2020-07-30 11:52:47 status unpacked python3-distupgrade:all 1:20.04.21
2020-07-30 11:52:47 status half-installed python3-distupgrade:all 1:20.04.21
2020-07-30 11:52:48 status unpacked python3-distupgrade:all 1:20.04.23
```

Should I downgrade my Python version to see if Sage could start up 
properly? Thanks much!
slelievre在 2020年8月3日星期一下午1:57:05 [UTC+8]寫道：

> Le lundi 3 août 2020 05:31:01 UTC+2, Samuel Tang a écrit :
>>
>> Hi team,
>>
>> This issue happened to me just one day ago.
>>
>> I am aware of https://trac.sagemath.org/ticket/18492 and
>>
> https://www.mail-archive.com/debian-b...@lists.debian.org/msg1671690.html 
>> 
>>
> as they have the same TypeError, but I think that is not my case.
>>
>> Thanks for the help in advance!
>>
>
> Hi Samuel,
>
> Did you just install Sage? Probably not or you would have installed
> either Sage 9.1 or Sage 9.2.beta7.
>
> More likely, did you have Sage installed on your computer for a while,
> via some package manager, and working well, and did you just upgrade
> the system Python from Python 3.7.x to Python 3.8.x?
>
> Python 3.8.x is not supported yet, we're slowly getting there, see:
>
> - Sage Trac ticket 27754
>   Upgrade: Python 3.8.5
>   https://trac.sagemath.org/ticket/27754
>
> For more support, what is your OS and how did you install Sage?
>
>

-- 
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/e7c8ad74-6767-4f79-b225-e734c3fe4402n%40googlegroups.com.

[sage-support] Re: Sage Crash Report: `TypeError` upon startup (Sage 9.0.0)

[slelievre]

Le lundi 3 août 2020 05:31:01 UTC+2, Samuel Tang a écrit :
>
> Hi team,
>
> This issue happened to me just one day ago.
>
> I am aware of https://trac.sagemath.org/ticket/18492 and
>
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1671690.html
>
as they have the same TypeError, but I think that is not my case.
>
> Thanks for the help in advance!
>

Hi Samuel,

Did you just install Sage? Probably not or you would have installed
either Sage 9.1 or Sage 9.2.beta7.

More likely, did you have Sage installed on your computer for a while,
via some package manager, and working well, and did you just upgrade
the system Python from Python 3.7.x to Python 3.8.x?

Python 3.8.x is not supported yet, we're slowly getting there, see:

- Sage Trac ticket 27754
  Upgrade: Python 3.8.5
  https://trac.sagemath.org/ticket/27754

For more support, what is your OS and how did you install Sage?

-- 
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/3db476fe-aaf3-4107-b65d-f7607467ad6bo%40googlegroups.com.

Re: [sage-support] Re: Sage Crash Report: Missing symbols in conda build for macOS?

[Michael Boyle]

That works!  Similarly

conda install -n sage "pynac=0.7.26=py36ha01bd41_0"

works for my python 3.6 attempt.  I see that you've already opened an issue 
on pynac-feedstock, so I'll leave you to it.

Thanks very much for you help!

-- 
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/b6a93fe7-3a1d-4b36-9af8-91e01f55d714%40googlegroups.com.

Re: [sage-support] Re: Sage Crash Report: Missing symbols in conda build for macOS?

[Isuru Fernando]

Hi,

Can you try doing the following?

conda install -n sage27 "pynac=0.7.26=py27ha01bd41_0"

Isuru

On Tue, Nov 19, 2019 at 11:23 AM Michael Boyle <
michael.oliver.bo...@gmail.com> wrote:

> Sure.  Here it is:
>
> > conda list
> # packages in environment at
> /Users/myusername/.continuum/miniconda3.7/envs/sage27:
> #
> # NameVersion   Build  Channel
> _r-mutex  1.0.1   anacondar_1conda-forge
> alabaster 0.7.12 py_0conda-forge
> appdirs   1.4.3  py_1conda-forge
> appnope   0.1.0 py27_1000conda-forge
> arb   2.16.0h3aece09_1000conda-forge
> attrs 19.3.0 py_0conda-forge
> automat   0.8.0  py_0conda-forge
> babel 2.7.0  py_0conda-forge
> backports 1.0py_2conda-forge
> backports.functools_lru_cache 1.6.1  py_0
> conda-forge
> backports.os  0.1.1 py27_1001conda-forge
> backports.shutil_get_terminal_size 1.0.0  py_3
> conda-forge
> backports_abc 0.5py_1conda-forge
> bdw-gc8.0.4ha1b3eb9_0conda-forge
> bleach3.1.0  py_0conda-forge
> brial 1.2.5  py_1conda-forge
> bwidget   1.9.130conda-forge
> bzip2 1.0.8h01d97ff_1conda-forge
> ca-certificates   2019.9.11hecc5488_0conda-forge
> cairo 1.16.0he1c11cd_1002conda-forge
> cctools   921  h5ba7a2e_4conda-forge
> cddlib1!0.94j   h65ac59c_1001conda-forge
> certifi   2019.9.11py27_0conda-forge
> cffi  1.13.2   py27h33e799b_0conda-forge
> chardet   3.0.4 py27_1003conda-forge
> clang 9.0.0   default_hf57f61e_4conda-forge
> clang_osx-64  9.0.0h22b1bf0_3conda-forge
> clangxx   9.0.0   default_hf57f61e_4conda-forge
> clangxx_osx-649.0.0h22b1bf0_3conda-forge
> click 7.0py_0conda-forge
> cliquer   1.21  h1de35cc_1000conda-forge
> compiler-rt   9.0.0h2b4a0d1_1conda-forge
> configparser  3.7.3py27_1conda-forge
> constantly15.1.0 py_0conda-forge
> contextlib2   0.6.0.post1py_0conda-forge
> cryptography  2.8  py27hafa8578_0conda-forge
> curl  7.65.3   h22ea746_0conda-forge
> cvxopt1.2.3   py27h43946de_203conda-forge
> cycler0.10.0 py_2conda-forge
> cypari2   2.1.1py27h7c56200_0conda-forge
> cysignals 1.10.2   py27hba7914e_1conda-forge
> cython0.29.14  py27h4a8c4bd_0conda-forge
> decorator 4.4.1  py_0conda-forge
> defusedxml0.6.0  py_0conda-forge
> docutils  0.15.2   py27_0conda-forge
> dsdp  5.8   h7674d01_1203conda-forge
> ecl   16.1.2h0672242_1004conda-forge
> eclib 20190226 he5f4af6_2conda-forge
> ecm   7.0.4 h65ac59c_1002conda-forge
> entrypoints   0.3   py27_1000conda-forge
> enum341.1.6 py27_1002conda-forge
> expat 2.2.5 h4a8c4bd_1004conda-forge
> fastcache 1.1.0py27h0b31af3_0conda-forge
> fflas-ffpack  2.4.3h75e9206_1conda-forge
> fftw  3.3.8   nompi_h44ae4c8_1110
> conda-forge
> flask 0.11.1 py_1conda-forge
> flask-autoindex   0.6.2  py_0conda-forge
> flask-babel   0.12.2 py_0conda-forge
> flask-oldsessions 0.10   py_0conda-forge
> flask-openid  1.2.5 py27_1003conda-forge
> flask-silk0.2py_0conda-forge
> flintqs 

[sage-support] Re: Sage Crash Report: Missing symbols in conda build for macOS?

[Michael Boyle]

Sure.  Here it is:

> conda list
# packages in environment at 
/Users/myusername/.continuum/miniconda3.7/envs/sage27:
#
# NameVersion   Build  Channel
_r-mutex  1.0.1   anacondar_1conda-forge
alabaster 0.7.12 py_0conda-forge
appdirs   1.4.3  py_1conda-forge
appnope   0.1.0 py27_1000conda-forge
arb   2.16.0h3aece09_1000conda-forge
attrs 19.3.0 py_0conda-forge
automat   0.8.0  py_0conda-forge
babel 2.7.0  py_0conda-forge
backports 1.0py_2conda-forge
backports.functools_lru_cache 1.6.1  py_0conda-forge
backports.os  0.1.1 py27_1001conda-forge
backports.shutil_get_terminal_size 1.0.0  py_3
conda-forge
backports_abc 0.5py_1conda-forge
bdw-gc8.0.4ha1b3eb9_0conda-forge
bleach3.1.0  py_0conda-forge
brial 1.2.5  py_1conda-forge
bwidget   1.9.130conda-forge
bzip2 1.0.8h01d97ff_1conda-forge
ca-certificates   2019.9.11hecc5488_0conda-forge
cairo 1.16.0he1c11cd_1002conda-forge
cctools   921  h5ba7a2e_4conda-forge
cddlib1!0.94j   h65ac59c_1001conda-forge
certifi   2019.9.11py27_0conda-forge
cffi  1.13.2   py27h33e799b_0conda-forge
chardet   3.0.4 py27_1003conda-forge
clang 9.0.0   default_hf57f61e_4conda-forge
clang_osx-64  9.0.0h22b1bf0_3conda-forge
clangxx   9.0.0   default_hf57f61e_4conda-forge
clangxx_osx-649.0.0h22b1bf0_3conda-forge
click 7.0py_0conda-forge
cliquer   1.21  h1de35cc_1000conda-forge
compiler-rt   9.0.0h2b4a0d1_1conda-forge
configparser  3.7.3py27_1conda-forge
constantly15.1.0 py_0conda-forge
contextlib2   0.6.0.post1py_0conda-forge
cryptography  2.8  py27hafa8578_0conda-forge
curl  7.65.3   h22ea746_0conda-forge
cvxopt1.2.3   py27h43946de_203conda-forge
cycler0.10.0 py_2conda-forge
cypari2   2.1.1py27h7c56200_0conda-forge
cysignals 1.10.2   py27hba7914e_1conda-forge
cython0.29.14  py27h4a8c4bd_0conda-forge
decorator 4.4.1  py_0conda-forge
defusedxml0.6.0  py_0conda-forge
docutils  0.15.2   py27_0conda-forge
dsdp  5.8   h7674d01_1203conda-forge
ecl   16.1.2h0672242_1004conda-forge
eclib 20190226 he5f4af6_2conda-forge
ecm   7.0.4 h65ac59c_1002conda-forge
entrypoints   0.3   py27_1000conda-forge
enum341.1.6 py27_1002conda-forge
expat 2.2.5 h4a8c4bd_1004conda-forge
fastcache 1.1.0py27h0b31af3_0conda-forge
fflas-ffpack  2.4.3h75e9206_1conda-forge
fftw  3.3.8   nompi_h44ae4c8_1110conda-forge
flask 0.11.1 py_1conda-forge
flask-autoindex   0.6.2  py_0conda-forge
flask-babel   0.12.2 py_0conda-forge
flask-oldsessions 0.10   py_0conda-forge
flask-openid  1.2.5 py27_1003conda-forge
flask-silk0.2py_0conda-forge
flintqs   1.0   hc269f14_1000conda-forge
fontconfig2.13.1h6b1039f_1001conda-forge
fplll 5.2.1 hc88034f_1000conda-forge
fpylll0.4.1devpy27heb9bef1_1000conda-forge
freetype  2.10.0

[sage-support] Re: Sage Crash Report: Missing symbols in conda build for macOS?

[Julian Rüth]

Hi Micheal,

could you share the output of `conda list` for that environment?

Feel free to open an issue for this at 
https://github.com/conda-forge/sage-feedstock/issues as well.

julian

On Tuesday, November 19, 2019 at 6:04:23 PM UTC+1, Michael Boyle wrote:
>
> I followed the installation instructions for conda 
>  with both
> python=3.6 (the most recent version that could install sage without
> conflicts) and then python=2.7 (the one specifically cited in the
> instructions) on macOS 10.13.6, using miniconda3.7.  Both complete
> installation happily, but sage immediately dies in both environment.s
> I have never used Sage before, so I have no Sage configuration, and I had
> no input history during the session because I literally just typed `sage`
> on the command line and it failed.  I use conda frequently, and don't 
> usually
> have problems, so I doubt that it's anything very specific to my setup.
>
> Both 3.6 and 2.7 fail in the same way: there's a missing symbol from some
> dylib.  The symbol is
>
> __ZNSt3__16vectorIN5GiNaC2exENS_9allocatorIS2_EEE10deallocateEv
>
> which demangles to
>
> std::__1::vector 
> >::deallocate()
>
> So I guess that's not getting included in lib, somehow.  The full report
> for 2.7 is attached — though the 3.6 report is essentially identical.
>
> I've searched through every dylib that conda installs in envs/sage/lib, and
> the only similar symbol I find is
>
> __ZNSt3__16vectorIN5GiNaC2exENS_9allocatorIS2_EEE13__vdeallocateEv
>
> which is in libpynac.dylib -> libpynac.18.dylib, and demangles to
>
> std::__1::vector 
> >::__vdeallocate()
>
> I wonder if it's related to https://github.com/pynac/pynac/issues/239.
>
> I appreciate any help you can give me.  Thanks!
>
>

-- 
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/91a9d244-f818-46bc-b156-a8824c5e4ec6%40googlegroups.com.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

your reports says at the end:

ImportError: 
/home/katsu95i/anaconda3/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3:
 
undefined symbol: libiconv 


do you have libiconv installed?
If not, it's a missing dependence in the conda build, so you can install 
it, and then sage should work...


On Monday, August 27, 2018 at 2:54:42 PM UTC+2, kats...@gmail.com wrote:
>
> mail -s 'Sage Crash Report' sage-s...@googlegroups.com  < 
> /home/katsu95i/.sage/ipython-5.0.0/Sage_crash_report.txt 
>
>  information about: 
> - The operating system: Ubuntu 18.04 64-bit 
> - How Sage was installed: conda isntall -c conda-forge sage 
> - How to reproduce the crash: $ sage 
>
> *** 
>
>
> IPython post-mortem report 
>
> {'commit_hash': '033ab93c7', 
>  'commit_source': 'installation', 
>  'default_encoding': 'UTF-8', 
>  'ipython_path': 
> '/home/katsu95i/anaconda3/lib/python3.6/site-packages/IPython', 
>  'ipython_version': '5.8.0', 
>  'os_name': 'posix', 
>  'platform': 'Linux-4.16.12-041612-generic-x86_64-with-debian-buster-sid', 
>  'sys_executable': '/home/katsu95i/anaconda3/bin/sage-python23', 
>  'sys_platform': 'linux', 
>  'sys_version': '3.6.6 |Anaconda custom (64-bit)| (default, Jun 28 2018, ' 
> '17:14:51) \n' 
> '[GCC 7.2.0]'} 
>
> *** 
>
>
>
>
> *** 
>
>
> Crash traceback: 
>
> --- 
>
> --- 
>
> ImportErrorPython 3.6.6: 
> /home/katsu95i/anaconda3/bin/sage-python23 
>Mon Aug 27 21:45:26 
> 2018 
> A problem occurred executing Python code.  Here is the sequence of 
> function 
> calls leading up to the error, with the most recent (innermost) call last. 
> /home/katsu95i/anaconda3/bin/sage-ipython in () 
>   1 #!/usr/bin/env sage-python23 
>   2 # -*- coding: utf-8 -*- 
>   3 """ 
>   4 Sage IPython startup script. 
>   5 """ 
>   6 
>   7 # Display startup banner. Do this before anything else to give the 
> user 
>   8 # early feedback that Sage is starting. 
>   9 from sage.misc.banner import banner 
>  10 banner() 
>  11 
>  12 from sage.repl.interpreter import SageTerminalApp 
>  13 
>  14 app = SageTerminalApp.instance() 
> ---> 15 app.initialize() 
> global app.initialize =  TerminalIPythonApp.initialize of 
> > 
>  16 app.start() 
>
>  in 
> initialize(self=, 
> argv=None) 
>
> /home/katsu95i/anaconda3/lib/python3.6/site-packages/traitlets/config/application.py
>  
>
> in catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={}) 
>  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False 
>  73 else: 
>  74 raise ValueError("Unsupported value for environment 
> variable: 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to 
> '%s' which is none of  {'0', '1', 'false', 'true', ''}."% _envvar ) 
>  75 
>  76 
>  77 @decorator 
>  78 def catch_config_error(method, app, *args, **kwargs): 
>  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init. 
>  80 
>  81 On a TraitError (generally caused by bad config), this 
> will print the trait's 
>  82 message, and exit the app. 
>  83 
>  84 For use on init methods, to prevent invoking excepthook on 
> invalid input. 
>  85 """ 
>  86 try: 
> ---> 87 return method(app, *args, **kwargs) 
> method =  0x7f999f94e730> 
> app =  0x7f99a673d588> 
> args = (None,) 
> kwargs = {} 
>  88 except (TraitError, ArgumentError) as e: 
>  89 app.print_help() 
>  90 app.log.fatal("Bad config encountered during 
> initialization:") 
>  91 app.log.fatal(str(e)) 
>  92 app.log.debug("Config at the time: %s", app.config) 
>  93 app.exit(1) 
>  94 
>  95 
>  96 class ApplicationError(Exception): 
>  97 pass 
>  98 
>  99 
> 100 class LevelFormatter(logging.Formatter): 
> 101 """Formatter with additional `highlevel` record 
> 102 
>
> /home/katsu95i/anaconda3/lib/python3.6/site-packages/IPython/terminal/ipapp.py
>  
>
> in initialize(self=, 
> argv=None) 
> 301 
> 302 return super(TerminalIPythonApp, 
> self).parse_command_line(argv) 
> 303 
> 304 @catch_config_error 
> 305 def initialize(self, argv=None): 
> 306 """Do actions after construct, but before starting the 
> app.""" 
> 307 super(TerminalIPythonApp, self).initialize(argv) 
> 308 if self.subapp is not None: 
> 309 # don't 

Re: [sage-support] Re: Sage crash report

[Maxim Leyenson]

Дмитрий, спасибо огромное.

Установка python2-cypari2 решила проблему.

Пишу Вам по-русски, потому что слышал Ваше имя раньше.

Добрый вечер. Максим.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report

[Dima Pasechnik]

On Sunday, August 26, 2018 at 12:51:28 PM UTC+2, Maxim Leyenson wrote:
>
> Dear friends, 
>
> I would appreciate help with the following crash report (in the 
> attachment) 
>
> a few details: 
>
> * first run of Sage; 
>
> * System: Fedora 28, 64 bit 
>
> * Sage source: Fedora repository, 
> Sage 8.0-2.fc28 
>

is it this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1464520
 ?

the suggested there workaround is 

dnf -y install python2-cypari2



> * $ uname -a 
>
> Linux toucan 4.17.3-200.fc28.x86_64 #1 SMP Tue Jun 26 14:17:07 UTC 
> 2018 x86_64 x86_64 x86_64 GNU/Linux 
>
> Thank you 
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[slelievre]

Sat 2018-03-10 11:29:34 UTC, Alasdair:
>
> As created just now.  Enjoy!
>
> -Alasdair
>
> -- 
> facebook twitter wordpress linkedin google+


What is the operating system, and what version of it?
How was Sage installed? What led to the crash?

The crash report ends with this piece of information:

ImportError: libvpx.so.4: cannot open shared object file:
No such file or directory

Maybe ffmpeg was installed with libvpx support (which allows to use
the VP8 / VP9 video codecs)? One way to solve the problem might
be to just install libvpx and libvpx-dev.

Under GNU/Linux distributions, you should be able to install
those using the distribution's package manager. Under Ubuntu:

sudo apt install libvpx-dev

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dillon Ethier]

Yeah, I traced it to my .bash_aliases file and commented it out so it won't 
be causing me any more problems.

On Tuesday, February 20, 2018 at 5:42:16 PM UTC-5, Dima Pasechnik wrote:
>
>
>
> On Tuesday, February 20, 2018 at 7:26:25 PM UTC, Dillon Ethier wrote:
>>
>> Alright, I unset LD_LIBRARY_PATH and changed PATH to 
>> /usr/sbin:/usr/bin:/sbin:/bin:/ then rebuilt it, and it worked. I reran the 
>> tests and only one doctest failed. To check, I rebooted and tried again, 
>> causing a crash. But LD_LIBRARY_PATH and PATH had reinitialized to their 
>> previous values.
>>
>
> it is because they are set in a (hidden) config file, such as ~/.bashrc or 
> ~/.bash_profile
> (which in turn might source more config data from /etc/bash/bashrc (it 
> differs from one Linux distro to another how these
> files are exactly named)
>
> No need to reboot after changing these, loggin out/logging in again should 
> be more than enough
> (often merely sourcing the updates suffice) 
>
>  
>
>> I unset LD_LIBRARY_PATH and now it works, so the problem must be with 
>> that variable specifically. Thank you so much for your patience and help!
>>
>> On Tuesday, February 20, 2018 at 11:14:50 AM UTC-5, Dima Pasechnik wrote:
>>>
>>> I bet you have stuff in /usr/local/lib (to which your LD_LIBRARY_PATH is 
>>> pointing to) that is problematic.
>>> Unset it and try again.
>>>
>>> Also, I'd remove /usr/local/* things from the PATH
>>>
>>> On Tuesday, February 20, 2018 at 4:11:16 PM UTC, Dillon Ethier wrote:

 I uninstalled Anaconda completely and I can't find any relevent vars 
 sticking around but the problem persists.
 This is the output of 'env':

 CLUTTER_IM_MODULE=xim
 LC_ALL=en_US.UTF-8
 LD_LIBRARY_PATH=.:/usr/local/lib

 LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
 LESSCLOSE=/usr/bin/lesspipe %s %s
 TERMINATOR_UUID=urn:uuid:6eb55745-6a99-427c-875e-7a590077cafb
 XDG_MENU_PREFIX=gnome-
 LANG=en_US.UTF-8
 DISPLAY=:0
 GNOME_SHELL_SESSION_MODE=ubuntu
 COLORTERM=truecolor
 ZEITGEIST_DATA_PATH=/home/dillon/.local/share/zeitgeist
 USERNAME=dillon
 XDG_VTNR=2
 GIO_LAUNCHED_DESKTOP_FILE_PID=32694
 SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
 XDG_SESSION_ID=9
 USER=dillon
 DESKTOP_SESSION=ubuntu
 QT4_IM_MODULE=xim
 TEXTDOMAINDIR=/usr/share/locale/
 WAYLAND_DISPLAY=wayland-0
 PWD=/home/dillon
 HOME=/home/dillon
 JOURNAL_STREAM=9:391383
 TEXTDOMAIN=im-config
 XDG_SESSION_TYPE=wayland

 XDG_DATA_DIRS=/usr/share/ubuntu:/home/dillon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
 TERMINATOR_DBUS_NAME=net.tenshu.Terminator20x20309d54defed5d4
 XDG_SESSION_DESKTOP=ubuntu
 GJS_DEBUG_OUTPUT=stderr
 TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
 TERM=xterm-256color
 SHELL=/bin/bash
 VTE_VERSION=4804
 QT_IM_MODULE=ibus
 XMODIFIERS=@im=ibus
 IM_CONFIG_PHASE=2
 XDG_CURRENT_DESKTOP=ubuntu:GNOME

 GIO_LAUNCHED_DESKTOP_FILE=/home/dillon/.local/share/applications/x-terminal-emulator.desktop
 XDG_SEAT=seat0
 SHLVL=3
 LANGUAGE=en_US.UTF-8
 GDMSESSION=ubuntu
 GNOME_DESKTOP_SESSION_ID=this-is-deprecated
 LOGNAME=dillon
 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
 XDG_RUNTIME_DIR=/run/user/1000
 XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

 

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

On Tuesday, February 20, 2018 at 7:26:25 PM UTC, Dillon Ethier wrote:
>
> Alright, I unset LD_LIBRARY_PATH and changed PATH to 
> /usr/sbin:/usr/bin:/sbin:/bin:/ then rebuilt it, and it worked. I reran the 
> tests and only one doctest failed. To check, I rebooted and tried again, 
> causing a crash. But LD_LIBRARY_PATH and PATH had reinitialized to their 
> previous values.
>

it is because they are set in a (hidden) config file, such as ~/.bashrc or 
~/.bash_profile
(which in turn might source more config data from /etc/bash/bashrc (it 
differs from one Linux distro to another how these
files are exactly named)

No need to reboot after changing these, loggin out/logging in again should 
be more than enough
(often merely sourcing the updates suffice) 

 

> I unset LD_LIBRARY_PATH and now it works, so the problem must be with that 
> variable specifically. Thank you so much for your patience and help!
>
> On Tuesday, February 20, 2018 at 11:14:50 AM UTC-5, Dima Pasechnik wrote:
>>
>> I bet you have stuff in /usr/local/lib (to which your LD_LIBRARY_PATH is 
>> pointing to) that is problematic.
>> Unset it and try again.
>>
>> Also, I'd remove /usr/local/* things from the PATH
>>
>> On Tuesday, February 20, 2018 at 4:11:16 PM UTC, Dillon Ethier wrote:
>>>
>>> I uninstalled Anaconda completely and I can't find any relevent vars 
>>> sticking around but the problem persists.
>>> This is the output of 'env':
>>>
>>> CLUTTER_IM_MODULE=xim
>>> LC_ALL=en_US.UTF-8
>>> LD_LIBRARY_PATH=.:/usr/local/lib
>>>
>>> LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
>>> LESSCLOSE=/usr/bin/lesspipe %s %s
>>> TERMINATOR_UUID=urn:uuid:6eb55745-6a99-427c-875e-7a590077cafb
>>> XDG_MENU_PREFIX=gnome-
>>> LANG=en_US.UTF-8
>>> DISPLAY=:0
>>> GNOME_SHELL_SESSION_MODE=ubuntu
>>> COLORTERM=truecolor
>>> ZEITGEIST_DATA_PATH=/home/dillon/.local/share/zeitgeist
>>> USERNAME=dillon
>>> XDG_VTNR=2
>>> GIO_LAUNCHED_DESKTOP_FILE_PID=32694
>>> SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
>>> XDG_SESSION_ID=9
>>> USER=dillon
>>> DESKTOP_SESSION=ubuntu
>>> QT4_IM_MODULE=xim
>>> TEXTDOMAINDIR=/usr/share/locale/
>>> WAYLAND_DISPLAY=wayland-0
>>> PWD=/home/dillon
>>> HOME=/home/dillon
>>> JOURNAL_STREAM=9:391383
>>> TEXTDOMAIN=im-config
>>> XDG_SESSION_TYPE=wayland
>>>
>>> XDG_DATA_DIRS=/usr/share/ubuntu:/home/dillon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
>>> TERMINATOR_DBUS_NAME=net.tenshu.Terminator20x20309d54defed5d4
>>> XDG_SESSION_DESKTOP=ubuntu
>>> GJS_DEBUG_OUTPUT=stderr
>>> TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
>>> TERM=xterm-256color
>>> SHELL=/bin/bash
>>> VTE_VERSION=4804
>>> QT_IM_MODULE=ibus
>>> XMODIFIERS=@im=ibus
>>> IM_CONFIG_PHASE=2
>>> XDG_CURRENT_DESKTOP=ubuntu:GNOME
>>>
>>> GIO_LAUNCHED_DESKTOP_FILE=/home/dillon/.local/share/applications/x-terminal-emulator.desktop
>>> XDG_SEAT=seat0
>>> SHLVL=3
>>> LANGUAGE=en_US.UTF-8
>>> GDMSESSION=ubuntu
>>> GNOME_DESKTOP_SESSION_ID=this-is-deprecated
>>> LOGNAME=dillon
>>> DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
>>> XDG_RUNTIME_DIR=/run/user/1000
>>> XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
>>>
>>> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>>> GJS_DEBUG_TOPICS=JS ERROR;JS LOG
>>>
>>> SESSION_MANAGER=local/lappy:@/tmp/.ICE-unix/31985,unix/lappy:/tmp/.ICE-unix/31985
>>> LESSOPEN=| /usr/bin/lesspipe %s
>>> GTK_IM_MODULE=ibus
>>> _=/usr/bin/env
>>> OLDPWD=/home/dillon/.cache
>>>
>>> I'm considering reinstalling the OS 

[sage-support] Re: Sage Crash Report

[Dillon Ethier]

Alright, I unset LD_LIBRARY_PATH and changed PATH to 
/usr/sbin:/usr/bin:/sbin:/bin:/ then rebuilt it, and it worked. I reran the 
tests and only one doctest failed. To check, I rebooted and tried again, 
causing a crash. But LD_LIBRARY_PATH and PATH had reinitialized to their 
previous values. I unset LD_LIBRARY_PATH and now it works, so the problem 
must be with that variable specifically. Thank you so much for your 
patience and help!

On Tuesday, February 20, 2018 at 11:14:50 AM UTC-5, Dima Pasechnik wrote:
>
> I bet you have stuff in /usr/local/lib (to which your LD_LIBRARY_PATH is 
> pointing to) that is problematic.
> Unset it and try again.
>
> Also, I'd remove /usr/local/* things from the PATH
>
> On Tuesday, February 20, 2018 at 4:11:16 PM UTC, Dillon Ethier wrote:
>>
>> I uninstalled Anaconda completely and I can't find any relevent vars 
>> sticking around but the problem persists.
>> This is the output of 'env':
>>
>> CLUTTER_IM_MODULE=xim
>> LC_ALL=en_US.UTF-8
>> LD_LIBRARY_PATH=.:/usr/local/lib
>>
>> LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
>> LESSCLOSE=/usr/bin/lesspipe %s %s
>> TERMINATOR_UUID=urn:uuid:6eb55745-6a99-427c-875e-7a590077cafb
>> XDG_MENU_PREFIX=gnome-
>> LANG=en_US.UTF-8
>> DISPLAY=:0
>> GNOME_SHELL_SESSION_MODE=ubuntu
>> COLORTERM=truecolor
>> ZEITGEIST_DATA_PATH=/home/dillon/.local/share/zeitgeist
>> USERNAME=dillon
>> XDG_VTNR=2
>> GIO_LAUNCHED_DESKTOP_FILE_PID=32694
>> SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
>> XDG_SESSION_ID=9
>> USER=dillon
>> DESKTOP_SESSION=ubuntu
>> QT4_IM_MODULE=xim
>> TEXTDOMAINDIR=/usr/share/locale/
>> WAYLAND_DISPLAY=wayland-0
>> PWD=/home/dillon
>> HOME=/home/dillon
>> JOURNAL_STREAM=9:391383
>> TEXTDOMAIN=im-config
>> XDG_SESSION_TYPE=wayland
>>
>> XDG_DATA_DIRS=/usr/share/ubuntu:/home/dillon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
>> TERMINATOR_DBUS_NAME=net.tenshu.Terminator20x20309d54defed5d4
>> XDG_SESSION_DESKTOP=ubuntu
>> GJS_DEBUG_OUTPUT=stderr
>> TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
>> TERM=xterm-256color
>> SHELL=/bin/bash
>> VTE_VERSION=4804
>> QT_IM_MODULE=ibus
>> XMODIFIERS=@im=ibus
>> IM_CONFIG_PHASE=2
>> XDG_CURRENT_DESKTOP=ubuntu:GNOME
>>
>> GIO_LAUNCHED_DESKTOP_FILE=/home/dillon/.local/share/applications/x-terminal-emulator.desktop
>> XDG_SEAT=seat0
>> SHLVL=3
>> LANGUAGE=en_US.UTF-8
>> GDMSESSION=ubuntu
>> GNOME_DESKTOP_SESSION_ID=this-is-deprecated
>> LOGNAME=dillon
>> DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
>> XDG_RUNTIME_DIR=/run/user/1000
>> XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
>>
>> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>> GJS_DEBUG_TOPICS=JS ERROR;JS LOG
>>
>> SESSION_MANAGER=local/lappy:@/tmp/.ICE-unix/31985,unix/lappy:/tmp/.ICE-unix/31985
>> LESSOPEN=| /usr/bin/lesspipe %s
>> GTK_IM_MODULE=ibus
>> _=/usr/bin/env
>> OLDPWD=/home/dillon/.cache
>>
>> I'm considering reinstalling the OS in order to get this to work again.
>>
>>
>> On Tuesday, February 20, 2018 at 3:11:23 AM UTC-5, Dima Pasechnik wrote:
>>>
>>> most probably you have a conflict with Anaconda installation. Unset all 
>>> the relevant to Anaconda env. vars before rebuilding Sage.
>>
>>

-- 
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 post to this group, send email to 

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

I bet you have stuff in /usr/local/lib (to which your LD_LIBRARY_PATH is 
pointing to) that is problematic.
Unset it and try again.

Also, I'd remove /usr/local/* things from the PATH

On Tuesday, February 20, 2018 at 4:11:16 PM UTC, Dillon Ethier wrote:
>
> I uninstalled Anaconda completely and I can't find any relevent vars 
> sticking around but the problem persists.
> This is the output of 'env':
>
> CLUTTER_IM_MODULE=xim
> LC_ALL=en_US.UTF-8
> LD_LIBRARY_PATH=.:/usr/local/lib
>
> LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
> LESSCLOSE=/usr/bin/lesspipe %s %s
> TERMINATOR_UUID=urn:uuid:6eb55745-6a99-427c-875e-7a590077cafb
> XDG_MENU_PREFIX=gnome-
> LANG=en_US.UTF-8
> DISPLAY=:0
> GNOME_SHELL_SESSION_MODE=ubuntu
> COLORTERM=truecolor
> ZEITGEIST_DATA_PATH=/home/dillon/.local/share/zeitgeist
> USERNAME=dillon
> XDG_VTNR=2
> GIO_LAUNCHED_DESKTOP_FILE_PID=32694
> SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
> XDG_SESSION_ID=9
> USER=dillon
> DESKTOP_SESSION=ubuntu
> QT4_IM_MODULE=xim
> TEXTDOMAINDIR=/usr/share/locale/
> WAYLAND_DISPLAY=wayland-0
> PWD=/home/dillon
> HOME=/home/dillon
> JOURNAL_STREAM=9:391383
> TEXTDOMAIN=im-config
> XDG_SESSION_TYPE=wayland
>
> XDG_DATA_DIRS=/usr/share/ubuntu:/home/dillon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
> TERMINATOR_DBUS_NAME=net.tenshu.Terminator20x20309d54defed5d4
> XDG_SESSION_DESKTOP=ubuntu
> GJS_DEBUG_OUTPUT=stderr
> TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
> TERM=xterm-256color
> SHELL=/bin/bash
> VTE_VERSION=4804
> QT_IM_MODULE=ibus
> XMODIFIERS=@im=ibus
> IM_CONFIG_PHASE=2
> XDG_CURRENT_DESKTOP=ubuntu:GNOME
>
> GIO_LAUNCHED_DESKTOP_FILE=/home/dillon/.local/share/applications/x-terminal-emulator.desktop
> XDG_SEAT=seat0
> SHLVL=3
> LANGUAGE=en_US.UTF-8
> GDMSESSION=ubuntu
> GNOME_DESKTOP_SESSION_ID=this-is-deprecated
> LOGNAME=dillon
> DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
> XDG_RUNTIME_DIR=/run/user/1000
> XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
> GJS_DEBUG_TOPICS=JS ERROR;JS LOG
>
> SESSION_MANAGER=local/lappy:@/tmp/.ICE-unix/31985,unix/lappy:/tmp/.ICE-unix/31985
> LESSOPEN=| /usr/bin/lesspipe %s
> GTK_IM_MODULE=ibus
> _=/usr/bin/env
> OLDPWD=/home/dillon/.cache
>
> I'm considering reinstalling the OS in order to get this to work again.
>
>
> On Tuesday, February 20, 2018 at 3:11:23 AM UTC-5, Dima Pasechnik wrote:
>>
>> most probably you have a conflict with Anaconda installation. Unset all 
>> the relevant to Anaconda env. vars before rebuilding Sage.
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dillon Ethier]

I uninstalled Anaconda completely and I can't find any relevent vars 
sticking around but the problem persists.
This is the output of 'env':

CLUTTER_IM_MODULE=xim
LC_ALL=en_US.UTF-8
LD_LIBRARY_PATH=.:/usr/local/lib
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
LESSCLOSE=/usr/bin/lesspipe %s %s
TERMINATOR_UUID=urn:uuid:6eb55745-6a99-427c-875e-7a590077cafb
XDG_MENU_PREFIX=gnome-
LANG=en_US.UTF-8
DISPLAY=:0
GNOME_SHELL_SESSION_MODE=ubuntu
COLORTERM=truecolor
ZEITGEIST_DATA_PATH=/home/dillon/.local/share/zeitgeist
USERNAME=dillon
XDG_VTNR=2
GIO_LAUNCHED_DESKTOP_FILE_PID=32694
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
XDG_SESSION_ID=9
USER=dillon
DESKTOP_SESSION=ubuntu
QT4_IM_MODULE=xim
TEXTDOMAINDIR=/usr/share/locale/
WAYLAND_DISPLAY=wayland-0
PWD=/home/dillon
HOME=/home/dillon
JOURNAL_STREAM=9:391383
TEXTDOMAIN=im-config
XDG_SESSION_TYPE=wayland
XDG_DATA_DIRS=/usr/share/ubuntu:/home/dillon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
TERMINATOR_DBUS_NAME=net.tenshu.Terminator20x20309d54defed5d4
XDG_SESSION_DESKTOP=ubuntu
GJS_DEBUG_OUTPUT=stderr
TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
TERM=xterm-256color
SHELL=/bin/bash
VTE_VERSION=4804
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus
IM_CONFIG_PHASE=2
XDG_CURRENT_DESKTOP=ubuntu:GNOME
GIO_LAUNCHED_DESKTOP_FILE=/home/dillon/.local/share/applications/x-terminal-emulator.desktop
XDG_SEAT=seat0
SHLVL=3
LANGUAGE=en_US.UTF-8
GDMSESSION=ubuntu
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
LOGNAME=dillon
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
XDG_RUNTIME_DIR=/run/user/1000
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
GJS_DEBUG_TOPICS=JS ERROR;JS LOG
SESSION_MANAGER=local/lappy:@/tmp/.ICE-unix/31985,unix/lappy:/tmp/.ICE-unix/31985
LESSOPEN=| /usr/bin/lesspipe %s
GTK_IM_MODULE=ibus
_=/usr/bin/env
OLDPWD=/home/dillon/.cache

I'm considering reinstalling the OS in order to get this to work again.


On Tuesday, February 20, 2018 at 3:11:23 AM UTC-5, Dima Pasechnik wrote:
>
> most probably you have a conflict with Anaconda installation. Unset all 
> the relevant to Anaconda env. vars before rebuilding Sage.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

most probably you have a conflict with Anaconda installation. Unset all the 
relevant to Anaconda env. vars before rebuilding Sage.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dillon Ethier]

Initially I had never set the SAGE_ROOT variable or any of the build 
variables other than MAKE, and it worked fine. I only changed it afterward 
in order to get Jupyter(anaconda) to recognize the kernel. I have tried 
setting SAGE_ROOT to be /home/dillon/sage-8.1 and rebuilding but the 
problem persists- it keeps choking on this "mfinteg" thing. I can't find 
any information on it through Google.

On Monday, February 19, 2018 at 11:44:05 AM UTC-5, Dima Pasechnik wrote:
>
> Your log says that your Sage installation is in /home/dillon/sage-8.1
> I guess you might want to set it as SAGE_ROOT
>
> On Monday, February 19, 2018 at 3:25:04 AM UTC, Dillon Ethier wrote:
>>
>> Hello,
>>
>> I recently built Sage on my laptop running Ubuntu 17.10 (x86 - 64 bit). 
>> It worked perfectly, and successfully ran all of the basic tests (I never 
>> ran the long tests). I tried to start it up today and it wouldn't work, 
>> because it said it could not find the directory that I had set as SAGE_ROOT 
>> (I don't remember exactly what it was set as, I think maybe /usr/bin/sage 
>> or something like that), and indeed this directory no longer existed. I 
>> tried to rebuild Sage in order to fix the issue, and it hasn't worked since
>> Every time I try to start Sage, it crashes immediately. I get this error 
>> that seems to be coming from Pari somewhere but the error messages are 
>> baffling to me. I've tried rebuilding multiple times and nothing helps. I 
>> guess what I'm trying to say is that I KNOW that it's possible for Sage to 
>> work on my machine, as I had already done it. I just can't figure out what 
>> got broken or how to fix it. Any help would be much appreciated.
>>
>> Thanks,
>>
>> Dillon Ethier
>>
>>
>>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

Your log says that your Sage installation is in /home/dillon/sage-8.1
I guess you might want to set it as SAGE_ROOT

On Monday, February 19, 2018 at 3:25:04 AM UTC, Dillon Ethier wrote:
>
> Hello,
>
> I recently built Sage on my laptop running Ubuntu 17.10 (x86 - 64 bit). It 
> worked perfectly, and successfully ran all of the basic tests (I never ran 
> the long tests). I tried to start it up today and it wouldn't work, because 
> it said it could not find the directory that I had set as SAGE_ROOT (I 
> don't remember exactly what it was set as, I think maybe /usr/bin/sage or 
> something like that), and indeed this directory no longer existed. I tried 
> to rebuild Sage in order to fix the issue, and it hasn't worked since
> Every time I try to start Sage, it crashes immediately. I get this error 
> that seems to be coming from Pari somewhere but the error messages are 
> baffling to me. I've tried rebuilding multiple times and nothing helps. I 
> guess what I'm trying to say is that I KNOW that it's possible for Sage to 
> work on my machine, as I had already done it. I just can't figure out what 
> got broken or how to fix it. Any help would be much appreciated.
>
> Thanks,
>
> Dillon Ethier
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Volker Braun]

Looks like you used the Sage binary on Fedora 25; That apparently won't 
work and you need a more recent Fedora version. 

As a side note: Fedora 25 is EOL, so no more security fixes etc...



On Friday, December 29, 2017 at 4:15:09 AM UTC+1, rj wrote:
>
>
>
> IPython post-mortem report
>
> {'commit_hash': u'5c9c918',
>  'commit_source': 'installation',
>  'default_encoding': 'UTF-8',
>  'ipython_path': 
> '/home/rjoshua/Downloads/SageMath/local/lib/python2.7/site-pac\
> kages/IPython',
>  'ipython_version': '5.1.0',
>  'os_name': 'posix',
>  'platform': 
> 'Linux-4.8.6-300.fc25.x86_64-x86_64-with-fedora-25-Twenty_Five',
>  'sys_executable': '/home/rjoshua/Downloads/SageMath/local/bin/python',
>  'sys_platform': 'linux2',
>  'sys_version': '2.7.13 (default, Mar 26 2017, 18:34:22) \n[GCC 6.3.1 
> 20161221 \
> (Red Hat 6.3.1-1)]'}
>
> ***
> Crash traceback:
>
> ---
> ---
> ImportErrorPython 2.7.13: /home/rjoshua/Downloads/SageMath/local/bin/python
>Thu Dec 28 22:03:45 2017
> A problem occurred executing Python code.  Here is the sequence of function
> calls leading up to the error, with the most recent (innermost) call last.
> /home/rjoshua/Downloads/SageMath/src/bin/sage-ipython in ()
>   1 #!/usr/bin/env python
>   2 # -*- coding: utf-8 -*-
>   3 """
>   4 Sage IPython startup script.
>   5 """
>   6
>   7 from sage.repl.interpreter import SageTerminalApp
>   8
>   9 app = SageTerminalApp.instance()
> ---> 10 app.initialize()
> global app.initialize =  of  e.repl.interpreter.SageTerminalApp object at 0x7ff3b3204050>>
>  11 app.start()
>
>  in 
> initialize(self= ject>, argv=None)
>
>
> /home/rjoshua/Downloads/SageMath/local/lib/python2.7/site-packages/traitlets/con\
> fig/application.pyc in catch_config_error(method=, 
> app= e.repl.interpreter.SageTerminalApp object>, *args=(None,), **kwargs={})
>  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
>  73 else:
>  74 raise ValueError("Unsupported value for environment variable: 
> 'TRAIT\
> LETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is none of  
> {'0',\
>  '1', 'false', 'true', ''}."% _envvar )
>  75
> 78 def catch_config_error(method, app, *args, **kwargs):
>  79 """Method decorator for catching invalid config 
> (Trait/ArgumentError\
> s) during init.
>  80
>  81 On a TraitError (generally caused by bad config), this will 
> print th\
> e trait's
>  82 message, and exit the app.
>  83
>  84 For use on init methods, to prevent invoking excepthook on 
> invalid i\
> nput.
>  85 """
>  86 try:
> ---> 87 return method(app, *args, **kwargs)
> method = 
> app =  0x7ff3b3204050>
> args = (None,)
> kwargs = {}
>  88 except (TraitError, ArgumentError) as e:
>  89 app.print_help()
>  90 app.log.fatal("Bad config encountered during 
> initialization:")
>  91 app.log.fatal(str(e))
>  92 app.log.debug("Config at the time: %s", app.config)
>  93 app.exit(1)
>  94
>  95
>  96 class ApplicationError(Exception):
>  97 pass
>  98
>  99
> 100 class LevelFormatter(logging.Formatter):
> 101 """Formatter with additional `highlevel` record
> 102
>
> 294
> 296
> 297 @catch_config_error
> 298 def initialize(self, argv=None):
> 299 """Do actions after construct, but before starting the 
> app."""
> 300 super(TerminalIPythonApp, self).initialize(argv)
> 301 if self.subapp is not None:
> 302 # don't bother initializing further, starting subapp
> 303 return
> 304 # print self.extra_args
> 305 if self.extra_args and not self.something_to_run:
> 306 self.file_to_run = self.extra_args[0]
> 307 self.init_path()
> 308 # create the shell
> --> 309 self.init_shell()
> self.init_shell =   .interpreter.SageTerminalApp object at 0x7ff3b3204050>>
> 310 # and draw the banner
> 311 self.init_banner()
> 312 # Now a variety of things that happen after the banner is 
> printe\
> d.
> 313 self.init_gui_pylab()
> 314 self.init_extensions()
> 315 self.init_code()
> 316
> 317 def init_shell(self):
> 318 """initialize the InteractiveShell instance"""
> 319 # Create an InteractiveShell instance.
> 320 # shell.display_banner should always be False for the 
> terminal
> 321 # based app, because we call 

[sage-support] Re: Sage Crash Report

[Simon King]

Hi Dima,

On 2017-10-23, Dima Pasechnik  wrote:
>> ... which means that we should enhance our crash message (if there is any; 
>> I don't recall what I saw when Sage last crashed for me). 
>>
> if you like to refresh your experience, you might try various 2-liners from
> https://trac.sagemath.org/ticket/22766 :-)

OK, I see that there is no helpful message at all (even not a message
telling "please report at sage-devel").

Best regards,
Simon

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

On Monday, October 23, 2017 at 10:32:30 AM UTC+1, Simon King wrote:
>
> On 2017-10-23, Jeroen Demeyer  
> wrote: 
> > On 2017-10-22 21:01, Jan Groenewald wrote: 
> >> If you can email this file to the developers 
> > ...provided with information on how you installed Sage, what OS you are 
> > using, which version of Sage you are running, what command you ran when 
> > you got this error. 
> > 
> > Too many people think that a "Crash Report" is sufficient information. 
>
> ... which means that we should enhance our crash message (if there is any; 
> I don't recall what I saw when Sage last crashed for me). 
>
if you like to refresh your experience, you might try various 2-liners from
https://trac.sagemath.org/ticket/22766 :-)
 

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Simon King]

On 2017-10-23, Jeroen Demeyer  wrote:
> On 2017-10-22 21:01, Jan Groenewald wrote:
>> If you can email this file to the developers
> ...provided with information on how you installed Sage, what OS you are 
> using, which version of Sage you are running, what command you ran when 
> you got this error.
>
> Too many people think that a "Crash Report" is sufficient information.

... which means that we should enhance our crash message (if there is any;
I don't recall what I saw when Sage last crashed for me).

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Nicolas Dero Miralles]

Thanks Dima for your help.

I successfully installed libgfortan however when compiling SageMath a new 
error appears in the crash report :
ImportError: /usr/lib/i386-linux-gnu/libstdc++.so.6: version 
`GLIBCXX_3.4.21' not found (required by 
/home/nicolas/SageMath/local/lib/libntl.so.33)

Could you help me ?

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

At the bottom of your log, one sees:


ImportError: libgfortran.so.3: cannot open shared object file: No such file or 
directory



Please install libgfortran (e.g. by installing gfortran), it will fix the 
problem.

On Tuesday, October 10, 2017 at 10:46:35 PM UTC+1, Nicolas Dero Miralles 
wrote:
>
>
>
> I have recently downloaded SageMath for educational purposes. However, I 
> faced problems while installing the software.
> I use Ubuntu 15.04 and when building binaries from the terminal the 
> installation seems to be almost completed when a message appears (in copy 
> you will find the crash report) :
>
> Oops, Sage crashed. We do our best to make it stable, but...
>
> A crash report was automatically generated with the following information:
>   - A verbatim copy of the crash traceback.
>   - A copy of your input history during this session.
>   - Data on your current Sage configuration.
>
> It was left in the file named:
> '/home/nicolas/.sage/ipython-5.0.0/Sage_crash_report.txt'
> If you can email this file to the developers, the information in it will 
> help
> them in understanding and correcting the problem.
>
> You can mail it to: sage-support at sage-s...@googlegroups.com 
> 
> with the subject 'Sage Crash Report'.
>
> If you want to do it now, the following command will work (under Unix):
> mail -s 'Sage Crash Report' sage-s...@googlegroups.com  < 
> /home/nicolas/.sage/ipython-5.0.0/Sage_crash_report.txt
>
> To ensure accurate tracking of this issue, please file a report about it 
> at:
> http://trac.sagemath.org
>
> Hit  to quit (your terminal may close):
>
>
> Thanking you in advance for your help.
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: 'Sage Crash Report

[Dima Pasechnik]

Are you on Fedora 26? Then it looks like this:

It looks like you hit this bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=1464520 

You need to install psutils: 
$ dnf install python2-psutil 

On Friday, October 6, 2017 at 4:34:09 PM UTC+1, Lee Duke wrote:
>
> *** 
>
>
> IPython post-mortem report 
>
> {'commit_hash': u'5c9c918', 
>   'commit_source': 'installation', 
>   'default_encoding': 'UTF-8', 
>   'ipython_path': '/usr/lib64/sagemath/site-packages/IPython', 
>   'ipython_version': '5.1.0', 
>   'os_name': 'posix', 
>   'platform': 
> 'Linux-4.12.9-300.fc26.x86_64-x86_64-with-fedora-26-Twenty_Six', 
>   'sys_executable': '/usr/lib64/sagemath/local/bin/python', 
>   'sys_platform': 'linux2', 
>   'sys_version': '2.7.13 (default, Sep  5 2017, 08:53:59) \n[GCC 7.1.1 
> 20170622 (Red Hat 7.1.1-3)]'} 
>
> *** 
>
>
>
>
> *** 
>
>
> Crash traceback: 
>
> --- 
>
> --- 
>
> ImportError Python 2.7.13: 
> /usr/lib64/sagemath/local/bin/python 
> Fri Oct  6 11:28:35 
> 2017 
> A problem occurred executing Python code.  Here is the sequence of 
> function 
> calls leading up to the error, with the most recent (innermost) call last. 
> /usr/lib64/sagemath/local/bin/sage-ipython in () 
>1 #!/usr/bin/env python 
>2 # -*- coding: utf-8 -*- 
>3 """ 
>4 Sage IPython startup script. 
>5 """ 
>6 
>7 from sage.repl.interpreter import SageTerminalApp 
>8 
>9 app = SageTerminalApp.instance() 
> ---> 10 app.initialize() 
>  global app.initialize =  SageTerminalApp.initialize of  object at 0x7f9a675e1290>> 
>   11 app.start() 
>
>  in 
> initialize(self=, argv=None) 
>
> /usr/lib/python2.7/site-packages/traitlets/config/application.pyc in 
> catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={}) 
>   72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False 
>   73 else: 
>   74 raise ValueError("Unsupported value for environment 
> variable: 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' 
> which is none of  {'0', '1', 'false', 'true', ''}."% _envvar ) 
>   75 
>   76 
>   77 @decorator 
>   78 def catch_config_error(method, app, *args, **kwargs): 
>   79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init. 
>   80 
>   81 On a TraitError (generally caused by bad config), this will 
> print the trait's 
>   82 message, and exit the app. 
>   83 
>   84 For use on init methods, to prevent invoking excepthook on 
> invalid input. 
>   85 """ 
>   86 try: 
> ---> 87 return method(app, *args, **kwargs) 
>  method =  
>  app =  0x7f9a675e1290> 
>  args = (None,) 
>  kwargs = {} 
>   88 except (TraitError, ArgumentError) as e: 
>   89 app.print_help() 
>   90 app.log.fatal("Bad config encountered during 
> initialization:") 
>   91 app.log.fatal(str(e)) 
>   92 app.log.debug("Config at the time: %s", app.config) 
>   93 app.exit(1) 
>   94 
>   95 
>   96 class ApplicationError(Exception): 
>   97 pass 
>   98 
>   99 
>  100 class LevelFormatter(logging.Formatter): 
>  101 """Formatter with additional `highlevel` record 
>  102 
>
> /usr/lib64/sagemath/site-packages/IPython/terminal/ipapp.pyc in 
> initialize(self=, argv=None) 
>  294 
>  295 return super(TerminalIPythonApp, 
> self).parse_command_line(argv) 
>  296 
>  297 @catch_config_error 
>  298 def initialize(self, argv=None): 
>  299 """Do actions after construct, but before starting the 
> app.""" 
>  300 super(TerminalIPythonApp, self).initialize(argv) 
>  301 if self.subapp is not None: 
>  302 # don't bother initializing further, starting subapp 
>  303 return 
>  304 # print self.extra_args 
>  305 if self.extra_args and not self.something_to_run: 
>  306 self.file_to_run = self.extra_args[0] 
>  307 self.init_path() 
>  308 # create the shell 
> --> 309 self.init_shell() 
>  self.init_shell =  > 
>  310 # and draw the banner 
>  311 self.init_banner() 
>  312 # Now a variety of things that happen after the banner 
> is printed. 
>  313 self.init_gui_pylab() 
>  314 self.init_extensions() 
>  315 self.init_code() 

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

It's not clear how you're installing Sage. You are running Ubuntu 17 and it 
appears that you are installing an Ubuntu package of some sort, but how 
exactly?

On Wednesday, September 27, 2017 at 6:58:29 PM UTC+1, The Geeko wrote:
>
> I'm having problems with new installation of Sage... 
>
> Chris "Kam" McIntosh
> aka Kam McIntosh 'I'i
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

On Friday, September 1, 2017 at 10:32:17 PM UTC+1, Назар Зибилюк wrote:

at the bottom of the log one sees

ImportError: No module named psutil


Also, it appears to be Sage 7.6 on Fedora 26.


First,  try
 
sudo dnf install python2-psutil

--- I'm not sure whether Sage uses system's Python2, or a
special version of Python2...


If this does not help, then 


sudo sage --pip install psutil


ought to do the job.


HTH

Dima


 

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[slelievre]

On Tuesday, August 15, 2017 at 9:49:35 PM UTC-7, William wrote:

> On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri wrote:
>
>> One of the very last lines of the report says
>>
>>> ImportError: libgfortran.so.3: cannot open shared object file: No such 
file or directory
>>
>> You need to install gfortran on your computer.
>
> We should really build binaries that don't require fortran to be 
installed,
> or put in an error before Python even starts importing.
>
> I personally hit or saw the above crash report dozens of times recently,
> due to installing Sage binaries in various fairly minimal Docker 
containers.
> william

I opened Sage trac ticket #23753 to track this issue.
https://trac.sagemath.org/ticket/23753

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[slelievre]

2017-05-09 18:26:36 UTC+1, Abhishek Kesarwani:

>  trying to install sagemath on my ubuntu 17.04 it shows the following 
error:
>
> Oops, Sage crashed. We do our best to make it stable, but...

This might be because Sage requires gfortran to be installed.

Try installing gfortran by typing the following in a terminal:

sudo apt-get install gfortran

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[John H Palmieri]

On Tuesday, August 15, 2017 at 9:49:35 PM UTC-7, William wrote:
>
> On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri  > wrote:
>
>> One of the very last lines of the report says
>>
>>>
>>> ImportError: libgfortran.so.3: cannot open shared object file: No such file 
>>> or directory
>>>
>>>
>> You need to install gfortran on your computer.
>>
>
> We should really build binaries that don't require fortran to be 
> installed, or put in an error before Python even starts importing.
>

Yes, I agree.
 

>
> I personally hit or saw the above crash report dozens of times recently, 
> due to installing Sage binaries in various fairly minimal Docker containers.
>
> william
>
> -- 
> -- William Stein
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[William Stein]

On Tue, Aug 15, 2017 at 7:47 PM John H Palmieri 
wrote:

> One of the very last lines of the report says
>
>>
>> ImportError: libgfortran.so.3: cannot open shared object file: No such file 
>> or directory
>>
>>
> You need to install gfortran on your computer.
>

We should really build binaries that don't require fortran to be installed,
or put in an error before Python even starts importing.

I personally hit or saw the above crash report dozens of times recently,
due to installing Sage binaries in various fairly minimal Docker containers.

william

-- 
-- William Stein

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[John H Palmieri]

One of the very last lines of the report says

>
> ImportError: libgfortran.so.3: cannot open shared object file: No such file 
> or directory
>
>
You need to install gfortran on your computer.



On Tuesday, August 15, 2017 at 6:15:01 PM UTC-7, kats...@gmail.com wrote:
>
> Sage Crash Report
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report

[Silvio Reyes]

On Wednesday, December 21, 2016 at 2:14:17 PM UTC-5, leonel torres salinas 
wrote:
>
> Hello, i just wanted to try Sagemath in my computer
>
> Toshiba satellite l745d runing Fedora 25 with LXDE desktop
>
> I tried to execute it from the binaries but it wasn't enough for it
>
> Thank you for the support, i really enjoy your work
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

Hi,
how is Sage installed in your case?
It appears to be some pre-packaged binary installer, but which one?

The error is 
ImportError: No module named psutil


On Wednesday, July 19, 2017 at 2:15:59 AM UTC+1, Keivan Monfared wrote:
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[Grant Ellis]

Thanks! Grant

On Jul 18, 2017 9:29 AM, "Dima Pasechnik"  wrote:

> You need to have (lib)gfortran installed, see the bottom of your log:
>
> ImportError: libgfortran.so.3: cannot open shared object file: No such file 
> or directory
>
>
> On Tuesday, July 18, 2017 at 9:49:40 AM UTC+1, Grant Ellis wrote:
>>
>> ​Greetings:
>>
>> I originally had Anaconda3 installed on my Ubuntu 16.04 notebook and
>> could not get Sage to setup and run.
>>
>> I then uninstalled Anaconda3 and then reinstalled Sage.​  After the
>> re-installation then Sage crashed.
>>
>> Please help!
>>
>> Thanks and regards,
>>
>> Grant Ellis
>>
> --
> 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 post to this group, send email to sage-support@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

You need to have (lib)gfortran installed, see the bottom of your log:

ImportError: libgfortran.so.3: cannot open shared object file: No such file or 
directory


On Tuesday, July 18, 2017 at 9:49:40 AM UTC+1, Grant Ellis wrote:
>
> ​Greetings:
>
> I originally had Anaconda3 installed on my Ubuntu 16.04 notebook and could 
> not get Sage to setup and run.
>
> I then uninstalled Anaconda3 and then reinstalled Sage.​  After the 
> re-installation then Sage crashed.
>
> Please help!
>
> Thanks and regards, 
>
> Grant Ellis
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

It should be enough to run Sage in a shell session where PATH variable does not 
contain anything from /sw/.

(there may be more variable that might affect running Sage, although this is 
probably a bug then)

PS. it is true that Core2 duo is x86_64, but not all such CPUs are created 
equal. Different CPUs support different machine hardware commands, and 
compilers are able to use this to produce faster code, at expense of 
portability. This is why a binary distribution needs to use the most basic 
subset of machine commands to be useful on all x86_64s.


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[whit3rd]

On Wednesday, June 21, 2017 at 3:01:09 AM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Wednesday, June 21, 2017 at 9:04:12 AM UTC+1, whit3rd wrote:
>>
>> Seconds after install of version 7.6, on MacOS 10.11.6
>> on a MacBook Pro (Core 2 duo, 4GB RAM)
>>
>
> it might be that the executable you downloaded needs a better CPU (Core 2 
> duo is quite old...)
> What exactly have you installed, what file?
>
> It's "sage-7.6-OSX_10.11.6-x86_64.dmg" for the installer.

Core 2 is certainly  both x86 and 64-bit.   This CPU is 2.26 GHz, probably 
Penryn P8400 or SP9300
Apple MacBook Pro 5.5 is the machine designation
 

> As well, it might be that you have some kind of conflict with some stuff 
> in /sw/ you have in your PATH.
> Could you temporarily rename /sw/ and try again?
>

That works!  Don't see any reason there'd be conflict, though.  Sage 
doesn't put anything into /sw,
 but /sw overrides anyhow?

How might I restore the /sw directory and still keep Sage running?

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

On Wednesday, June 21, 2017 at 9:04:12 AM UTC+1, whit3rd wrote:
>
> Seconds after install of version 7.6, on MacOS 10.11.6
> on a MacBook Pro (Core 2 duo, 4GB RAM)
>

it might be that the executable you downloaded needs a better CPU (Core 2 
duo is quite old...)
What exactly have you installed, what file?

As well, it might be that you have some kind of conflict with some stuff in 
/sw/ you have in your PATH.
Could you temporarily rename /sw/ and try again?



> On initially installing Sage, there was one warning 
> ***
> /Applications/SageMath/src/bin/sage-env: line 291: /sw/bin/sed: Bad CPU 
> type in executable
> **
> then this crash happened seconds after it seemed to complete, after
>  the prompt 
> ***
> │ SageMath version 7.6, Release Date: 2017-03-25 │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> ***
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[John H Palmieri]

On Sunday, June 18, 2017 at 4:41:22 AM UTC-7, Dima Pasechnik wrote:
>
> git repo is not relevant, but a python module that shadows a Sage python 
> module would be a problem.


For example, if you have your own file "parser.py", it would interfere with 
the standard Python module "parser". 

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[vesely . pepa]

Sorry, it is cause missing gfortran.
Now it is working fine.

Dne sobota 17. června 2017 12:42:42 UTC+2 vesel...@gmail.com napsal(a):
>
> Hi,
>
> i install SageMath from binaries
> sage-7.6-Ubuntu_16.04-x86_64.tar.bz2
>
> I expand package and run
> ./sage
>
> Then the installation crash.
>
> My system is Xubuntu 16.04
>
> Thank you for help
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[John H Palmieri]

"ImportError: libgfortran.so.3: cannot open shared object file: No such file or 
directory"

It looks like you need to install fortran on your machine.



On Monday, June 5, 2017 at 10:12:12 AM UTC-7, Vincent HERBERT wrote:
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash Report

[Dima Pasechnik]

at the bottom of the report you see


ImportError: libgfortran.so.3: cannot open shared object file: No such file or 
directory


You need to install libgfortran in order to fix this.

apt-get install libgfortran3

On Wednesday, May 10, 2017 at 9:26:59 AM UTC+1, Abhishek Kesarwani wrote:
>
>
> Hi,
>  
>  Whenever i trying to install sagemath on my ubuntu 17.04 it shows the 
> following error:
>
> Oops, Sage crashed. We do our best to make it stable, but...
>
> A crash report was automatically generated with the following information:
>   - A verbatim copy of the crash traceback.
>   - A copy of your input history during this session.
>   - Data on your current Sage configuration.
>
> It was left in the file named:
> '/home/abhishek/.sage/ipython-5.0.0/Sage_crash_report.txt'
> If you can email this file to the developers, the information in it will 
> help
> them in understanding and correcting the problem.
>
> You can mail it to: sage-support at sage-s...@googlegroups.com 
> 
> with the subject 'Sage Crash Report'.
>
> If you want to do it now, the following command will work (under Unix):
> mail -s 'Sage Crash Report' sage-s...@googlegroups.com  < 
> /home/abhishek/.sage/ipython-5.0.0/Sage_crash_report.txt
>
> To ensure accurate tracking of this issue, please file a report about it 
> at:
> http://trac.sagemath.org
> PLEASE HELP ME OUT FROM THIS PROBLEM.
>
> Thank you 
> -- 
> Abhishek Kesarwani
> (Research Scholar)
> Department of Mathematics
> Indian Institute of technology, Madras
> Chennai- 600036,Tamil Nadu
> Ph. 7499221918
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

What version of Sage is this? It's not clear from the log.

The log mentions iPython 4, whereas Sage has switched to iPython 5.
It could be that the error comes from some stale content in ~/.sage/

As a 1st check, try to rename ~/.sage/ to something else, and see if it 
starts then.


On Friday, April 7, 2017 at 2:24:17 AM UTC+1, Kevin Buzzard wrote:
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

your log says

ImportError: libgfortran.so.3: cannot open shared object file: No such file 
or directory

you need to install this library by the appropriate apt-get call.

On Monday, March 27, 2017 at 10:40:42 PM UTC+1, zhang zhou wrote:
>
> Hello,
>
> I got a SageMath (7.5.1) crash at its first run on my Ubuntu 16.04 laptop. 
> Crash report is attached.
>
> Best regards,
>
> Zhang
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report. appears to have loaded, failed to run.

[Vegard Lima]

On Wed, Mar 8, 2017 at 6:56 AM, John H Palmieri  wrote:
> Just about the last line in your crash report says
>
>ImportError: libgfortran.so.3: cannot open shared object file: No such
> file or directory
>
> So you need to install gfortran, however that is done with Fedora. An
> internet search suggests something like "yum install gcc-gfortran".

On my Fedora 25 system:

$ rpm -qf /usr/lib64/libgfortran.so.3
libgfortran-6.3.1-1.fc25.x86_64

so you install by running

$ dnf install libgfortran

(yum is nowadays just a script that runs dnf.)

-- 
Vegard

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report. appears to have loaded, failed to run.

[John H Palmieri]

Just about the last line in your crash report says

   ImportError: libgfortran.so.3: cannot open shared object file: No such file 
or directory


So you need to install gfortran, however that is done with Fedora. An 
internet search suggests something like "yum install gcc-gfortran".

-- 
John



On Tuesday, March 7, 2017 at 6:05:05 PM UTC-8, wem...@uccs.edu wrote:
>
>
>
> Team SageMath,
>
>  
>
> Thankyou for providing the email address
>
>  
>
> Sage will not load and run properly on my Fedora Linux System (used the 
> latest Linux build Sage-7.5.1-Fedora).  
>
>  
>
> Printed out readme file you provided, and executed it to the best of my 
> ability.  Sage crashed, not sure why.  No directory was specified regarding 
> installation, so I created a course directory cs5920 and installed it there.
>
>  
>
> However, I cannot get it to run.  I verified I had all the correct 
> programs gcc, make, m4, perl, rnalib, and tar.  I have 
> perl-ExtUtils-MakeMaker package as well allthough I did not know 
> (--vversion didn't work) until I tried to install the package, then Lenix 
> told me.
>
>  
>
> I am using Fedora 25 on an I5 core machine.
>
>  
>
> Any help getting it to run would be most appreciated.
>
>  
>
> Following are installed:
>
> $*gcc --version*
>
> gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)
>
> Copyright (C) 2016 Free Software Foundation, Inc.
>
> This is free software; see the source for copying conditions. There is NO
>
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>  
>
> $*make --version*
>
> GNU Make 4.1
>
> Built for x86_64-redhat-linux-gnu
>
> Copyright (C) 1988-2014 Free Software Foundation, Inc.
>
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
>
> This is free software: you are free to change and redistribute it.
>
> There is NO WARRANTY, to the extent permitted by law.
>
>  
>
> *$m4 --version*
>
> m4 (GNU M4) 1.4.17
>
> Copyright (C) 2013 Free Software Foundation, Inc.
>
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>.
>
> This is free software: you are free to change and redistribute it.
>
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by Rene' Seindal.
>
>  
>
> $*perl --version*
>
>  
>
> This is perl 5, version 24, subversion 1 (v5.24.1) built for 
> x86_64-linux-thread-multi
>
> (with 63 registered patches, see perl -V for more detail)
>
> Copyright 1987-2017, Larry Wall
>
> Perl may be copied only under the terms of either the Artistic License or 
> the
>
> GNU General Public License, which may be found in the Perl 5 source kit.
>
> Complete documentation for Perl, including FAQ lists, should be found on
>
> this system using "man perl" or "perldoc perl". If you have access to the
>
> Internet, point your browser at http://www.perl.org/, the Perl Home Page.
>
>  
>
> *$ranlib --version*
>
> GNU ranlib version 2.26.1-1.fc25
>
> Copyright (C) 2015 Free Software Foundation, Inc.
>
> This program is free software; you may redistribute it under the terms of
>
> the GNU General Public License version 3 or (at your option) any later 
> version.
>
> This program has absolutely no warranty.
>
>  
>
> *$tar --version*
>
> tar (GNU tar) 1.29
>
> Copyright (C) 2015 Free Software Foundation, Inc.
>
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>.
>
> This is free software: you are free to change and redistribute it.
>
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by John Gilmore and Jay Fenlason.
>
>  
>
> *$ dnf install perl-ExtUtils-MakeMaker*
>
> Last metadata expiration check: 0:55:22 ago on Sat Mar  4 14:07:46 2017.
>
> Package perl-ExtUtils-MakeMaker-7.24-1.fc25.noarch is already installed, 
> skipping.
>
> Dependencies resolved.
>
> Nothing to do.
>
> Complete!
>
>  
>
>  
>
>  
>
> V/r, Bill
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

I presume you are trying to install a Sage binary for Ubuntu 16.04 into
a VM running this version of Ubuntu, right?

At the bottom of your log one sees

ImportError: libgfortran.so.3: cannot open shared object file: No such file 
or directory

You need to install libgfortran3 on your (virtual) Ubuntu 16.04, by running 
something like

sudo apt-get install libgfortran3

It should fix the error in question.


On Thursday, February 16, 2017 at 1:28:20 PM UTC, Jonathan Samuel wrote:
>
> I have got a problem while running the binary version of Sagemath on 
> ubuntu 10.04. please help 
>
> 1. My guest OS ubuntu 16.04 (on VMware 10)
> 2. my host OS windows 7
>
>
>
>
> [image: Best Regards]
>
> *Jonathan Samuel*
>
> E-mail: jimmy...@gmail.com   
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

is it an installation from source?
anyhow, with Sage 7.5 just released, we are already quite far from 7.1 
you're trying (why?) to get to work.


On Thursday, January 12, 2017 at 3:38:03 PM UTC, Santanu wrote:
>
> I am getting these. Please help me. 
>
>
> santanu@Math-Sans:~/SageMath$ ./sage
> ┌┐
> │ SageMath Version 7.1, Release Date: 2016-03-20 │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> └┘
>
> **
>
> Oops, Sage crashed. We do our best to make it stable, but...
>
> A crash report was automatically generated with the following information:
>   - A verbatim copy of the crash traceback.
>   - A copy of your input history during this session.
>   - Data on your current Sage configuration.
>
> It was left in the file named:
> '/home/santanu/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt'
> If you can email this file to the developers, the information in it will 
> help
> them in understanding and correcting the problem.
>
> You can mail it to: sage-support at sage-s...@googlegroups.com 
> 
> with the subject 'Sage Crash Report'.
>
> If you want to do it now, the following command will work (under Unix):
> mail -s 'Sage Crash Report' sage-s...@googlegroups.com  < 
> /home/santanu/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt
>
> To ensure accurate tracking of this issue, please file a report about it 
> at:
> http://trac.sagemath.org
>
> Hit  to quit (your terminal may close):
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

you need libgfortran on your system
try doing
apt-get install libgfortran3
and re-start sage

On Tuesday, December 27, 2016 at 12:13:20 PM UTC, Robert Samal wrote:
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report 7.0

[Laurent Bakri]

Yep that did the trick 
Thanks a lot


Le mercredi 14 décembre 2016 14:28:09 UTC+1, Laurent Bakri a écrit :
>
>
>
> Hi all, 
> I am using sage  on Debian (sid)
> Sagemath 7.0 was working fine until an upgrade of python  to version 3 
> Then it stop working with an syntax error due to python 3  
> So I (re)lnked pyhton to python 2.7 but now it crashes for a reason I 
> cannot determine 
> here is the crash report 
> Thanks in advance,
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report 7.0

[Dima Pasechnik]

On Wednesday, December 14, 2016 at 7:31:30 PM UTC, Laurent Bakri wrote:
>
>
> Hmm.. this is getting hard to follow the thread... 
> Yes there is a reason I can't upgrade  (with the last gcc there is an  
> error on flint described here "-r and -pie may not be used together" 
> 
> while compiling from source (or upgrading )  and the binary install from 
> scratch  does not work either (but i forgot the error) 
> Althought there was a patch suggested to compile the last version in this 
> google group  somewhere. hould I focus on that on your opinion ? 
>

I think the latest Sage beta (7.5.beta6) already includes this fix.
Get it here https://github.com/sagemath/sage/tree/develop
and build from source.

 

> Thanks a lot 
>
>   
> 
> Le mercredi 14 décembre 2016 14:28:09 UTC+1, Laurent Bakri a écrit :
>>
>>
>>
>> Hi all, 
>> I am using sage  on Debian (sid)
>> Sagemath 7.0 was working fine until an upgrade of python  to version 3 
>> Then it stop working with an syntax error due to python 3  
>> So I (re)lnked pyhton to python 2.7 but now it crashes for a reason I 
>> cannot determine 
>> here is the crash report 
>> Thanks in advance,
>>
>>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report 7.0

[Laurent Bakri]

Hmm.. this is getting hard to follow the thread... 
Yes there is a reason I can't upgrade  (with the last gcc there is an  
error on flint described here "-r and -pie may not be used together" 

while compiling from source (or upgrading )  and the binary install from 
scratch  does not work either (but i forgot the error) 
Althought there was a patch suggested to compile the last version in this 
google group  somewhere. hould I focus on that on your opinion ? 
Thanks a lot 

  

Le mercredi 14 décembre 2016 14:28:09 UTC+1, Laurent Bakri a écrit :
>
>
>
> Hi all, 
> I am using sage  on Debian (sid)
> Sagemath 7.0 was working fine until an upgrade of python  to version 3 
> Then it stop working with an syntax error due to python 3  
> So I (re)lnked pyhton to python 2.7 but now it crashes for a reason I 
> cannot determine 
> here is the crash report 
> Thanks in advance,
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage crash report 7.0

[Dima Pasechnik]

On Wednesday, December 14, 2016 at 3:44:19 PM UTC, NITIN DARKUNDE wrote:
>
> Hello, I have some old version of sage installed two years ago on my 
> laptop. Also some worksheets are saved on it. How to upgrade it to latest 
> 7.4 version? Whether old saved worksheets will remain saved? or get deleted?
>

You can always download the worksheets into files and save them to some 
reasonable place. (With an open worksheet such an option is in File menu, I 
think).
Normally it's a file with .sws extension.
And you can do the opposite, load a worksheet from a file.

I'd recommend to install a new version of Sage, not to upgrade the existing 
one (an upgrade from such an old version won't be possible anyway).
Then you can load your worksheets into the new version.




  

>
> On Dec 14, 2016 9:08 PM, "Dima Pasechnik"  
> wrote:
>
> Is there any reason you cannot upgrade to a more recent version? The 
> current stable version is 7.4.
>
>
> On Wednesday, December 14, 2016 at 1:28:09 PM UTC, Laurent Bakri wrote:
>>
>>
>>
>> Hi all, 
>> I am using sage  on Debian (sid)
>> Sagemath 7.0 was working fine until an upgrade of python  to version 3 
>> Then it stop working with an syntax error due to python 3  
>> So I (re)lnked pyhton to python 2.7 but now it crashes for a reason I 
>> cannot determine 
>> here is the crash report 
>> Thanks in advance,
>>
>> -- 
> 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...@googlegroups.com .
> To post to this group, send email to sage-s...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage crash report 7.0

[NITIN DARKUNDE]

Hello, I have some old version of sage installed two years ago on my
laptop. Also some worksheets are saved on it. How to upgrade it to latest
7.4 version? Whether old saved worksheets will remain saved? or get deleted?

On Dec 14, 2016 9:08 PM, "Dima Pasechnik"  wrote:

Is there any reason you cannot upgrade to a more recent version? The
current stable version is 7.4.


On Wednesday, December 14, 2016 at 1:28:09 PM UTC, Laurent Bakri wrote:
>
>
>
> Hi all,
> I am using sage  on Debian (sid)
> Sagemath 7.0 was working fine until an upgrade of python  to version 3
> Then it stop working with an syntax error due to python 3
> So I (re)lnked pyhton to python 2.7 but now it crashes for a reason I
> cannot determine
> here is the crash report
> Thanks in advance,
>
> --
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report 7.0

[Dima Pasechnik]

Is there any reason you cannot upgrade to a more recent version? The 
current stable version is 7.4.

On Wednesday, December 14, 2016 at 1:28:09 PM UTC, Laurent Bakri wrote:
>
>
>
> Hi all, 
> I am using sage  on Debian (sid)
> Sagemath 7.0 was working fine until an upgrade of python  to version 3 
> Then it stop working with an syntax error due to python 3  
> So I (re)lnked pyhton to python 2.7 but now it crashes for a reason I 
> cannot determine 
> here is the crash report 
> Thanks in advance,
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report Sage 7.4

[slelievre]

Le vendredi 9 décembre 2016 19:00:35 UTC+1, Girish Belkar a écrit :
>
> I tried to install Sage 7.4 on my lubuntu using binary 
> sage-7.4-Ubuntu_16.04-x86_64.tar.bz2.
>
> I extracted to home folder and the run the command ./sage in terminal
>
> I got the message that sage has crashed.
>
> I am attaching the crash report
>
> Kindly help 
>

Install gfortran:

apt-get install libgfortran3

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Afonso Henriques Silva Leite]

Ok, sorry for my poor message. I installed libgfortran and that solved the 
problem. Thanks.

Em domingo, 6 de novembro de 2016 12:01:34 UTC-3, Afonso Henriques Silva 
Leite escreveu:
>
> Please, I need some help here!
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

On Sunday, November 6, 2016 at 3:01:34 PM UTC, Afonso Henriques Silva Leite 
wrote:
>
> Please, I need some help here!
>

the important line in your report is

ImportError: libgfortran.so.3: cannot open shared object file: No such file 
or directory 

Probably you are using a binary release of Sage that was built on a machine 
with libgfortran.so.3
globally installed.
Chances are that if you install libgfortran on your system (i.e. if you run 
debian or ubuntu
this would be done by "apt-get install libgfortran")
and it will be the correct version, Sage would just work.

It would be possible to say more if you also mentioned how you installed 
Sage, which version, what OS you are running, etc.


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: sage crash report

[leif]

Eric Gourgoulhon wrote:
> Le vendredi 16 septembre 2016 10:37:22 UTC+2, Ralf Stephan a écrit :
> 
> Looks like C++ ABI mismatch. While gcc-4.8.4 should work
> you maybe want to install a newer version. What Sage version
> is this?
> 
> 
> I guess this is SageMath 7.3 from the AIMS PPA, installed on Ubuntu
> 16.04. See
> https://groups.google.com/d/msg/sage-devel/z1XQDRt-OFs/hnYuxcleBgAJ
> for an update on this.

FWIW, I replied to the exact same crash report of September 11th.


Orthogonal to the C++ ABI issues, we really need to patch / modify
IPython (and Python) to get *meaningful* crash reports (and /correct/
output for the system Sage was built on and the one it is actually
running on).

As is, the "crash reports" (I wouldn't say an import error is a crash
anyway) are mainly useless spam, at least when the reporters in addition
only rarely answer questions from replies, of which a couple weren't
necessary with proper generated system information either.


-leif


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: sage crash report

[Eric Gourgoulhon]

Le vendredi 16 septembre 2016 10:37:22 UTC+2, Ralf Stephan a écrit :
>
> Looks like C++ ABI mismatch. While gcc-4.8.4 should work
> you maybe want to install a newer version. What Sage version
> is this?
>

I guess this is SageMath 7.3 from the AIMS PPA, installed on Ubuntu 16.04. 
See 
https://groups.google.com/d/msg/sage-devel/z1XQDRt-OFs/hnYuxcleBgAJ
for an update on this. 

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: sage crash report

[Ralf Stephan]

Looks like C++ ABI mismatch. While gcc-4.8.4 should work
you maybe want to install a newer version. What Sage version
is this?

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[leif]

leif wrote:
> Fabio Di Cosmo wrote:
>> IPython post-mortem report
>>
>> {'commit_hash': u'b630b41',
>>   'commit_source': 'installation',
>>   'default_encoding': 'UTF-8',
>>   'ipython_path':
>> '/usr/lib/sagemath/local/lib/python2.7/site-packages/IPython',
>>   'ipython_version': '4.2.1',
>>   'os_name': 'posix',
>>   'platform': 'Linux-4.4.0-36-generic-x86_64-with-debian-stretch-sid',
>> 'sys_executable': '/usr/lib/sagemath/local/bin/python',
>>   'sys_platform': 'linux2',
>>   'sys_version': '2.7.10 (default, Aug  6 2016, 15:34:26) \n[GCC 4.8.4]'}
>>
>> ***
>>
>> 
>>
>>  107 # This must come before Calculus -- it initializes the Pynac
>> library.
>> --> 108 import sage.symbolic.pynac
>>  global sage.symbolic.pynac = undefined
>>
>> ImportError:
>> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/symbolic/pynac.so:
>>
>> undefined symbol:
>> _ZN5GiNaC8constantC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFNS_2exEjP7_objectERKS6_j
>>
>> ***
> 
> GiNaC::constant::constant(std::__cxx11::basic_string std::char_traits, std::allocator >, GiNaC::ex (*)(unsigned
> int, _object*), std::__cxx11::basic_string std::allocator > const&, unsigned int)
> 
> 
> Looks like you downloaded the wrong binary for your distro; your
> standard C++ library apparently doesn't have a dual ABI.

... or the latter rather the other way around:

It seems your Sage was originally built with / for an older Debian
version (presumably Wheezy / 7.x, with GCC 4.8), while (parts of) the
Sage library now got rebuilt with a newer compiler version, GCC 5.x or
6.x, which by default use a different C++ ABI than earlier versions,
such that some of the rebuilt parts are now incompatible to those built
with the older compiler.

So you'd either have to download the appropriate binary distribution of
Sage for your system/distro, or rebuild Sage with the native compiler.

It *might* be sufficient to just run

./sage -f pynac && make

but you may run into further similar errors later as well.


-leif


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[leif]

Fabio Di Cosmo wrote:
> IPython post-mortem report
> 
> {'commit_hash': u'b630b41',
>   'commit_source': 'installation',
>   'default_encoding': 'UTF-8',
>   'ipython_path':
> '/usr/lib/sagemath/local/lib/python2.7/site-packages/IPython',
>   'ipython_version': '4.2.1',
>   'os_name': 'posix',
>   'platform': 'Linux-4.4.0-36-generic-x86_64-with-debian-stretch-sid',
> 'sys_executable': '/usr/lib/sagemath/local/bin/python',
>   'sys_platform': 'linux2',
>   'sys_version': '2.7.10 (default, Aug  6 2016, 15:34:26) \n[GCC 4.8.4]'}
> 
> ***
> 
> 
> 
>  107 # This must come before Calculus -- it initializes the Pynac
> library.
> --> 108 import sage.symbolic.pynac
>  global sage.symbolic.pynac = undefined
> 
> ImportError:
> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/symbolic/pynac.so:
> 
> undefined symbol:
> _ZN5GiNaC8constantC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFNS_2exEjP7_objectERKS6_j
> 
> ***

GiNaC::constant::constant(std::__cxx11::basic_string, GiNaC::ex (*)(unsigned
int, _object*), std::__cxx11::basic_string const&, unsigned int)


Looks like you downloaded the wrong binary for your distro; your
standard C++ library apparently doesn't have a dual ABI.


-leif


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[leif]

Harald Andres Helfgott wrote:
>  'platform': 'Linux-3.19.0-66-generic-x86_64-with-debian-jessie-sid',
> ...
> ImportError: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version 
> `GLIBCXX_3.4.21' not found (required by 
> /home/helfgott/Desktop/SageMath/local/lib/libntl.so.25)

Smells like you downloaded the wrong Sage binary, in other words, your
distro is too old for the one you had chosen.

The version tag 3.4.21 is from GCC 5.x, your GCC is presumably 4.8 or
4.9 (from Debian 7 or 8, respectively, I think).


HTH,

-leif


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report

[leif]

Volker Braun wrote:
> Missing dependency on gsl on arch?

Don't think so, as libgsl.so must have been there during link of the
extension module.

Either ldconfig has messed up the links, or probably some RUN_PATH issue.

(Or he really took some [incomplete] binary built elsewhere.)


-leif

> 
> ImportError: libgsl.so.19: cannot open shared object file: No such file
> or directory
> 


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report

[Volker Braun]

Missing dependency on gsl on arch?

ImportError: libgsl.so.19: cannot open shared object file: No such file or 
directory




On Monday, August 15, 2016 at 8:48:14 AM UTC+2, leif wrote:
>
> Dima Pasechnik wrote: 
> > it is also ipython 5.0, which, as we know, is problematic. 
>
> But -- perhaps surprisingly, the error /here/ is unrelated to IPython. 
>
> I guess it's Sage 7.4.beta0 though. 
>
>
> -leif 
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report

[leif]

Dima Pasechnik wrote:
> it is also ipython 5.0, which, as we know, is problematic.

But -- perhaps surprisingly, the error /here/ is unrelated to IPython.

I guess it's Sage 7.4.beta0 though.


-leif


-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report

[Dima Pasechnik]

it is also ipython 5.0, which, as we know, is problematic.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage crash report

[leif]

sebastian bach wrote:
> I don't know how to fix this
> 
> ***
> 
> IPython post-mortem report
> 
> {'commit_hash': u'',
>  'commit_source': '(none found)',
>  'default_encoding': 'UTF-8',
>  'ipython_path': '/usr/lib/python2.7/site-packages/IPython',
>  'ipython_version': '5.0.0',
>  'os_name': 'posix',
>  'platform': 'Linux-4.2.5-1-ARCH-i686-with-glibc2.0',
>  'sys_executable': '/usr/bin/python2',
>  'sys_platform': 'linux2',
>  'sys_version': '2.7.10 (default, Sep  7 2015, 13:41:51) \n[GCC 5.2.0]'}
> 
> ***
> 
> 
> 
> ***
> 
> Crash traceback:
> 
> ---
> ---
> ImportError Python 2.7.10: /usr/bin/python2
>Mon Aug 15 03:53:21 2016
> A problem occurred executing Python code.  Here is the sequence of function
> calls leading up to the error, with the most recent (innermost) call last.
> /usr/bin/sage-ipython in ()
>   1 #!/usr/bin/env python2
>   2 # -*- coding: utf-8 -*-
>   3 """
>   4 Sage IPython startup script.
>   5 """
>   6 
>   7 # Install extra readline commands before IPython initialization
>   8 from sage.repl.readline_extra_commands import *
>   9 
>  10 from sage.repl.interpreter import SageTerminalApp
>  11 
>  12 app = SageTerminalApp.instance()
> ---> 13 app.initialize()
> global app.initialize =  of >
>  14 app.start()
> 
>  in
> initialize(self=, argv=None)
> 
> /usr/lib/python2.7/site-packages/traitlets/config/application.pyc in
> catch_config_error(method=,
> app=, *args=(None,),
> **kwargs={})
>  59 
>  60
> #-
>  61 # Application class
>  62
> #-
>  63 
>  64 @decorator
>  65 def catch_config_error(method, app, *args, **kwargs):
>  66 """Method decorator for catching invalid config
> (Trait/ArgumentErrors) during init.
>  67 
>  68 On a TraitError (generally caused by bad config), this will
> print the trait's
>  69 message, and exit the app.
>  70 
>  71 For use on init methods, to prevent invoking excepthook on
> invalid input.
>  72 """
>  73 try:
> ---> 74 return method(app, *args, **kwargs)
> method = 
> app = 
> args = (None,)
> kwargs = {}
>  75 except (TraitError, ArgumentError) as e:
>  76 app.print_help()
>  77 app.log.fatal("Bad config encountered during
> initialization:")
>  78 app.log.fatal(str(e))
>  79 app.log.debug("Config at the time: %s", app.config)
>  80 app.exit(1)
>  81 
>  82 
>  83 class ApplicationError(Exception):
>  84 pass
>  85 
>  86 
>  87 class LevelFormatter(logging.Formatter):
>  88 """Formatter with additional `highlevel` record
>  89 
> 
> /usr/lib/python2.7/site-packages/IPython/terminal/ipapp.pyc in
> initialize(self=, argv=None)
> 294 
> 295 return super(TerminalIPythonApp,
> self).parse_command_line(argv)
> 296 
> 297 @catch_config_error
> 298 def initialize(self, argv=None):
> 299 """Do actions after construct, but before starting the
> app."""
> 300 super(TerminalIPythonApp, self).initialize(argv)
> 301 if self.subapp is not None:
> 302 # don't bother initializing further, starting subapp
> 303 return
> 304 # print self.extra_args
> 305 if self.extra_args and not self.something_to_run:
> 306 self.file_to_run = self.extra_args[0]
> 307 self.init_path()
> 308 # create the shell
> --> 309 self.init_shell()
> self.init_shell =  >
> 310 # and draw the banner
> 311 self.init_banner()
> 312 # Now a variety of things that happen after the banner
> is printed.
> 313 self.init_gui_pylab()
> 314 self.init_extensions()
> 315 self.init_code()
> 316 
> 317 def init_shell(self):
> 318 """initialize the InteractiveShell instance"""
> 319 # Create an InteractiveShell instance.
> 320 # shell.display_banner should always be False for the
> terminal
> 321 # based app, because we call shell.show_banner() by hand
> below
> 322 # so the banner shows *before* all extension loading stuff.
> 323 self.shell = 

Re: [sage-support] Re: Sage Crash Report

[Henri Girard]

Your welcome...
I like very much this tool because it works fine and is well documented :)
I wanted to translate examples but it's too much work, and I guess all 
people using it are knowing english !

Better original language than a bad translation !
Henri

Le 01/04/2016 14:55, Oscar Alberto Castillo Felisola a écrit :
Thank you HG, Your suggestion worked like a charm. I create a new 
branch in my sage installation and tried your suggestion, and it works 
smoothly.


Best wishes!
Oscar.

On Thursday, 31 March 2016 14:56:08 UTC-3, HG wrote:

sagemanifolds compiles well usually... Just follow the install doc
and sm-install.sh :

http://sagemanifolds.obspm.fr/download.html#script_install/sm-install.sh


I prefer than git.

Le 31/03/2016 19:00, Oscar Alberto Castillo Felisola a écrit :

Hi Eric,

I finally compiled the source of sage from github, but I got a
merge conflict when I added the sagemanifolds branch. I'll post
further when I get to the office. Hope you could help me.

Cheers.

On Tuesday, 29 March 2016 15:51:53 UTC-3, Eric Gourgoulhon wrote:

Hi Oscar,

I'm afraid I cannot help much with your specific problem. The
only thing I can tell is that Sage 7.1 + SageManifolds 0.9
works well on Ubuntu, which is based on Debian, but of course
differs from it.

Best regards,

Eric.

Le mardi 29 mars 2016 16:04:20 UTC+2, Oscar Alberto Castillo
Felisola a écrit :

Dear community,

lately, I'm having problems with the installation of
SAGE. I downloaded the version Sage v.7.1 for Debian_8,
and it seems to work... but I installed sagemanifold
v.0.9, and I got the report file attached to this post.

I'm having problems too when compiling the scr code,
because the file `flint*` has a problem.

Any suggestions?

-- 
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...@googlegroups.com .
To post to this group, send email to sage-s...@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-support
.
For more options, visit https://groups.google.com/d/optout
.


--
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 post to this group, send email to sage-support@googlegroups.com 
.

Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[Oscar Alberto Castillo Felisola]

Thank you HG, Your suggestion worked like a charm. I create a new branch in 
my sage installation and tried your suggestion, and it works smoothly.

Best wishes!
Oscar.

On Thursday, 31 March 2016 14:56:08 UTC-3, HG wrote:
>
> sagemanifolds compiles well usually... Just follow the install doc and 
> sm-install.sh :
>
> http://sagemanifolds.obspm.fr/download.html#script_install/sm-install.sh
>
> I prefer than git.
>
> Le 31/03/2016 19:00, Oscar Alberto Castillo Felisola a écrit :
>
> Hi Eric, 
>
> I finally compiled the source of sage from github, but I got a merge 
> conflict when I added the sagemanifolds branch. I'll post further when I 
> get to the office. Hope you could help me.
>
> Cheers.
>
> On Tuesday, 29 March 2016 15:51:53 UTC-3, Eric Gourgoulhon wrote: 
>>
>> Hi Oscar, 
>>
>> I'm afraid I cannot help much with your specific problem. The only thing 
>> I can tell is that Sage 7.1 + SageManifolds 0.9 works well on Ubuntu, which 
>> is based on Debian, but of course differs from it.
>>
>> Best regards,
>>
>> Eric.
>>
>> Le mardi 29 mars 2016 16:04:20 UTC+2, Oscar Alberto Castillo Felisola a 
>> écrit : 
>>>
>>> Dear community,  
>>>
>>> lately, I'm having problems with the installation of SAGE. I downloaded 
>>> the version Sage v.7.1 for Debian_8, and it seems to work... but I 
>>> installed sagemanifold v.0.9, and I got the report file attached to this 
>>> post.
>>>
>>> I'm having problems too when compiling the scr code, because the file 
>>> `flint*` has a problem.
>>>
>>> Any suggestions?
>>>
>> -- 
> 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...@googlegroups.com .
> To post to this group, send email to sage-s...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[Henri Girard]

sagemanifolds compiles well usually... Just follow the install doc and 
sm-install.sh :


http://sagemanifolds.obspm.fr/download.html#script_install/sm-install.sh

I prefer than git.

Le 31/03/2016 19:00, Oscar Alberto Castillo Felisola a écrit :

Hi Eric,

I finally compiled the source of sage from github, but I got a merge 
conflict when I added the sagemanifolds branch. I'll post further when 
I get to the office. Hope you could help me.


Cheers.

On Tuesday, 29 March 2016 15:51:53 UTC-3, Eric Gourgoulhon wrote:

Hi Oscar,

I'm afraid I cannot help much with your specific problem. The only
thing I can tell is that Sage 7.1 + SageManifolds 0.9 works well
on Ubuntu, which is based on Debian, but of course differs from it.

Best regards,

Eric.

Le mardi 29 mars 2016 16:04:20 UTC+2, Oscar Alberto Castillo
Felisola a écrit :

Dear community,

lately, I'm having problems with the installation of SAGE. I
downloaded the version Sage v.7.1 for Debian_8, and it seems
to work... but I installed sagemanifold v.0.9, and I got the
report file attached to this post.

I'm having problems too when compiling the scr code, because
the file `flint*` has a problem.

Any suggestions?

--
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 post to this group, send email to sage-support@googlegroups.com 
.

Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Oscar Alberto Castillo Felisola]

Hi Eric,

I finally compiled the source of sage from github, but I got a merge 
conflict when I added the sagemanifolds branch. I'll post further when I 
get to the office. Hope you could help me.

Cheers.

On Tuesday, 29 March 2016 15:51:53 UTC-3, Eric Gourgoulhon wrote:
>
> Hi Oscar, 
>
> I'm afraid I cannot help much with your specific problem. The only thing I 
> can tell is that Sage 7.1 + SageManifolds 0.9 works well on Ubuntu, which 
> is based on Debian, but of course differs from it.
>
> Best regards,
>
> Eric.
>
> Le mardi 29 mars 2016 16:04:20 UTC+2, Oscar Alberto Castillo Felisola a 
> écrit :
>>
>> Dear community, 
>>
>> lately, I'm having problems with the installation of SAGE. I downloaded 
>> the version Sage v.7.1 for Debian_8, and it seems to work... but I 
>> installed sagemanifold v.0.9, and I got the report file attached to this 
>> post.
>>
>> I'm having problems too when compiling the scr code, because the file 
>> `flint*` has a problem.
>>
>> Any suggestions?
>>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Oscar Alberto Castillo Felisola]

Hi Volker,

I discover that a git repository hosted at github. I was able to compile 
the source from that repository, which is by the way more updated that the 
repository advertised at the documentation.

Nonetheless, I'm still having problems when trying to compile the 
sagemanifolds branch... It gave me some conflict issues, and didn't work 
after the resolution.

Thank you!

On Tuesday, 29 March 2016 19:39:07 UTC-3, Volker Braun wrote:
>
> Should be fixed in the next version. In the meantime, you can download the 
> source tarball and compile that.
>
>
>
> On Tuesday, March 29, 2016 at 4:04:20 PM UTC+2, Oscar Alberto Castillo 
> Felisola wrote:
>>
>> Dear community, 
>>
>> lately, I'm having problems with the installation of SAGE. I downloaded 
>> the version Sage v.7.1 for Debian_8, and it seems to work... but I 
>> installed sagemanifold v.0.9, and I got the report file attached to this 
>> post.
>>
>> I'm having problems too when compiling the scr code, because the file 
>> `flint*` has a problem.
>>
>> Any suggestions?
>>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

The crash report alone does not say what version of
Sage you are using, whether or not you built it yourself,
and how to reproduce this crash (just launch Sage in the
terminal? something else?)


On Friday, February 19, 2016 at 2:52:18 AM UTC, 程海 wrote:
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Dima Pasechnik]

Thanks, but without knowing how this is obtained, it is not useful, sorry.
(we need to know OS, which Sage version, binary or source install, and a 
sequence of commands that led to the crash)

On Saturday, February 6, 2016 at 9:47:13 AM UTC, Herb Doughty wrote:
>
>  
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Gabriel Chênevert]

Oh. You're absolutely right! Sorry for wasting bandwidth with that...

(I was trying to use the latest Ubuntu 15.10 binary under Mint 17, which is 
still based on Trusty)

Le vendredi 15 janvier 2016 20:28:38 UTC+1, Volker Braun a écrit :
>
> Presumably you are using a binary that wasn't built for your distribution 
> / version. Compile from source.
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage Crash Report

[Volker Braun]

Presumably you are using a binary that wasn't built for your distribution / 
version. Compile from source.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.