From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080208 Fedora/2.0.0.12-1.fc8 Firefox/2.0.0.12 Description of problem: When an image is resized using 'poster' and the result is opened with Ghostscript, then ghostscript crashes. Version-Release number of selected component (if applicable): netpbm-progs-10.35.32-2.fc8 poster-20060221-4.fc8 ghostscript-8.61-8.fc8 How reproducible: Always Steps to Reproduce: 1. Use pngtopnm to convert the image to pnm (pngtopnm babytux.png > babytux.pnm) 2. Use pnmtops to convert the image to postscript (pnmtops babytux.pnm > babytux.ps) 3. Use poster to resize the postscript image to A0 (poster -v -s2 babytux.ps > babytux_a0.ps) 4. Try to open the result with ghostscript (ghostscript babytux_a0.ps) Actual Results: Ghostscript crashes with the following output: $ ghostscript babytux_a0.ps GPL Ghostscript 8.61 (2007-11-21) Copyright (C) 2007 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Loading NimbusSanL-Regu font from /usr/share/fonts/default/Type1/n019003l.pfb... 2828064 1117413 2173452 879196 1 done. Error: /limitcheck in -file- Operand stack: print_content_of_complete_page_0 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1889 1 3 %oparray_pop 1888 1 3 %oparray_pop 1872 1 3 %oparray_pop 1755 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push Dictionary stack: --dict:1143/1684(ro)(G)-- --dict:0/20(G)-- --dict:87/200(L)-- Current allocation mode is local Current file position is 77575 GPL Ghostscript 8.61: Unrecoverable error, exit code 1 $ Expected Results: The file should be displayed, or a user-understandable error should be returned. Additional info: It can very well be the case that the 'poster' program does not produce a valid postscript file, but I am unable to determine if this is the case.
See also: http://bugs.kde.org/show_bug.cgi?id=130332 Sending that output.ps file directly to an HP LaserJet 6MP produces no output, so I think the PostScript is incorrect. Changing component to poster.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. 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 Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
The problem still exists in Fedora 10. I am reopening the bug.
Created attachment 328525 [details] The png file
When I open de result file with gsview, then I get this message: GSview 4.8 2006-02-25 play_sound: not implemented debug=0 GPL Ghostscript 8.63 (2008-08-01) Copyright (C) 2008 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Displaying DSC file /home/egon/tmp/poster_test/babytux_a0.ps Displaying page 1 WM_GSTEXTINDEX not implemented Loading NimbusSanL-Regu font from /usr/share/fonts/default/Type1/n019003l.pfb... 2841044 1235422 13048296 11694232 2 done. Error: /limitcheck in --%ztokenexec_continue-- Operand stack: print_content_of_complete_page_0 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- Dictionary stack: --dict:1149/1684(ro)(G)-- --dict:0/20(G)-- --dict:91/200(L)-- Current allocation mode is local --- Begin offending input --- --- End offending input --- file offset = 632044 gsapi_run_string_continue returns -101
Any update on this ? I can't seem to produce any valid output with poster. Evince will display empty pages and ghostscript will display the same error as above.
Created attachment 350423 [details] original file Output of poster : $ poster -v essai.ps > essaibis.ps Using default media of A4 Defaulting poster size to media size of A4 Using default cutmargin of 0% Using default whitemargin of 0 Deciding for 1 column and 1 row of portrait pages. Deciding for a scale factor of 1 print page 1
Created attachment 350425 [details] output file $ poster -v essai.ps > essaibis.ps Using default media of A4 Defaulting poster size to media size of A4 Using default cutmargin of 0% Using default whitemargin of 0 Deciding for 1 column and 1 row of portrait pages. Deciding for a scale factor of 1 print page 1
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. 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 Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This problem still exists: netpbm-10.47.04-1.fc11.i586 poster-20060221-6.fc11.i586 ghostscript-8.70-1.fc11.i586 kind regards, Egon
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. 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 Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This problem still exists in Fedora 12: netpbm-progs-10.47.09-2.fc12.x86_64 ghostscript-8.71-6.fc12.x86_64 poster-20060221-7.fc12.x86_64
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. 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 Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This problem still exists in Fedora 14. netpbm-10.47.17-1.fc14.x86_64 netpbm-progs-10.47.17-1.fc14.x86_64 ghostscript-8.71-16.fc14.x86_64 ================ $ ghostscript babytux_a0.ps GPL Ghostscript 8.71 (2010-02-10) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Can't find (or can't open) font file /usr/share/ghostscript/8.71/Resource/Font/NimbusSanL-Regu. Can't find (or can't open) font file NimbusSanL-Regu. Can't find (or can't open) font file /usr/share/ghostscript/8.71/Resource/Font/NimbusSanL-Regu. Can't find (or can't open) font file NimbusSanL-Regu. Querying operating system for font files... Loading NimbusSanL-Regu font from /usr/share/fonts/default/Type1/n019003l.pfb... 3582792 1884724 7139132 5826710 1 done. Error: /limitcheck in -file- Operand stack: print_content_of_complete_page_0 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1878 1 3 %oparray_pop 1877 1 3 %oparray_pop 1861 1 3 %oparray_pop 1755 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push Dictionary stack: --dict:1150/1684(ro)(G)-- --dict:0/20(G)-- --dict:87/200(L)-- Current allocation mode is local Current file position is 631162 GPL Ghostscript 8.71: Unrecoverable error, exit code 1
This problem still exists in Fedora 15 netpbm-progs-10.47.26-2.fc15.x86_64 netpbm-10.47.26-2.fc15.x86_64 ghostscript-9.02-1.fc15.x86_64
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I think I am going for the record for the longest open bug... -> This problem still exists in Fedora 17
I can confirm this on Fedora 18 as well. A ps file written with poster-20060221-10.fc18.x86_64 crashes gs. poster-20050907-1 (Ubuntu 10.04.4) called with the same input and options produces working ps code. An absolute basic gs file may work, but trying something like a printout of a web page gives broken postscript. Also note the file position at the crash. At least, it's not at the start. 4 years on one bug. 4 more years? Ingvar $ rpm -q poster poster-20060221-10.fc18.x86_64 $ poster -v -mA4 -pA3 webpage_printout.ps > poster.ps Using default cutmargin of 5% Using default whitemargin of 0 Deciding for 1 column and 2 rows of landscape pages. Deciding for a scale factor of 1.23824 print page 1 print page 2 print page 3 print page 4 print page 5 print page 6 print page 7 print page 8 print page 9 print page 10 print page 11 print page 12 $ gs poster.ps GPL Ghostscript 9.06 (2012-08-08) Copyright (C) 2012 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Can't find (or can't open) font file /usr/share/ghostscript/9.06/Resource/Font/NimbusSanL-Regu. Can't find (or can't open) font file NimbusSanL-Regu. Can't find (or can't open) font file /usr/share/ghostscript/9.06/Resource/Font/NimbusSanL-Regu. Can't find (or can't open) font file NimbusSanL-Regu. Querying operating system for font files... Loading NimbusSanL-Regu font from /usr/share/fonts/default/Type1/n019003l.pfb... 3569848 2204763 7136816 5696455 1 done. Error: /syntaxerror in -file- Operand stack: print_content_of_complete_page_0 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1894 1 3 %oparray_pop 1893 1 3 %oparray_pop 1877 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push Dictionary stack: --dict:1161/1684(ro)(G)-- --dict:0/20(G)-- --dict:94/200(L)-- Current allocation mode is local Current file position is 74486 GPL Ghostscript 9.06: Unrecoverable error, exit code 1
Created attachment 646658 [details] Patch that fixes a gs crash This patch reverts some "print_content_of_complete_page" thing introduced in version 20060221 that crashes gs on big files.
Wonder if upstream version 20060221 ever worked anywhere. Attached patch fixes this. Working specfile and f18 src and x86_64 rpms at http://users.linpro.no/ingvar/poster/f18/ Ingvar
Hi Ingvar, I downloaded and tested your RPM. -> It works fine, and fixes the problem! Great work! (where do I send my karma?) ;) kind regards, Egon
The PostScript from the comment #9 is incorrect. It looks like the poster program encloses a PS programs into curly braces and expects it to work as a procedure. Unfortunately, if the program has inline data, it will fail. poster should copy PS program to a %ram% device or an array of strings and execute it from there.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. 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 Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I am afraid that the patch has not made it to an RPM yet. This problem still exists under Fedora with the following RPMs: ghostscript-9.07-3.fc19.x86_64 poster-20060221-11.fc19.x86_64 kind regards, Egon
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This problem does still exist on Fedora 20 and Fedora 21. As the package has not changed in a few years, my patch does still work, though. Ingvar
Any feedback on the provided patch? If no objections, I'll apply it soon to fedora's packaging.
Tested, and works for me on the simple ps files I've ran it on. Covers at least my needs. Patch, updated spec and src.rpm here: http://users.linpro.no/ingvar/poster/f21 Ingvar
This bug is still open, and may be reproduced on f22, as on most earlier fedoras. My patch still works for my needs. Source rpm, x86_64 rpm, patch and specfile for f22 at http://users.linpro.no/ingvar/poster/f22 Ingvar
I'll apply the supplied patch today, but may want to consider retiring poster... since it is dead upstream, see: https://bugs.kde.org/show_bug.cgi?id=130332#c7 "KDEPrint is obsolete, unmaintained and will never be revived."
poster-20060221-17.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/poster-20060221-17.fc22
poster-20060221-17.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/poster-20060221-17.fc21
Package poster-20060221-17.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing poster-20060221-17.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11010/poster-20060221-17.fc22 then log in and leave karma (feedback).
poster-20060221-17.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
poster-20060221-17.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.