Description of problem: klatexformula uses pswrite as the output device for gs, but gs does not have that output device anymore. There is a ps2write which may be equivalent. There is also an epswrite gs device. But klatexformula needs to be altered to use an existing device. Version-Release number of selected component (if applicable): klatexformula 3.2.7-2.mga4 ghostscript 9.10-2.mga4 How reproducible: Run klatexformla and type in any expression and hit evaluate An error message about pswrite will pop up. Always. klatexformula is useless with this error. Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
The problem seems to be in grep -r 'pswrite' . ./klatexformula-3.2.7/src/klfbackend/klfbackend.cpp: << "-sDEVICE=pswrite" << "-sOutputFile="+dir_native_separators(fnOutlFontsEps)
See the discussion in https://bugs.launchpad.net/ubuntu/+source/klatexformula/+bug/1296902 where it is stated that klatexformula 3.2.8 fixes this bug for Ubuntu.
The latest non-beta release is 3.2.11 which I have compiled into an rpm (by minimally changing the klatexformula.spec file). It does seem to fix this bug, but I have not tested it sufficiently to know that other bugs do not lurk there. (I cannot attach the src.rpm, it is too big)
Luc updated it to 3.2.11 in Cauldron, maybe it can be updated for 4.
CC: (none) => mageiaAssignee: bugsquad => lmenutSource RPM: klatexformula and ghostscript => klatexformulaSeverity: critical => normal
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD