Do you mean that if you open Sage.app and click on the Terminal Session > Sage menu, that Terminal.app doesn’t open? Or do you mean that Terminal.app doesn’t open automatically when you try to start the notebook server?
For now, doing it manually once (and typing in a password) should fix the problem. If it doesn’t, then there is some other problem. -Ivan On Jan 8, 2015, at 4:39 PM, Ruizhi Deng <[email protected]> wrote: Thank you! But the problem for me is that the terminal don't start. On Wednesday, January 7, 2015 at 11:04:20 PM UTC-5, kcrisman wrote: > > > > On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote: >> >> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I >> started sage successfully for the first time but I have trouble running >> sage after that. It constantly shows that Sage server failed to start. >> And here's the log information I find. It might be useful. >> > > Looks like the issues at https://groups.google.com/ > forum/#!topic/sage-support/_Ly5eQ2E-10 and originally reported in a > different form at http://trac.sagemath.org/ticket/9873#comment:33 > > Ivan, any ideas for a long-term fix on this? This really should work > without having to do > > Terminal Session > Sage > then type notebook(). > > as suggested in that thread. > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
