Problems with installation of sage-9.3-Ubuntu_20.04-x86_64
I downloaded and installed sage from sage-9.3-Ubuntu_20.04-x86_64 on a Ubuntu 20.04 installation. However I believe this version is broken. A simple example is the basic arrow in the documentation.
arrow3d((0,0,0), (1,1,1), 1).show()
The binary for Ubuntu 18.04 has the same problem.
After building from source on a Raspberry Pi4, 9.3 works without any problems. I know I can build from source on my PC, but this can be off-putting for new and inexperienced users.
Could you be a little more specific? What is the issue with the arrow?
Sage crashes, it spews out some messages and ends with "attaching gdb to process id ... . I ran
./sage --testall
and a couple hours later I had a 200MB file with 948 lines containing "# Killed due to illegal instruction". To satisfy my curiosity I downloaded sage-9.3-Debian_GNU_Linux_10-i686 and installed it and it worked (although it coughed out a few warnings).I cannot reproduce your issue: SageMath installed from
sage-9.3-Ubuntu_20.04-x86_64.tar.bz2
works well on my Ubuntu 20.04 computer. Which command makes it crash in your case?I've edited the original question to include the specific command. To check if it was a quirk of my hardware I built Sage from source and everything seems to run correctly.
Thanks. I still cannot reproduce your issue with my install of
sage-9.3-Ubuntu_20.04-x86_64.tar.bz2
: the commandarrow3d((0,0,0), (1,1,1), 1).show()
works for me, both in the console and in the Jupyter notebook.Thanks for checking this out. May I ask which mirror you downloaded the file from? I used North American mirrors.
I used the French mirror (Université Pierre et Marie Curie, Paris, France)
Ah well, I downloaded from the mirror at Université Pierre et Marie Curie, Paris and had the same results. As a practical matter for me the issue is moot since I was able to build from source and have a sage that is running properly as far as I can tell. I ran
./sage --testall
and gotAll tests passed!
I also ran./sage --testall
on the installation from the binary download and have saved the output. I'll go through it and try posting on the SageTrac developers forum to see if anyone has an insight into what's happening.I'll leave this thread open in case anyone else runs into this problem.