The bug is not fixed by replacing Gutsy's Ghostscript with the official 8.61 release. The bug simply only appears if Ghostscript is built as a dynamic library, as it is done in Gutsy. The users who solved the problem with the official release compiled Ghostscript statically (the default behavior when simply doing "./configure; make; sudo make install") and therefore the problem disappeared for them.
The bug occurs only if all of these conditions are fulfilled:
1. The input file is a Postscript file generated by Acrobat from an encrypted PDF file.
2. Ghostscript is built as a library (i.e. "make so", as Gutsy's Ghostscript).
3. The input file is sent to Ghostcript via "- <filename" or "cat filename | gs -" (printing system call Ghostscript this way).
Under these conditions it also occurs with the released Ghostscript 8.61.
The bug is not fixed by replacing Gutsy's Ghostscript with the official 8.61 release. The bug simply only appears if Ghostscript is built as a dynamic library, as it is done in Gutsy. The users who solved the problem with the official release compiled Ghostscript statically (the default behavior when simply doing "./configure; make; sudo make install") and therefore the problem disappeared for them.
See
http:// bugs.ghostscrip t.com/show_ bug.cgi? id=689577
The bug occurs only if all of these conditions are fulfilled:
1. The input file is a Postscript file generated by Acrobat from an encrypted PDF file.
2. Ghostscript is built as a library (i.e. "make so", as Gutsy's Ghostscript).
3. The input file is sent to Ghostcript via "- <filename" or "cat filename | gs -" (printing system call Ghostscript this way).
Under these conditions it also occurs with the released Ghostscript 8.61.