We had a similar problem. It turned out that our $LD_LIBRARY_PATH had
an inappropriate entry. sage starts without error after we removed
the inappropriate entry.
Elizabeth
On Feb 1, 7:50 am, Volker Braun wrote:
> Sage prepends its own directory to the PATH, of course. You are the first
> one w
Sage prepends its own directory to the PATH, of course. You are the first
one who managed to break the startup in the CrashHandler import, so it is
definitely not easy to break. My hint is still to use strace, but you'll
have to read the manpage and do some investigation of your own.
Volker
--
You may be right, I did have ~/.local/bin added to my path. However,
removing any reference to it (in .bashrc, where it was aded in the first
place) still confuses sage:
jscandal@jorges { ~ }$ env | grep PATH
DEFAULTS_PATH=/usr/share/gconf/gnome.default.path
PATH=/home/jscandal/bin:/usr/local/sb
