Opened 11 years ago

Closed 7 years ago

#9477 closed defect (fixed)

jmol shows a black screen in the notebook, it works fine in the reference manual

Reported by: olazo Owned by: olazo
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: notebook Keywords: jmol
Cc: Merged in:
Authors: Reviewers: Karl-Dieter Crisman, Oscar Gerardo Lazo Arjona
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

I get the following error message in the log of my notebook when I try to show a 3d plot with jmol:

script compiler ERROR: se esperaba una instrucción
----line 1 command 1 of /home/admin/0/cells/30/sage0-size500.jmol?1278886612:
          >>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <<<<
ERROR en guión: script compiler ERROR: se esperaba una instrucción
----line 1 command 1 of /home/admin/0/cells/30/sage0-size500.jmol?1278886612:
          >>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <<<<
eval ERROR: 
----line 1 command 1:
         script >> "/home/admin/0/cells/30/sage0-size500.jmol?1278886612" <<

Jmol loads, and shows a black screen instead of the actual plot.

If I try the exact same plot in the cells in the reference manual, the plot shows perfectly and no error message appears in the log.

This seems to me rather like the opposite to #3167 in which things worked fine in the notebook but not in the help

Change History (9)

comment:1 Changed 11 years ago by olazo

It may be important to mention that the following command does not popup a jmol window in the command line:

sage: a=point3d([0,0,0])
sage: a.show()

But, if I use:

sage: a.export_jmol('/home/oscar/point')

a zip file containing a SCRIPT file appears there, and I can use:

sage: !java -jar /home/cwitty/sage-4.4.4/local/lib/python2.6/site-packages/sagenb-0.8-py2.6.egg/sagenb/data/jmol/Jmol.jar}}}

to make jmol open in my desktop, and I can then use it to open the SCRIPT file, and it shows the point just fine.

comment:2 Changed 8 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:3 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:4 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:5 follow-up: Changed 7 years ago by kcrisman

Oscar, can you verify whether this is still happening for you? Given how much the notebook has changed in the meantime it might be hard to track this down, and it looks like something akin to #3167 is back. I think this would be worth closing unless we have more information.

comment:6 in reply to: ↑ 5 Changed 7 years ago by olazo

Replying to kcrisman:

Oscar, can you verify whether this is still happening for you? Given how much the notebook has changed in the meantime it might be hard to track this down, and it looks like something akin to #3167 is back. I think this would be worth closing unless we have more information.

This no longer happens to me. I am currently using sage version 5.0 (though I expect it to be safe to assume that sage 6 won't make the problem come back). If I remember correctly this had to do more with the implementation of java in firefox than with jmol or sage at all. I think I fixed this by using the privative version of the java plugin for firefox. However, icedtea works just fine now that I use a more recent version of it. I suggest this ticket to be closed. Cheers!

Last edited 7 years ago by olazo (previous) (diff)

comment:7 Changed 7 years ago by kcrisman

  • Milestone changed from sage-6.3 to sage-duplicate/invalid/wontfix
  • Reviewers set to Karl-Dieter Crisman, Oscar Gerardo Lazo Arjona
  • Status changed from new to needs_review

Thanks! Very helpful.

comment:8 Changed 7 years ago by kcrisman

  • Status changed from needs_review to positive_review

comment:9 Changed 7 years ago by vbraun

  • Resolution set to fixed
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.