Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56105 - [mupdf] rendering issue

Attached to Project: Community Packages
Opened by Vijay Marupudi (vijaygopalmarupudi) - Tuesday, 24 October 2017, 14:25 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 09 January 2019, 07:47 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: mupdf does not properly show LaTeX like symbols.


Additional info:
* package version(s): 1.11-4
* config and/or log files etc.


Steps to reproduce: Open attached file using mupdf <filename> from terminal.


   Lecture 12.pdf (1.54 MiB)
This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 09 January 2019, 07:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  recent version
Comment by Mohammed Yaseen Mowzer (moyamo) - Wednesday, 06 December 2017, 06:48 GMT
So I'm having the same problem, both with zathura-pdf-mupdf and with the standalone mupdf. Downgrading zathura-pdf-mupdf to a version where it worked didn't fix the issue. So the problem is probably not with mupdf but a configuration issue or a problem with a related library.
Comment by naruto (narutowindy) - Friday, 18 May 2018, 04:02 GMT
damn, i thougt my pdfs are corrupted !! i think images are not showing in the rendering .... please fix issue, cant read books....
Comment by Mohammed Yaseen Mowzer (moyamo) - Friday, 18 May 2018, 07:23 GMT
Strangely enough, this bug seems to have fixed itself for me. @naruto this bug was about symbols (text in a certain font) not showing. Not about images not displaying.
Comment by naruto (narutowindy) - Friday, 18 May 2018, 17:26 GMT
hmm not fixed for me, still showing rendering errors and warnings....
Comment by Andrew Carlotti (ACarlotti) - Saturday, 21 July 2018, 10:48 GMT
naruto: It looks like you have a different bug to the original poster, but one that I just reported at https://bugs.archlinux.org/task/59410 as a new bug. Can you check whether my issue is the same, and comment on that bug about whether or not you can reproduce it?
Comment by Ivy Foster (escondida) - Tuesday, 08 January 2019, 23:09 GMT
As far as I can tell, this no longer seems to be present in 1.14.0-1. Anybody who looked at this previously want to confirm and close?
Comment by Mohammed Yaseen Mowzer (moyamo) - Wednesday, 09 January 2019, 05:23 GMT
As I said before this seems to have fixed itself for me. @eworm should probably confirm, since they originally reported the bug.
Comment by Christian Hesse (eworm) - Wednesday, 09 January 2019, 07:47 GMT
I am the assignee, not the reporter.
However the attached PDF file looks good to me. In lack of a bad example... Probably fixed.

Loading...