On Feb 11, 1:42 pm, Timothy Clemans wrote:
> I used to see this problem on sagenb.org
>
How did you resolve it there?
--
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,
I used to see this problem on sagenb.org
On Thu, Feb 11, 2010 at 10:45 AM, zsharon wrote:
> On Feb 11, 12:34 pm, Michael Madison
> wrote:
>> I had the same problem on both VMWARe and VirtualBox running sage,
>> however, I was using Windows XP at the time and I was using the
>> FireFox browser a
On Feb 11, 12:34 pm, Michael Madison
wrote:
> I had the same problem on both VMWARe and VirtualBox running sage,
> however, I was using Windows XP at the time and I was using the
> FireFox browser at the time. I did two things: 1. I emptied the Trash
> in Sagenotebook. It is not clear this rea
I had the same problem on both VMWARe and VirtualBox running sage,
however, I was using Windows XP at the time and I was using the
FireFox browser at the time. I did two things: 1. I emptied the Trash
in Sagenotebook. It is not clear this really was what fixed the
problem, but it did work sever