This is a Debian-specific problem, I think they're working on updating Sage to a more recent version (the current stable version is 8.9). I cc to the specific list.
On Sat, Oct 12, 2019 at 6:36 PM Sage user <clu...@gmail.com> wrote: > > My terminal output is pasted below, bug report is attached. > > I tried emailing sage-supp...@googlegroups.com per the terminal output - > didn't work (bounced). Sagemath homepage 'Report a bug' brought me here. > > OS is Debian testing amd64. Sage installed from Debian testing repos. Crash > occurs immediately on executing sage. > > Thanks > Chris > > Terminal output follows ... > > ~$ sage > ┌────────────────────────────────────────────────────────────────────┐ > │ SageMath version 8.6, Release Date: 2019-01-15 │ > │ Using Python 2.7.17. 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/c/.ipython/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-supp...@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-supp...@googlegroups.com < > /home/c/.ipython/Sage_crash_report.txt > > In your email, please also include information about: > - The operating system under which the crash happened: Linux, macOS, Windows, > other, and which exact version (for example: Ubuntu 16.04.3, macOS 10.13.2, > Windows 10 Pro), and whether it is 32-bit or 64-bit; > - How Sage was installed: using pip or conda, from GitHub, as part of > a Docker container, or other, providing more detail if possible; > - How to reproduce the crash: what exact sequence of instructions can one > input to get the same crash? Ideally, find a minimal yet complete sequence > of instructions that yields the crash. > > To ensure accurate tracking of this issue, please file a report about it at: > http://trac.sagemath.org > > Hit <Enter> to quit (your terminal may close): > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/6c336b0f-bbfa-43b6-9bc0-36854710abb1%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2Zs6Bcse7LOdcm5yU1qWeSafHPr4g4Zzy9yd-cs3hk1w%40mail.gmail.com.
