Created attachment 72499 [details] File which is displayed incorrectly Okular does not display the minus sign in the formula, but xdvik displays (the sign should be): \documentclass{article} \begin{document} $e^{-i\pi}$ \end{document}
Created attachment 72502 [details] attachment-16610-0.html Works for me. Can you attach a screenshot of what you get?
Fri, 13 Jul 2012 14:38:31 +0000 от Albert Astals Cid <tsdgeos@terra.es>: https://bugs.kde.org/show_bug.cgi?id=303479 Albert Astals Cid <tsdgeos@terra.es> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tsdgeos@terra.es --- Comment #1 from Albert Astals Cid <tsdgeos@terra.es> --- Works for me. Can you attach a screenshot of what you get?
Created attachment 72503 [details] attachment-16610-1.dat
Created attachment 72504 [details] Screenshot_of_xdvik.png
Created attachment 72505 [details] Screenshot_of_Okular.png
Which okular version are you using?
DVI Backend Version 0.3.4 Using KDE Development Platform 4.8.4 (4.8.4) under Gnome 3.2.1 (if it is important) Fri, 13 Jul 2012 15:01:53 +0000 от Albert Astals Cid <tsdgeos@terra.es>: > > > > > https://bugs.kde.org/show_bug.cgi?id=303479 > > --- Comment #6 from Albert Astals Cid <tsdgeos@terra.es> --- > Which okular version are you using? > > -- > You are receiving this mail because: > You reported the bug. >
Also I made a bug report that Okular is crashing while closing (maybe it is related to the bug under consideration) Fri, 13 Jul 2012 15:01:53 +0000 от Albert Astals Cid <tsdgeos@terra.es>: https://bugs.kde.org/show_bug.cgi?id=303479 --- Comment #6 from Albert Astals Cid <tsdgeos@terra.es> --- Which okular version are you using?
I think I have found deeper reason of the problem: In the properties of the file (in Okular) I found (in Font Tab) Name : "cmsy7, 100%" Type : TeX Free Type-handled File: The font /usr/share/texmf/fonts/type1/bluesky/cm/cmsy7.pfb could be opened and read, but its font format is unsupported When I changed the fonts to larger, the problem with displaying "-" disappeared. Moreover, another bug I reported today disappeared: crashing of Okular while closing or returning to Editor (Kile). Thus the question: why the problem with the font leads to crashing Okular? Fri, 13 Jul 2012 15:01:53 +0000 от Albert Astals Cid <tsdgeos@terra.es>: https://bugs.kde.org/show_bug.cgi?id=303479 --- Comment #6 from Albert Astals Cid <tsdgeos@terra.es> --- Which okular version are you using?
"When I changed the fonts to larger", you mean in the dvi file, not that you zoom, right?
yes.
Which fedora version are you running? Can you write the md5sum of /usr/share/texmf/fonts/type1/bluesky/cm/cmsy7.pfb? Are you running your fedora version fully updated?
Fedora 16 fully updated md5sum gives: 8e734115ec391395a9327eb0ddf82a04 /usr/share/texmf/fonts/type1/bluesky/cm/cmsy7.pfb
Fedora 16 here too, but i get fe52d379879bc0313debe81e97969908 (#okular: it's the same as tosky's). Package: texlive-texmf-fonts-2007-40.fc15 Does yum reinstall texlive-texmf-fonts help?
(In reply to comment #14) > Fedora 16 here too Seems I've forgotten what my OS version is. Sorry, I'm running fedora 15. My package is: texlive-texmf-fonts-2007-40.fc15 Yours should be: texlive-texmf-fonts-2007-40.fc16 Since in tosky's fc16 it has the same checksum as in my fc15, I suppose that cmsy7.pfb is the same in both packages and the checksum I wrote is still valid.
I obtained: ..... Running Transaction Installing : texlive-texmf-fonts-2007-40.fc16.noarch 1/1 Error unpacking rpm package texlive-texmf-fonts-2007-40.fc16.noarch error: unpacking of archive failed on file /usr/share/texmf/fonts/type1/bluesky/cm/cmssi17.pfb: cpio: rename Verifying : texlive-texmf-fonts-2007-40.fc16.noarch 1/1 Failed: texlive-texmf-fonts.noarch 0:2007-40.fc16
(In reply to comment #16) > Running Transaction > Installing : texlive-texmf-fonts-2007-40.fc16.noarch 1/1 > Error unpacking rpm package texlive-texmf-fonts-2007-40.fc16.noarch > error: unpacking of archive failed on file > /usr/share/texmf/fonts/type1/bluesky/cm/cmssi17.pfb: cpio: rename > Verifying : texlive-texmf-fonts-2007-40.fc16.noarch 1/1 > Failed: > texlive-texmf-fonts.noarch 0:2007-40.fc16 Looks like something is wrong with that file. Can you please try to completely remove it (maybe with --nodeps) and reinstall it again? Maybe you could also clean the yum cache (yum clean all), as the copy in cache could be corrupted. Alternatively you could try to download (and install) the file again from here: http://koji.fedoraproject.org/koji/buildinfo?buildID=272797 Anyway, I would say that this is NOTABUG; the other one (crash on exit, 303472) of course is a bug.
I removed fonts together with all dependent files, clean the yum cache and reinstalled TeX. Now all is OK (including stable exiting from Okular). Thanks for all. P.S. I saved the corrupted font file (its length is much shorter than of length of new file) if it will be needed to reproduce crash of Okular.
(In reply to comment #18) > P.S. I saved the corrupted font file (its length is much shorter than of > length of new file) if it will be needed to reproduce crash of Okular. I was able to reproduce the issue as well by injecting garbage in that file; just to be sure, please attach it to the other bug. Thanks for caring about Okular! I'm moving the substate of this bug to INVALID as it was not really a bug (i.e. the "-" was not shown because the font was not available).
Agreed with Luigi this is not our bug, but you should probably open a bug into fedora bug tracker and investigate why the font got corrupted in the first place
Now I agree of course that the corrupted fonts it is not a bug of Okular. But initially it was not obvious for me that it is a problem with fonts: strange displaying of formulas (which was not happened before in simple formulas with usual fonts) together with crashing Okular (with Kile!) when I return to Editor (Kile) to check the formulas. All this was too strange for me and I decided that all this is a bug of Okular. About opening a bug in fedora: I do not know is it a bug. I can not say when this problem have arisen. Maybe it was happened because I killed a relevant process some time ago. With so small information I am not sure that it is possible to trace a bug (if it is a bug).