Summary: | cannot display file content and crash on exit | ||
---|---|---|---|
Product: | [Applications] kghostview | Reporter: | Alias <jerome> |
Component: | general | Assignee: | Wilco Greven <greven> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | dummy postscript file created by SO 5.2 |
Description
Alias
2002-10-21 21:12:54 UTC
Please send in the file if the bug persists, closing for now... Can't reproduce behaviour with SO6 generated PS files. i don't think, the problem is due only to SO5.2 output file but instead, that it is a GNU gs pb. I could display SO5.2 output file before upgrading to KDE3.0 (gs was upgraded too). As I wrote, with anti-aliasing on, gv cannot display the file, it brings a error message and stop. The pb of kghostview is, that it doesn't display anything and doesn't show any error message. As you can't stop it, you have to exit. When exiting, kghostview crashes. So, although, you cannot probably solve entirely the pb (if it's a GNU gs one), you could prevent kghostview not to display an error message for instance and also that it crashes on exit. If you need more info, please ask. Can anyone post a testfile from SO 5.2 ? Created attachment 1326 [details]
dummy postscript file created by SO 5.2
I am sending a file created by SO5.2 It can't be displayed by kghostview when
antialiasing is on. No crash on exit. (It happened when I reported the bug,
can't reproduce it now)
It crashes for me if you do the following: option antialiasing is off
call kghostview test-so5.2.ps
content is displayed
go in option and select antialiasing on
content vanishes
and kghostview crashes on exit
message on console: KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kghostview path = <unknown> pid = 27590
kbug pops up
---
as I previously wrote, gv can't display the file when antialiasing is on
so it could be that this version of gs is buggy (6.52) At least gv doesn't
crash.
hope it helps
I had to reboot twice because of that file, once for gs 7.05 another for gs 6.52, but I was trying pure gs ("gs file.ps"). gs allocates too much memory and everything becomes unusable. kghostview uses another method (dsc structure) to guess the size of the pixmap it will allocate and so it doesn't crash. So, the display problems come from gs (or from StarOffice, which is generating broken postscript). I have already realised that kghostview doesn't tell you anything when gs fails and I will solve it really soon (I have a patch in my computer, but my copy if half-broken and I wanted to talk to Wilco who is the maintainer first .... but it will be in CVS in a few days). I also think that this issue has come up in another report where we established that gs was failing and kghostview wasn't saying anything and this needed to be fixed. If I find that bug, I will mark this as a duplicate. Interestingly, if you do ps2ps brokenFile.ps brokenFileFixed.ps you will get a file which will work perfectly with gs and be viewable with kghostview although kghostview will guess the paper-size wrong (kghostview uses the DSC structure which gs ignores when parsing. ps2ps which hangs on gs generates DSC structure but apparently here it is wrong). If you like this sort of thing, iterating through ps2ps will get you an alternating sequence after n=2 (consider n=0 to be the original broken file). Here is my reasoning: - That rendering fails is INVALID bc it is gs's fault. - That we don't tell the user (and sometimes crash) is a DUPLICATE So, I mark it as a DUPLICATE. Thank you for reporting. Do so again if you find other bugs. luis pedro coelho *** This bug has been marked as a duplicate of 56521 *** |