Re: [sage-support] Sage Crash Report

2025-07-28 Thread G. M.-S.
Hi. SageMath runs on macOS 10.13 and newer. *macOS 10.13, 10.14 and 10.15 are NOT "too old" for SageMath.* There was indeed a problem with SageMath-10.6_x86_64.dmg, which has been promptly corrected by Marc Culler in the following version. Please get *SageMath-10.7_x86_64.dmg* from https://gith

Re: [sage-support] Sage Crash Report

2025-07-07 Thread Hanlin Xu
OK, thank you! On Monday, July 7, 2025 at 10:00:58 AM UTC+8 dim...@gmail.com wrote: > Hi, your macOS is too old to run this binary. > (it's in fact well past EOL). > > Your best bet is to build from source, although I expect big trouble. > > If it's an old hardware you must use to run Sage, I can

Re: [sage-support] Sage Crash Report

2025-07-06 Thread Dima Pasechnik
Hi, your macOS is too old to run this binary. (it's in fact well past EOL). Your best bet is to build from source, although I expect big trouble. If it's an old hardware you must use to run Sage, I can only suggest to install Linux or FreeBSD on it, either directly, or in a VM HTH On July 6

Re: [sage-support] Sage Crash Report

2025-04-01 Thread Erick Ross
Thank you very much for the info. Maybe this just means that it is time for me to update to Ubuntu 24.04. On Tuesday, April 1, 2025 at 2:16:55 PM UTC-4 dim...@gmail.com wrote: > On Tue, Apr 1, 2025 at 9:34 AM Erick Ross wrote: > > > > OS: Ubuntu 20.04 (using WSL2 running on 64-bit Windows 10) >

Re: [sage-support] Sage Crash Report

2025-04-01 Thread Dima Pasechnik
On Tue, Apr 1, 2025 at 9:34 AM Erick Ross wrote: > > OS:Ubuntu 20.04 (using WSL2 running on 64-bit Windows 10) > Sage Installation: Using "apt install sagemath" in the terminal > Crash details: Just typed "sage" into the terminal, and it crashed. > > There is some undefined symbol e

Re: [sage-support] Sage Crash Report

2022-08-22 Thread Robert Parini
Thanks, that works! On Monday, 22 August 2022 at 15:12:15 UTC+1 isu...@gmail.com wrote: > Can you try the following? > > conda install mamba -n base > conda config --add channels conda-forge > conda config --set channel_priority strict > mamba create -n sagetest sage > conda activate sagetest > s

Re: [sage-support] Sage Crash Report

2022-08-22 Thread Isuru Fernando
Can you try the following? conda install mamba -n base conda config --add channels conda-forge conda config --set channel_priority strict mamba create -n sagetest sage conda activate sagetest sage On Sun, Aug 21, 2022 at 6:24 PM Robert Parini wrote: > Using conda on macOS 12.4 (with Apple silic

Re: [sage-support] Sage Crash Report

2022-08-22 Thread Robert Parini
Sure, output below, thanks --- # packages in environment at /Users/rparini/opt/miniconda3/envs/sagetest: # # NameVersion Build Channel _r-mutex 1.0.1 anacondar_1conda-forge alabaster 0.7.12

Re: [sage-support] Sage Crash Report

2022-08-21 Thread Isuru Fernando
Can you share the output of the following command? conda list -n sagetest On Sun, Aug 21, 2022 at 6:24 PM Robert Parini wrote: > Using conda on macOS 12.4 (with Apple silicon) I get the attached error > after installing sage with: > > conda create -n sagetest sage > conda activate sagetest > sa

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

2022-02-15 Thread Dima Pasechnik
On Wed, 16 Feb 2022, 02:43 'Bharathwaj Palvannan' via sage-support, < sage-support@googlegroups.com> 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 Mo

Re: [sage-support] Sage Crash Report

2022-01-17 Thread Nathan Dunfield
On Monday, January 17, 2022, Dima wrote: > This is an M1 machine, right? I don't think we already support these. > The recommended binaries for macOS, namely https://github.com/3-manifolds/Sage_macOS/releases are known to work fine on M1, though using Rosetta emulation for Sage 9.4. An M1-n

Re: [sage-support] Sage Crash Report

2022-01-17 Thread Dima Pasechnik
On Sun, Jan 16, 2022 at 4:56 PM 'Bharathwaj Palvannan' via sage-support wrote: > > Dear developers, > > > > I have been trying to install Sage on my macOS (Version 12.1 Monterey). I > tried installing it via the .tar and the .dmg files, but both methods failed > for various reasons. I am attachi

Re: [sage-support] Sage crash report

2022-01-10 Thread Dima Pasechnik
On Mon, Jan 10, 2022 at 2:12 PM Alba Carrodeguas wrote: > > Hello I´m using sage 6.10 through virtual machine, oracle, for linux. > The problem is when I start the virtual machine everything works fine until > it asks me for login and pasword, I write sage for both and also for the > other one t

Re: [sage-support] Sage crash report

2022-01-10 Thread Dima Pasechnik
On Mon, Jan 10, 2022 at 11:39 AM Alba Carrodeguas wrote: > > Sage crashed when logging in through virtual machine in order to be of any help, we'd need more details: what VM (virtual machine), what OS, what Sage version, how it was installed, how exactly you were trying to start Sage, what was th

Re: [sage-support] Sage Crash Report

2021-09-01 Thread hbetx9
I can ask this another way. I have the tarball, and I want to end up with a system wide install. This is not build from source. What is the best way to do this? In the referenced instructions the modification is to SAGE_LOCAL and not SAGE_ROOT. I'm confused as to the difference and effect. On

Re: [sage-support] Sage Crash Report

2021-09-01 Thread hbetx9
As the directory is in /opt and ownership is root.root, I can't run this as it gets permission denied when writing the log file. On Wednesday, September 1, 2021 at 2:08:56 PM UTC-5 Matthias Koeppe wrote: > See > https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-

Re: [sage-support] Sage Crash Report

2021-09-01 Thread Matthias Koeppe
See https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source point 4 ("./configure --prefix") On Wednesday, September 1, 2021 at 12:00:15 PM UTC-7 hbetx9 wrote: > So I got this working in my home directory but want the SageMath directory > system wide. I moved i

Re: [sage-support] Sage Crash Report

2021-09-01 Thread hbetx9
So I got this working in my home directory but want the SageMath directory system wide. I moved it to /opt and changed ownership to root.root, however this causes now a disagreement with the SAGE_ROOT environment variable. Should I unpack the tarball as root there to install or is there an easy

Re: [sage-support] Sage Crash Report

2021-08-31 Thread Matthias Koeppe
On Tuesday, August 31, 2021 at 12:55:46 PM UTC-7 hbetx9 wrote: > On my system, python2 and python3 is installed, but there is no generic > python symlink. Does this need to be created for sage and if so should it > be python3? In installed from tarball, so this is not an issue with the > Ubuntu

Re: [sage-support] Sage Crash Report

2021-08-31 Thread hbetx9
On my system, python2 and python3 is installed, but there is no generic python symlink. Does this need to be created for sage and if so should it be python3? In installed from tarball, so this is not an issue with the Ubuntu package. On Monday, August 30, 2021 at 9:13:49 AM UTC-5 hbetx9 wrote:

Re: [sage-support] Sage Crash Report

2021-08-30 Thread hbetx9
I think the issue is a disagreement with python. The package installs fine on a clean machine. I know this isn't the wheelhouse, but how can I diagnose my python configuration for compatibility with sage. In particular, I have python 3.8.10 installed systemwide. On Sunday, August 29, 2021 at 4

Re: [sage-support] Sage Crash Report

2021-08-29 Thread hbetx9
The package log has the following error: /usr/lib/python3/dist-packages/sage/combinat/root_system/branching_rules.py:1753: SyntaxWarning: "is not" with a literal. Did you mean "!="? if len(stypes) is not 2: /usr/lib/python3/dist-packages/sage/graphs/graph_latex.py:1159: SyntaxWarning: 'str'

Re: [sage-support] Sage Crash Report

2021-08-29 Thread Dima Pasechnik
On Sat, Aug 28, 2021 at 10:57 PM Lance Edward Miller wrote: > > To whom it may concern, > > I'm installing sage from the synaptic package manager on Linux Mint 20.1. > The package is for Sage 9.0, but the app does not run. Following is the crash > report, any advice on how to best resolve (unin

Re: [sage-support] Sage Crash Report

2021-08-16 Thread Dima Pasechnik
it appears that installing blender changed Python used to in Sage's venv. All bets are off in such a scenario - you'd need to rebuild Sage. On Tue, 17 Aug 2021, 00:20 Gaël Cousin, wrote: > Ubuntu 20.04 Focal Fossa > > > Dear all, > > Here follows attached a sage crash report. I think the sage

Re: [sage-support] Sage Crash Report

2021-03-24 Thread Mike Lee
Thank you Dima and Isuru, creating a new conda environment worked! (I'm guessing you updated the givaro dependency for the conda install) And it looks like manually specifying an older version of givaro will also work, based on Mariusz's report. On Wed, Mar 24, 2021 at 3:21 PM Mariusz Sokolowski

Re: [sage-support] Sage Crash Report

2021-03-24 Thread Mariusz Sokolowski
hey, I had similar/same(?) problem as Mike and installing older version of givaro (conda install "givaro=4.1.1=h192cbe9_1") fixed it. -M On Wednesday, March 24, 2021 at 12:55:05 PM UTC-4 isu...@gmail.com wrote: > Mike, > > Can you try creating a new conda environment? This is an issue with t

Re: [sage-support] Sage Crash Report

2021-03-24 Thread Isuru Fernando
Mike, Can you try creating a new conda environment? This is an issue with the latest givaro build we had and we marked it as broken. Details at https://github.com/conda-forge/givaro-feedstock/issues/13 (You could also try doing `conda install "givaro=4.1.1=h192cbe9_1"` to get the older link.) Is

Re: [sage-support] Sage Crash Report

2021-03-24 Thread Mike Lee
Not sure if this is relevant, but I get the following messages when I try running 'conda update givaro' in my sage conda environment (attached). I apologize for multiple messages! On Wed, Mar 24, 2021 at 8:42 AM Mike Lee wrote: > I believe the following line in the output of the nm command you >

Re: [sage-support] Sage Crash Report

2021-03-24 Thread Mike Lee
I believe the following line in the output of the nm command you suggested is the corresponding symbol? 00017da0 T Givaro::Integer::operator std::__cxx11::basic_string, std::allocator >() const I've also attached the full output of the nm command as a txt file below in case it's helpful!

Re: [sage-support] Sage Crash Report

2021-03-24 Thread Dima Pasechnik
On Tue, Mar 23, 2021 at 10:27 PM Mike Lee wrote: > > Hi, > > I'm facing a similar issue when I tried to install Sage through conda (I > followed the 'Setting Up' directions in https://wiki.sagemath.org/Conda). I > get the following error in my Sage_crash_report.txt (attached) > > 'ImportError:

Re: [sage-support] Sage Crash Report

2021-03-23 Thread Mike Lee
Hi, I'm facing a similar issue when I tried to install Sage through conda (I followed the 'Setting Up' directions in https://wiki.sagemath.org/Conda). I get the following error in my Sage_crash_report.txt (attached) 'ImportError: /home/msl/software/miniconda3/envs/sage/lib/python3.9/site-pack

Re: [sage-support] Sage Crash Report

2021-01-24 Thread Dima Pasechnik
at the bottom of the log you see ImportError: /home/mathieu/opt/SageMath/local/lib/python3.8/site-packages/sage/matrix/matrix_modn_sparse.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev which is an indication t

Re: [sage-support] Sage Crash Report

2020-04-23 Thread Dima Pasechnik
On Thu, Apr 23, 2020 at 9:42 PM Jean-Florent Raymond wrote: > > Hello, > > Did you try to rebuild since the upgrade? > If you upgraded a package that sage needs, then sage might complain that > it cannot find the version it was used to. > > It seems to be the case with libntl according to the cras

Re: [sage-support] Sage Crash Report

2020-04-23 Thread Jean-Florent Raymond
Hello, Did you try to rebuild since the upgrade? If you upgraded a package that sage needs, then sage might complain that it cannot find the version it was used to. It seems to be the case with libntl according to the crash report you attached: ImportError: libntl.so.35: cannot open shared object

Re: [sage-support] Sage Crash Report

2020-04-14 Thread HANG HUANG
Thank you very much for your suggestion. But now I got another problem about the building the package xz-5.2.2.p0. I attached the log file here. Any help will be greatly appreciated! Isuru Fernando 于2020年4月13日周一 下午8:50写道: > Looks like you are using ccache, but CCACHE_DIR is not pointing to the >

Re: [sage-support] Sage Crash Report

2020-04-13 Thread Isuru Fernando
Looks like you are using ccache, but CCACHE_DIR is not pointing to the scratch folder. Delete $HOME/.ccache and set CCACHE_DIR env variable to some place like /scratch/user/hhuang235/.ccache Isuru On Mon, Apr 13, 2020 at 8:45 PM HANG HUANG wrote: > Thanks very much for your reply. In fact, my s

Re: [sage-support] Sage Crash Report

2020-04-13 Thread HANG HUANG
Thanks very much for your reply. In fact, my scratch folder has almost 1T of free space. So I am really confused of why I got that error message. Best, Amy 'Justin C. Walker' via sage-support 于2020年4月13日周一 下午6:16写道: > > > > On Apr 13, 2020, at 14:59 , HANG HUANG wrote: > > > > I am trying to

Re: [sage-support] Sage Crash Report

2020-04-13 Thread 'Justin C. Walker' via sage-support
> On Apr 13, 2020, at 14:59 , HANG HUANG wrote: > > I am trying to install Sage version 9.0 on the High performance cluster at my > university, which runs Linux (CentOS 7). I am installing to my local > "scratch" folder since I do not have administrative permissions. I am trying > to instal

Re: [sage-support] Sage Crash report

2020-04-09 Thread hbetx9
I didn't see that option, will use in future, thanks! On Thursday, April 9, 2020 at 2:56:23 PM UTC-5, John H Palmieri wrote: > > Did you look at the file "README.md"? It suggests building in parallel to > speed things up. Have you tried that? > > > On Thursday, April 9, 2020 at 12:35:58 PM UTC-

Re: [sage-support] Sage Crash report

2020-04-09 Thread John H Palmieri
Did you look at the file "README.md"? It suggests building in parallel to speed things up. Have you tried that? On Thursday, April 9, 2020 at 12:35:58 PM UTC-7, hbetx9 wrote: > > I htink I know what I did, somehow I change the prefix to a directory that > didn't exist. I'm recompiling to see if

Re: [sage-support] Sage Crash report

2020-04-09 Thread hbetx9
I htink I know what I did, somehow I change the prefix to a directory that didn't exist. I'm recompiling to see if the error is fixed. Boy does this compile take a LONG time, is that the same for everyone? On Thursday, April 9, 2020 at 2:26:48 PM UTC-5, hbetx9 wrote: > > Okay, I did somethin

Re: [sage-support] Sage Crash report

2020-04-09 Thread hbetx9
Okay, I did something apparently odd. For context, I first unpacked in a directory, ran make (took a long time) and would close with an error concerning R as above. Sage would work on command line by running the copy in this directory. However, something I did broke this install, and I'm wonde

Re: [sage-support] Sage Crash report

2020-04-08 Thread Matthias Koeppe
On Wednesday, April 8, 2020 at 8:01:38 PM UTC-7, hbetx9 wrote: > > No, I just want all users to have this at default. Where should I put the > SAGE_ROOT directory? /usr/local? > Use "./configure --prefix=/usr/local/opt/sage-9.0" to set the installation prefix (SAGE_LOCAL). -- You received th

Re: [sage-support] Sage Crash report

2020-04-08 Thread hbetx9
No, I just want all users to have this at default. Where should I put the SAGE_ROOT directory? /usr/local? On Wednesday, April 8, 2020 at 9:36:33 PM UTC-5, Dima Pasechnik wrote: > > On Thu, Apr 9, 2020 at 10:30 AM hbetx9 > > wrote: > > > > Hi Matthias, > > > > Boy what a mess this is. I did

Re: [sage-support] Sage Crash report

2020-04-08 Thread Dima Pasechnik
On Thu, Apr 9, 2020 at 10:30 AM hbetx9 wrote: > > Hi Matthias, > > Boy what a mess this is. I didn't realize the rabbit hole went down that far. > Do you think I could skip this and after upgrading sage later stable versions > (I see you and others are working on it), this can be resolved? > > I

Re: [sage-support] Sage Crash report

2020-04-08 Thread hbetx9
Hi Matthias, Boy what a mess this is. I didn't realize the rabbit hole went down that far. Do you think I could skip this and after upgrading sage later stable versions (I see you and others are working on it), this can be resolved? If I don't resolve this now, then sage works but I'd like to

Re: [sage-support] Sage Crash report

2020-04-08 Thread Matthias Koeppe
Read https://doc.sagemath.org/html/en/developer/ if you wish to make changes to Sage, and https://trac.sagemath.org/ticket/29379 for the change ticket that makes the upgrade to R 3.6.3 On Wednesday, April 8, 2020 at 3:02:01 PM UTC-7, hbetx9 wrote: > > I _almost_ got this to work, I have R 3.6.3

Re: [sage-support] Sage Crash report

2020-04-08 Thread hbetx9
I _almost_ got this to work, I have R 3.6.3 but still get the following error: * package: r-3.6.2 log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2 Presumably, there is a flag or configure I can send make to use 3.

Re: [sage-support] Sage Crash report

2020-04-08 Thread hbetx9
On second thought, I should just fix this now. Am I correct I need to install package r-3.6.2 and rebuld? On Wednesday, April 8, 2020 at 11:54:39 AM UTC-5, hbetx9 wrote: > > Tried from source and got this error: > > Error building Sage. > > The following package(s) may have failed to build (not

Re: [sage-support] Sage Crash report

2020-04-08 Thread hbetx9
Thanks, I'll have to make that adjustment, at the moment I have two versions of sage, so I need to figure out how to make it just version 9 first. Otherwise my home .sage directory won't drive behavior of the things in SAGE_ROOT/local correct? On Wednesday, April 8, 2020 at 12:15:53 PM UTC-5

Re: [sage-support] Sage Crash report

2020-04-08 Thread slelievre
> can the color scheme for sage on the terminal be changed? > I used a dark background so this is not easy to read. If using the Sage REPL on a dark background, run the command sage: %colors Linux You can also include that command in a file called `init.sage` file, located in the `.sage` fo

Re: [sage-support] Sage Crash report

2020-04-08 Thread hbetx9
Tried from source and got this error: Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all-start'): * package: r-3.6.2 log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log build directory: /home/lmiller/sage-9.0/local/var/tmp/

Re: [sage-support] Sage Crash report

2020-04-07 Thread Dima Pasechnik
On Wed, Apr 8, 2020 at 11:05 AM hbetx9 wrote: > I installed from package on Mint 19.3. I'm happy to run whatever is > needed to help diagnose. For context, I have installed python 2.7.17 and the > package pulled sage 8.1. I'm not sure why the packages didn't pull the most > up to date. Is

Re: [sage-support] Sage Crash report

2020-04-07 Thread hbetx9
Hi Dima. I installed from package on Mint 19.3. I'm happy to run whatever is needed to help diagnose. For context, I have installed python 2.7.17 and the package pulled sage 8.1. I'm not sure why the packages didn't pull the most up to date. Is there a PPA I need to add? Best, Lance On S

Re: [sage-support] Sage Crash report

2020-04-04 Thread Dima Pasechnik
On Sun, Apr 5, 2020 at 7:44 AM Lance Edward Miller wrote: > > After install on Linux Mint 19.3, I got the following crash report. Any help > is appreciated. What exactly have you installed? A binary installation, or done a build from sources? > >

Re: [sage-support] Sage Crash Report

2020-03-25 Thread Dima Pasechnik
Also, sqlite has been updated in sagemath 9.0, as well as we have there https://trac.sagemath.org/ticket/28511 which is meant to help with skew clock issues. On Wed, 25 Mar 2020, 14:42 Dima Pasechnik, wrote: > > > On Wed, 25 Mar 2020, 14:19 Kashif Bari, wrote: > >> I do not believe I I have

Re: [sage-support] Sage Crash Report

2020-03-24 Thread Dima Pasechnik
On Wed, 25 Mar 2020, 14:19 Kashif Bari, wrote: > I do not believe I I have permissions to build on a disk physically in the > machine being used. > you may ask for, at least, explaining that you have a problem with skew timestamps. The scratch folder is where I was told to install any software

Re: [sage-support] Sage Crash Report

2020-03-24 Thread Kashif Bari
I do not believe I I have permissions to build on a disk physically in the machine being used. The scratch folder is where I was told to install any software that I wish to use. The home directory that I have is not large enough to install anything. On Tue, Mar 24, 2020 at 8:43 PM Dima Pasechnik

Re: [sage-support] Sage Crash Report

2020-03-24 Thread Dima Pasechnik
On Wed, 25 Mar 2020, 02:21 Kashif Bari, wrote: > Hi Dima, > > I am building locally, as this is a university cluster and I only have > access to my local directories. > by "local" I mean the filesystem on a disk physically in the machine you are using, as opposed to a networked file system, ofte

Re: [sage-support] Sage Crash Report

2020-03-24 Thread Kashif Bari
Hi Dima, I am building locally, as this is a university cluster and I only have access to my local directories. Unfortunately, this did not resolve the issue and this line was added to my output: [sqlite-3270100] configure: WARNING: unrecognized options: --disable-maintainer-mode In the log fil

Re: [sage-support] Sage Crash Report

2020-03-24 Thread Dima Pasechnik
On Tue, Mar 24, 2020 at 4:51 PM Kashif Bari wrote: > > I believe I was able to resolve the issue with mpc-1.1.0 by loading a more > recent version of the texinfo package! Hopefully others who have this issue > will be able to resolve it similarly. > > However, I ended up running into this issue

Re: [sage-support] Sage Crash Report

2020-03-24 Thread Kashif Bari
I believe I was able to resolve the issue with mpc-1.1.0 by loading a more recent version of the texinfo package! Hopefully others who have this issue will be able to resolve it similarly. However, I ended up running into this issue when running make again: Error building Sage. The following pac

Re: [sage-support] Sage Crash Report

2020-03-18 Thread Dima Pasechnik
On Thu, Mar 19, 2020 at 12:25 PM Kashif Bari wrote: > > Thank you, Dima, I was able to load the texinfo package before I did make and > I believe this resolved my issue with mpfr. However, I ran into the same > issue with mpc-1.1.0 now instead of mpfr. hmm, the same? If you have now makeinfo in

Re: [sage-support] Sage Crash Report

2020-03-18 Thread Kashif Bari
Thank you, Dima, I was able to load the texinfo package before I did make and I believe this resolved my issue with mpfr. However, I ran into the same issue with mpc-1.1.0 now instead of mpfr. I currently have sage 8.9 installed on my personal laptop, so I figured I would stick with the same versi

Re: [sage-support] Sage Crash Report

2020-03-18 Thread Dima Pasechnik
mpfr needs makeinfo program to be installed. This is a pretty standard thing, which on Centos is in texinfo package https://centos.pkgs.org/7/centos-x86_64/texinfo-5.1-5.el7.x86_64.rpm.html By the way, why are you building Sage 8.9, and not 9.0? On Thu, Mar 19, 2020 at 7:00 AM Kashif Bari wrote

Re: [sage-support] Sage Crash Report

2020-03-18 Thread kashbari
Thank you! Best, Kash > On Mar 18, 2020, at 6:48 PM, Isuru Fernando wrote: > >  > One alternative to installing sage is by using the conda package manager. > https://github.com/conda-forge/miniforge#download > It's know to work on CentOS 6 and above. > See https://github.com/conda-forge/sage-

Re: [sage-support] Sage Crash Report

2020-03-18 Thread Isuru Fernando
No, it doesn't require sudo privileges. It can be installed in your home directory. Isuru On Wed, Mar 18, 2020 at 8:05 PM wrote: > Hi! > Thanks for responding! Will this require any administrative permissions? > I do not have any sudo privileges. > > On Mar 18, 2020, at 6:48 PM, Isuru Fernando

Re: [sage-support] Sage Crash Report

2020-03-18 Thread kashbari
Hi! Thanks for responding! Will this require any administrative permissions? I do not have any sudo privileges. > On Mar 18, 2020, at 6:48 PM, Isuru Fernando wrote: > >  > One alternative to installing sage is by using the conda package manager. > https://github.com/conda-forge/miniforge#do

Re: [sage-support] Sage Crash Report

2020-03-18 Thread Isuru Fernando
One alternative to installing sage is by using the conda package manager. https://github.com/conda-forge/miniforge#download It's know to work on CentOS 6 and above. See https://github.com/conda-forge/sage-feedstock#installing-sage Isuru On Wed, Mar 18, 2020 at 6:00 PM Kashif Bari wrote: > I am

Re: [sage-support] Sage Crash report

2020-01-08 Thread Dima Pasechnik
at the end of your log: ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory Are you using system's gfortran? (you should) On Wed, Jan 8, 2020 at 4:42 PM Malcolm MacCallum wrote: > > This is from Ubuntu 18.04 Linux 64-bit > Sage built from source. The build

Re: [sage-support] Sage Crash Report

2020-01-05 Thread Dima Pasechnik
On Sun, 5 Jan 2020, 18:26 Jean-Florent Raymond, wrote: > Hello, > > Did you succeed building sage from source? If not what is the error > message? > Do you have a system version of ntl? ( pacman -Qs ntl ) > > On Arch linux (similar to Manjaro) I had the same message error > yesterday when trying

Re: [sage-support] Sage Crash Report

2020-01-02 Thread Dima Pasechnik
On Fri, Jan 3, 2020 at 9:03 AM Artemis Heller wrote: > > Hi, > > Here is the crash report from a freshly installed sagemath 9.0.1 from pacman > on manjaro linux with python 3.8. > > I've been trying to install sage 9.0 all day, sage library crashes the build > from source, I've tried installing

Re: [sage-support] Sage Crash Report

2019-10-21 Thread Eric Gourgoulhon
Le lundi 14 octobre 2019 08:57:57 UTC+2, Dima Pasechnik a écrit : > > Dear Dave, > > On Mon, Oct 14, 2019 at 1:03 AM dave dobbs > > wrote: > > > > OS: Xubuntu 18.04.1 64-bit > > downloaded from SAGE: sage-8.9-Ubuntu_16.04-x86_64.tar.bz2 > > wrong version - notice that you are running Ubuntu 1

Re: [sage-support] Sage Crash Report

2019-10-18 Thread Dima Pasechnik
On Sat, Oct 19, 2019 at 12:07 AM Sinan Kapçak wrote: > > on Linux Ubuntu 19.10 - > Sage installed by binaries downloaded by a torrent. > Downloaded and extracted and ./sage. it would be surprising if a binary for an earlier Ubuntu version worked on 19.10. You might need to build Sage from source.

Re: [sage-support] Sage Crash Report

2019-10-13 Thread Dima Pasechnik
Dear Dave, On Mon, Oct 14, 2019 at 1:03 AM dave dobbs wrote: > > OS: Xubuntu 18.04.1 64-bit > downloaded from SAGE: sage-8.9-Ubuntu_16.04-x86_64.tar.bz2 wrong version - notice that you are running Ubuntu 18.04, and you're trying a tarball fot 16.04. Tarball for 18.04 is not ready yet, I think.

Re: [sage-support] sage crash report

2019-09-02 Thread Vincent Delecroix
Dear Oscar, You should tell precisely what is your installation of Sage that is broken. Looking at the crash report, I assume that you use Sage from the system. In this situation, you would better address your question to some Debian help forum or mailing list. For the bug you encountered, it ha

Re: [sage-support] Sage Crash Report

2019-08-17 Thread Dima Pasechnik
This is built by Debian people, so it's really not our bug, I cc to the relevant list, On Sat, Aug 17, 2019 at 6:32 PM Carlos Mauricio Silva wrote: > > Hi, > I would like to report a crash: > > Operating System: Debian Linux Testing > carlos@arroway:~$ uname -a > Linux arroway 4.19.0-5-amd64 #1 S

Re: [sage-support] Sage Crash Report

2019-05-14 Thread Vincent Delecroix
Why is the package named "sagemath" not installed? Did you intentionally install only "sagemath-common"? To have a fully working SageMath installation you need the three packages sagemath sagemath-doc-en sagemath-jupyter The package "sagemath-common" is a dependency of the first one of these.

Re: [sage-support] Sage Crash Report

2019-05-14 Thread Erik Wallace
I still have not received an answer to this. Is the information I provided helpful or do you need more? On Wed, May 1, 2019 at 8:35 AM Erik Wallace wrote: > Here is the output: > > $ apt list --installed | grep sagemath > > sagemath-common/bionic,bionic,now 8.1-7ubuntu1 all [installed] > > $ ls

Re: [sage-support] Sage Crash Report

2019-05-11 Thread Clemens
Hi, I am sorry I double posted but I though my post did not get through (I did not find it because it was added to an existing topic/post, probably due to the subject?) Yes, the sage installation works. The error also occurs if I download the source tarball and try to install from source. Tha

Re: [sage-support] Sage Crash Report

2019-05-10 Thread Dima Pasechnik
It would be good to know whether your Sage installation is working at all. In case, can you try some simple computations at Sage prompt? On Sat, May 11, 2019 at 4:14 AM Clemens wrote: > > OS: macOS 10.14 > Installed from: sage-8.7-OSX_10.13.6-x86_64.dmg (Extracted to ~/SageMath) > > How to reprod

Re: [sage-support] Sage Crash Report

2019-05-01 Thread Erik Wallace
Here is the output: $ apt list --installed | grep sagemath sagemath-common/bionic,bionic,now 8.1-7ubuntu1 all [installed] $ ls -l /usr/lib/python2.7/dist-packages/sage/structure/ total 808 -rw-r--r-- 1 root root 641 Dec 7 2017 all.py -rw-r--r-- 1 root root 1114 Apr 15 21:51 all.pyc -rw-r--

Re: [sage-support] Sage Crash Report

2019-04-28 Thread Vincent Delecroix
I do not see anything obvious in the crash report that explains the problem. For each thing below could you copy paste the full output of what appears in the console. 1. The list of sagemath packages installed $ apt list --installed | grep sagemath 2. Files in /usr/lib/python2.7/dist-package

Re: [sage-support] Sage Crash Report

2019-04-28 Thread Erik Wallace
Yes, I downloaded via apt. The supporting python packages were also downloaded via apt. On Sat, Apr 27, 2019 at 5:08 PM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hello, > > What did you downloaded exactly? You meant that you installed > Sage from via the package manager (apt)? > > Be

Re: [sage-support] Sage Crash Report

2019-04-27 Thread Vincent Delecroix
Hello, What did you downloaded exactly? You meant that you installed Sage from via the package manager (apt)? Best Vincent Le 23/04/2019 à 03:22, Erik Wallace a écrit : Hello, I am submitting this crash report. I downloaded sage from the Ubuntu repo. Please let me know, how I can fix this.

Re: [sage-support] Sage Crash Report

2018-11-19 Thread Kolen Cheung
Thanks. This is it. I’m glad we discussed about the channel priority (if you noticed my original attachment sage-environment.yml, conda-forge is last.) I’m curious why this ABI incompatibility are allowed when satisfying the dependencies. I don’t know if the conda forge formula is written in

Re: [sage-support] Sage Crash Report

2018-11-18 Thread Isuru Fernando
Ah, that package was marked broken. conda-forge and defaults channels are not ABI compatible, (it'll be in a month or so once the conda-forge rebuild is done) You should prioritize conda-forge over defaults and see what happens. Let me know if it doesn't work and I'll send you the env file for a ne

Re: [sage-support] Sage Crash Report

2018-11-18 Thread Kolen Cheung
Interesting, it failed. sage ❯❯❯ conda env create -f env.yml Solving environment: failed ResolvePackageNotFound: - sagenb==1.0.3=py_0 Searching it on https://anaconda.org/conda-forge/sagenb/files shows it doesn’t exist. Has it been removed? Another question, I noticed that you prioritize

Re: [sage-support] Sage Crash Report

2018-11-18 Thread Isuru Fernando
Can you try doing `conda update libgd`? Python 3 builds are experimental and don't work correctly. (But they should be able to start sage.) I've attached an env file that works for me on linux. Isuru On Sunday, November 18, 2018 at 5:26:46 AM UTC-6, Dima Pasechnik wrote: > > I guess the place t

Re: [sage-support] Sage Crash Report

2018-11-18 Thread Dima Pasechnik
I guess the place to report such issues is here: https://github.com/conda-forge/sage-feedstock On Sun, Nov 18, 2018 at 10:58 AM Kolen Cheung wrote: > > I actually tried a whole bunch of combinations. Build with and without the > intel channel, with python 2 or 3, on 3 different systems (macOS, Ar

Re: [sage-support] Sage Crash Report

2018-11-18 Thread Kolen Cheung
I actually tried a whole bunch of combinations. Build with and without the intel channel, with python 2 or 3, on 3 different systems (macOS, ArchLinux, and SUSE), all through conda. They all have some problems (that upon `sage` there's an error, but this is the only one I reported so they can in

Re: [sage-support] Sage Crash Report

2018-11-18 Thread Dima Pasechnik
Oh, wait, these are all Python3 libraries, correct? This looks fishy to me. As well, Sage's libgd does not link ICU libraries (all these libicu*), fontconfig and webp, all these must be conda-forge modifications. So that's not something we could realistically fix without conda people. The usual s

Re: [sage-support] Sage Crash Report

2018-11-17 Thread Kolen Cheung
sage ~ ❯❯❯ ls -alh /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3 lrwxrwxrwx 1 sage sage 14 Nov 17 17:34 /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3 -> libgd.so.3.0.5 sage ~ ❯❯❯ ldd /home/sage/.conda/en

Re: [sage-support] Sage Crash Report

2018-11-17 Thread Dima Pasechnik
On Sun, Nov 18, 2018 at 12:11 AM Kolen Cheung wrote: > > I tried. the problem is libiconv is already there. conda install that shows > it's fulfilled. Probably a linking problem... What's the output of ldd /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so

Re: [sage-support] Sage Crash Report

2018-11-17 Thread Kolen Cheung
I tried. the problem is libiconv is already there. conda install that shows it's fulfilled. you can try to conda crete from the yml file to replicate the exact conda environment to reproduce this problem. Regards, Kolen On Nov 17, 2018, 3:30 PM -0800, Dima Pasechnik , wrote: > It looks like Sag

Re: [sage-support] Sage Crash Report

2018-11-17 Thread Dima Pasechnik
It looks like Sage installed via conda-forge, and ImportError: /home/sage/.conda/envs/sage/lib/python3.6/site-packages/sage/matrix/../../../../libgd.so.3: undefined symbol: libiconv seems to indicate that libiconv is missing in the environment. I don't know much about conda, but it seems that y

Re: [sage-support] Sage Crash Report

2018-03-11 Thread Jeroen Demeyer
On 2018-03-10 12:29, Alasdair McAndrew wrote: As created just now. Enjoy! How did you get that SageMath installation on your computer? Was it a binary install, a source install, an upgrade from an earlier version? In any case, I would suggest to simply reinstall Sage. -- You received this

Re: [sage-support] Sage Crash Report

2017-10-26 Thread Vegard Lima
Hi, On Thu, Oct 26, 2017 at 10:27 PM, Dima Pasechnik wrote: > On Thursday, October 26, 2017 at 4:55:19 PM UTC+1, Renan Birck Pinheiro > wrote: >> gfortran is installed but sage still doesn't work. I do have >> libgfortran.so.4 rather than libgfortran.so.3 that sage wants. >> > > then your only wa

Re: [sage-support] Sage Crash Report

2017-10-26 Thread Dima Pasechnik
Hi, On Thursday, October 26, 2017 at 4:55:19 PM UTC+1, Renan Birck Pinheiro wrote: > > Hello, > > gfortran is installed but sage still doesn't work. I do > have libgfortran.so.4 rather than libgfortran.so.3 that sage wants. > > then your only ways out are either to build Sage from source, or to

Re: [sage-support] Sage Crash Report

2017-10-26 Thread Renan Birck Pinheiro
Hello, gfortran is installed but sage still doesn't work. I do have libgfortran.so.4 rather than libgfortran.so.3 that sage wants. Thanks, 2017-10-25 11:12 GMT-02:00 Jeroen Demeyer : > This is a known problem which will be fixed for Sage 8.1 > > For now, you have to install gfortran from your F

  1   2   >