[sage-support] Re: Error starting sage after a source build

I just found a workaround to this issue. It doesn't actually solve the bug, but it might be usefull to someone experiencing this: Citing [1] : "In addition to the global site-packages paths, site is responsible for adding the user-specific loc

[sage-support] Re: Error starting sage after a source build

OK, track ticket is #10729 -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org

[sage-support] Re: Error starting sage after a source build

I agree that $HOME/.local/lib/python2.6/site-packages gets automatically added to sys.path if it exists: [vbraun@volker-desktop ~]$ mkdir -p .local/lib/python2.6/site-packages [vbraun@volker-desktop ~]$ sage -- | Sage Version 4.6

[sage-support] Re: Error starting sage after a source build

I have created a new user (test), switched to it I didn't create/modify any configuration file, that is, I got a brand new $HOME environment. Because I also reinstalled ubuntu, I am pretty sure there wasn't any specific configuration added by me, just plain ubuntu 10.10. I built sage, and all we

[sage-support] Re: Error starting sage after a source build

Thanks for the suggestion, I'll definitively check on that. I am turning a bit insane about this. I will now create a new user that, paired with the fact I reinstalled ubuntu while debugging this, should give me an environment free of any nonsense that I could have in my $HOME, and reinstall sa

[sage-support] Re: Error starting sage after a source build

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

Re: [sage-support] Re: Error starting sage after a source build

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 --

Re: [sage-support] Re: Error starting sage after a source build

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

Re: [sage-support] Re: Error starting sage after a source build

$HOME/.local/bin is not a "standard place" to look for executables. It will only be searched if you put it into the PATH yourself. -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For m

Re: [sage-support] Re: Error starting sage after a source build

There seem to be nothing special in ~/.ipython: jscandal@jorges { ~/sw }$ ls /home/jscandal/.ipython/ Crash_report_ipython.txt history ipython_config_pylab.py dbhistory.json ipython_config_pysh.py I have even moved ~/.ipython elsewhere, but sage will load the ipyth

Re: [sage-support] Re: Error starting sage after a source build

I mean ~/.ipython/ -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org

Re: [sage-support] Re: Error starting sage after a source build

There might be something in ~/.ipythonrc that pulls in your own ipython. -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/g

Re: [sage-support] Re: Error starting sage after a source build

I did a clean install, removing from my .bashrc two lines defining the PYTHONPATH and the PATH variables, opening a new terminal and making sure there were no traces of those variables in the environment. Sage built ok, but I got the same error upon starting sage. Then it occurred to me that I c

Re: [sage-support] Re: Error starting sage after a source build

Well, some bad and good news: The bad: I reinstalled ubuntu (not specifically for sage, as there were other things I've been trying to solve for a long time, but it helped me decide to do it), reinstalled sage, and I get exactly the same error. The good: I think I am closer now to find the caus

Re: [sage-support] Re: Error starting sage after a source build

2011/1/30 Simon King > Hi Jorges, > > Usually I build and install it just for myself, i.e., as a normal > user. Actually I don't have root access on the computer in my office. > That' no problem for working with Sage. > > Cheers, > Simon > > Thanks, I am building sage again, to be able to post th

[sage-support] Re: Error starting sage after a source build

Hi Jorges, On 30 Jan., 04:04, Jeff Post wrote: > On Saturday 29 January 2011 17:43, jorges wrote: > > > Maybe this is a dumb question, but should sage be built by root? > > I'm not sure this applies to Sage, since I haven't yet got it to work, but in > general, software should be built as an ordi

Re: [sage-support] Re: Error starting sage after a source build

On Saturday 29 January 2011 17:43, jorges wrote: > Maybe this is a dumb question, but should sage be built by root? I'm not sure this applies to Sage, since I haven't yet got it to work, but in general, software should be built as an ordinary user, but installed as root. There is some software t

[sage-support] Re: Error starting sage after a source build

Could be lots of reasons. Permissions? Weird LD_PRELOAD? Borked PYTHONPATH? You can see where it is seaching with strace. -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more optio

[sage-support] Re: Error starting sage after a source build

Yes, it's there. How come sage is not finding it? -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL

[sage-support] Re: Error starting sage after a source build

Do you have $SAGE_LOCALl/lib/python2.6/site-packages/IPython/CrashHandler.py -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.