Problems launching jupyter browser window and threejs browser window

[jplab]

Hi everyone,

I wanted to test the following ticket on sage 9.0beta2:

https://trac.sagemath.org/ticket/28658

So I wrote the following in the terminal:

sage: p = polytopes.icosahedron()
sage: p.plot()
Launched html viewer for Graphics3d Object

Then, a Firefox browser window opens with Firefox's "pingponging ball of Death" of an eternally loading window...

The same thing occurs with

sage -notebook

Previously, I've been having problems with launching jupyter, but copy-pasting

the link given in the terminal in the address bar always worked, so I had my workaround.

But I have grown tired of this workaround and I thought maybe someone knew how to solve this?

I've just done a "make distclean" for another reason, have a freshly compiled sage and moved ".sage" to ".sage_old" to see if

this changes anything: Nope.

I am running debian buster with firefox being my default browser.

Any ideas would be appreciated!

While we are here, on another train of thoughts: is it me or viewing polyhedron with threejs does not show the edges?

J-P

[Dima Pasechnik]

I too don't see the edges of the icosahedron while viewin the in
jupyter notebook.
Could you open a ticket for this?

>
> J-P
>
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/8dac1a83-f36d-4a7d-8769-53b4c0e5d73b%40googlegroups.com.

[Eric Gourgoulhon]

Le dimanche 27 octobre 2019 15:36:45 UTC+1, jplab a écrit :

Hi everyone,

I wanted to test the following ticket on sage 9.0beta2:

https://trac.sagemath.org/ticket/28658

So I wrote the following in the terminal:

sage: p = polytopes.icosahedron()
sage: p.plot()
Launched html viewer for Graphics3d Object

Then, a Firefox browser window opens with Firefox's "pingponging ball of Death" of an eternally loading window...

Works for me (on the same ticket branch). This is with Ubuntu 18.04 + Firefox 70.0. What is your system?

While we are here, on another train of thoughts: is it me or viewing polyhedron with threejs does not show the edges?

Same issue here.

Note that

sage: icosahedron()

shows the edges.

Eric.

 

[jplab]

Hi,

Le dimanche 27 octobre 2019 20:10:11 UTC+1, Dima Pasechnik a écrit :

On Sun, Oct 27, 2019 at 4:36 PM jplab <jeanphil...@gmail.com> wrote:
>
> Hi everyone,
>
> I wanted to test the following ticket on sage 9.0beta2:
>
> https://trac.sagemath.org/ticket/28658
>
> So I wrote the following in the terminal:
>
> sage: p = polytopes.icosahedron()
> sage: p.plot()
> Launched html viewer for Graphics3d Object
>
> Then, a Firefox browser window opens with Firefox's "pingponging ball of Death" of an eternally loading window...
>
> The same thing occurs with
>
> sage -notebook
>
> Previously, I've been having problems with launching jupyter, but copy-pasting
> the link given in the terminal in the address bar always worked, so I had my workaround.
> But I have grown tired of this workaround and I thought maybe someone knew how to solve this?
>
> I've just done a "make distclean" for another reason, have a freshly compiled sage and moved ".sage" to ".sage_old" to see if
> this changes anything: Nope.
>
> I am running debian buster with firefox being my default browser.
>
> Any ideas would be appreciated!
>
> While we are here, on another train of thoughts: is it me or viewing polyhedron with threejs does not show the edges?

I too don't see the edges of the icosahedron while viewin the in
jupyter notebook.
Could you open a ticket for this?

Yes, this is now #28662: https://trac.sagemath.org/ticket/28662

[jplab]

Then, a Firefox browser window opens with Firefox's "pingponging ball of Death" of an eternally loading window...

Works for me (on the same ticket branch). This is with Ubuntu 18.04 + Firefox 70.0. What is your system?

Ok... After some thoughts when you asked about my firefox version, it made me realize that I do not restart my firefox often.

Some time ago I updated it without restarting (which I am surprised it did not crash, which is the typical behavior...).

In any case, the classical "turning firefox on and off" made everything work again. (facepalm)

Just for the record: I have debian buster running Firefox 68.2.0esr.

Thanks for prompting me to realize that!

Best,

J-P