Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-14 Thread Matthias Koeppe
This code is from https://trac.sagemath.org/ticket/23711 On Saturday, November 14, 2020 at 7:32:27 PM UTC-8 kcrisman wrote: > (I frankly don't even see why this was done in the 1st place) >> >> > > # possible. Only when some future Matplotlib version really requires >> > > # a new structure for

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-14 Thread kcrisman
> (I frankly don't even see why this was done in the 1st place) > > > > # possible. Only when some future Matplotlib version really requires > > > # a new structure for the $MPLCONFIGDIR should this version > > > # number be changed to the new matplotlib version. > > > export MPLCONFIGDIR="$D

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-14 Thread Dima Pasechnik
On Fri, Nov 13, 2020 at 6:38 PM François Bissey wrote: > > Well it certainly wasn’t changed each time we upgraded MPL (and yes I am part > of the guilty) as it should have. Is there a ticket to fix this? (I frankly don't even see why this was done in the 1st place) Dima > > François > > > On 14/

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-13 Thread François Bissey
Well it certainly wasn’t changed each time we upgraded MPL (and yes I am part of the guilty) as it should have. François > On 14/11/2020, at 7:05 AM, Matthias Koeppe wrote: > > We have some suspicious code in src/bin/sage-env; perhaps this is a good > opportunity to review whether this should

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-13 Thread Matthias Koeppe
We have some suspicious code in src/bin/sage-env; perhaps this is a good opportunity to review whether this should be changed. if [ -z "$MPLCONFIGDIR" ]; then # We hardcode a version number in the directory name. The idea is # that we keep using the same version number as long as that is

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-13 Thread 'jonatha...@googlemail.com' via sage-devel
I only ran it once and it solved it permanently, also for the other installations of the same version on different computers, but with same home-directory. But it appears every user has to call it once. dim...@gmail.com schrieb am Freitag, 13. November 2020 um 14:08:52 UTC+1: > On Fri, Nov 13,

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-13 Thread Dima Pasechnik
On Fri, Nov 13, 2020 at 11:55 AM 'jonatha...@googlemail.com' via sage-devel wrote: > > Thank you François. > > I was doubtful that your answer would help, but it did finally after some > googling. > > I had to run > > import matplotlib.font_manager > matplotlib.font_manager._rebuild() > > At leas

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-13 Thread 'jonatha...@googlemail.com' via sage-devel
Thank you François. I was doubtful that your answer would help, but it did finally after some googling. I had to run import matplotlib.font_manager matplotlib.font_manager._rebuild() At least on the 9.2 install that did help and once my user had those fonts installed in home (believe this is

Re: [sage-devel] Jupyter notebook crashes with multiusers

2020-11-13 Thread François Bissey
The top of your crash log is interesting, especially with the context you give it. [I 08:54:47.064 NotebookApp] 302 GET /?token=9646f700a842467835ef92b578ebef632e86a326a85e828b (127.0.0.1) 1.53ms [I 08:54:56.520 NotebookApp] Kernel started: d273c9d9-80cb-45a6-a336-b3562f294b26, name: sagemath -