New gs breaks transparency of epstopdf

Bug #33255 reported by Gustavo Carneiro
6
Affects Status Importance Assigned to Milestone
GS-GPL
Fix Released
Medium
ghostscript (Ubuntu)
Fix Released
Medium
Unassigned
gs-esp (Ubuntu)
Invalid
Medium
Unassigned
imagemagick (Debian)
Fix Released
Unknown

Bug Description

I have an eps file which loses transparency information in some places when converted to pdf using epstopdf. This bug doesn't happen in breezy, only in dapper.

In both systems epstopdf gives me:
EPSTOPDF 2.7, 2001/03/05 - Copyright 1998-2001 by Sebastian Rahtz et al.

In breezy, gs --version is 8.01. In dapper, I have now 8.15.1. I assume it's the different gs version that's causing this.

Revision history for this message
Gustavo Carneiro (gjc) wrote : original eps file

original eps file

Revision history for this message
Gustavo Carneiro (gjc) wrote : file converted in dapper

you'll notice the first box (mobile node) is transparent and it shouldn't; it's easy to see in acrobat reader with transparency grid activated

Revision history for this message
Gustavo Carneiro (gjc) wrote : file converted in breezy

this file converted in breezy is ok

Matt Zimmerman (mdz)
Changed in gs-gpl:
assignee: nobody → ijackson
Revision history for this message
Ian Jackson (ijackson) wrote :

I have investigated this and reproduced it. It is an algorithmic error in gs. I'm not sure of the correct solution, I'm afraid, so I haven't fixed it.

The bug will happen whenever the first drawing operation in the file is a white fill. If you have some control over the order of objects in the .eps file, you may be able to work around it. For example, if you draw a non-white object underneath the white fill, the bug will go away.

I have reported the bug upstream, at
 http://bugs.ghostscript.com/show_bug.cgi?id=688641

Changed in gs-gpl:
status: Unconfirmed → Confirmed
Ian Jackson (ijackson)
Changed in gs-esp:
assignee: nobody → ijackson
Changed in gs-gpl:
status: Unconfirmed → Fix Released
Revision history for this message
Ian Jackson (ijackson) wrote :

I propose not to apply the patch from upstream unless this is a serious problem for you. Please let me know if my suggested workaround isn't sufficient.

The fix will be deployed in Ubuntu in due course, via upstream and Debian.

Thanks.

Changed in gs-gpl:
assignee: ijackson → nobody
Changed in gs-esp:
assignee: ijackson → nobody
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Bug still persists in ESP GhostScript 8.15.4. So a fix will only be using GPL GhostScript (which will be the default soon, after the upcoming ESP/GPL GhostScript merger). Please try gs-gpl and tell whether this fixes your problem.

Changed in gs-esp:
status: Unconfirmed → Needs Info
Changed in gs-gpl:
status: Confirmed → Needs Info
Revision history for this message
Gustavo Carneiro (gjc) wrote :

With current gs-gpl in Feisty (8.54), the problem remains.

Changed in gs-gpl:
status: Needs Info → Confirmed
Changed in gs-esp:
status: Needs Info → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote : Re: [GPL GS DOES NOT WORK] New gs breaks transparency of epstopdf

ESP Ghostscript is not developed upstream any more and replaced by GPL Ghostscript -> removing gs-esp task

Changed in gs-esp:
status: Confirmed → Rejected
Changed in gs-gpl:
status: Confirmed → Fix Committed
Changed in ghostscript:
status: Fix Committed → Fix Released
Changed in gs-gpl:
importance: Unknown → Medium
Changed in imagemagick (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.