New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOError: cannot identify image file #17940
Comments
comment:1
Works for me. Can you post your strace output? Can PIL open a PNG at all on your system? |
Replying to @gagern:
It seems I was misled: apparently JMol attaching its script to the generated PNG is normal behavior. The PNG file is apparently broken at some other point. Looking at the PNG chunks as reported by the I'll try to see whether we can work around this issue by forcing the locale to C, like |
Branch: u/gagern/ticket/17940 |
Commit: |
Author: Martin von Gagern |
comment:4
Setting the locale to C works as expected. New commits:
|
Reviewer: Volker Braun |
comment:5
Good detective job ;-) Did you report it upstream? |
comment:6
Replying to @vbraun:
Did so now: https://sourceforge.net/p/jmol/bugs/570/ |
Upstream: Workaround found; Bug reported upstream. |
Changed keywords from none to strange |
Changed branch from u/gagern/ticket/17940 to |
With Sage 6.6 beta 3 and using Sage Notebook I get a backtrace when I want to see a sphere:
Using strace I can see access to some
preview.png
and looking at that file I notice that it appears to be a regular PNG, concatenated with a Jmol script. So apparently two outputs ended up in the same data stream. This is likely a consequence of #17234.Upstream: Workaround found; Bug reported upstream.
CC: @vbraun
Component: user interface
Keywords: strange
Author: Martin von Gagern
Branch/Commit:
3818998
Reviewer: Volker Braun
Issue created by migration from https://trac.sagemath.org/ticket/17940
The text was updated successfully, but these errors were encountered: