On Sat, 13 Feb 2010 16:27:22 -0800 (PST), Tom Roche wrote:
> summary: I installed ubuntu package=sagemath (and dependencies) using
> aptitude on 2 previously-sage-clean ubuntu karmic boxes. Sage appeared
> to install cleanly on both boxes, but a simple problem (that works on
> sagenb.org) causes s
summary: I installed ubuntu package=sagemath (and dependencies) using
aptitude on 2 previously-sage-clean ubuntu karmic boxes. Sage appeared
to install cleanly on both boxes, but a simple problem (that works on
sagenb.org) causes sage to abend similarly on both boxes. How to fix
the current install
Dear David,
I appreciate very much your suggestions,
> > after typing a Yes to an update notification of Ubuntu-9.04 to 9.10 it
> > became unstable, first in an unnoticed way, until finally all my
> > installation crashes in a sudden "unable to boot".
>
> That could be a hardware problem.
>
> Can you think of *anything* you might have done to cause this?
Yes, actually. Just before things stopped working, I accidentally
told Windows to shut down without first closing the VirtualBox window
(thus allowing the VM to save state properly). I realized the mistake
right away, stopped the s
On 13 February 2010 11:00, David Kirkby wrote:
> On 13 February 2010 06:44, zsharon wrote:
>
>> Maybe your sage image is different, but for mine, the notebook is
>> started with the command "notebook" (w/o quotes).
>
> It should be
>
> sage: notebook()
>
> and not
>
> sage: notbook
>
> So the or
On 13 February 2010 06:44, zsharon wrote:
> Maybe your sage image is different, but for mine, the notebook is
> started with the command "notebook" (w/o quotes).
It should be
sage: notebook()
and not
sage: notbook
So the original poster was correct to have the quotes.
Dave
--
To post to
2010/2/13 Jorge E. ´Sanchez Sanchez :
>
> Dear support group,
>
> after typing a Yes to an update notification of Ubuntu-9.04 to 9.10 it
> became unstable, first in an unnoticed way, until finally all my
> installation crashes in a sudden "unable to boot".
That could be a hardware problem.
> So I
