The choice of simply not using the flag with ghostscript is a false
choice for most users, given ghostscript is used under the hood by a
number of applications. A cursory search for the error message on the
internet shows a number of related consequences, including pstoedit and
inkscape which uses pstoedit.

The notion that there's just a warning isn't true as well. The change
breaks pstoedit. The broken pstoedit breaks inkscape (Export to SVG).
This might well be bad code on the pstoedit side, but it's still a
change that breaks the (relative) userspace.

There's a description of what seems to have happened at 
https://bugs.launchpad.net/inkscape/+bug/1734624/comments/21

Specifically, the version of pstoedit included in 18.04 is not likely to
be compatible with the included version of ghostscript. Applications
depending on pstoedit will be broken on this release. Any other
applications directly depending on ghostscript and using DELAYBIND might
have similar trouble.

The pstoedit folk added a workaround specific to ghostscript 9.22 in
pstoedit 3.71. If pstoedit is bumped up to 3.71, it would be possible
for direct users of pstoedit to workaround with -rdb. This would
probably leave inkscape still broken because it uses pstoedit under the
hood.

Given 18.04 is an LTS, a solution does have to be found by and for
Ubuntu 18.04, or both pstoedit and inkscape will have issues for the
entire life of this release. The possible options I see are :

 * Upgrade ghostscript to 9.23, hopefully not resulting in any additional 
breakage.
 * Upgrade pstoedit to 3.71, so atleast the -rdb workaround will exist for 
direct users, but leaves inkscape partially broken.
 * Deal with ghostscipt upstream and find a way to patch in that one option 
back to 9.22, upgrade ghostscript to a patch release of 9.22. If DELAYBIND 
really does nothing useful, this should not be very difficult. However, the 
comments from their bugzilla listed above suggest ghostscript seems adamant 
this isn't their problem.
 * Deal with pstoedit upstream and find a way to patch 3.70 to include the -rdb 
workaround, upgrade to the next patch release of pstoedit, make users of it 
able to use pstoedit again even if inkscape remains broken.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785107

Title:
  Ghostscript and pstoedit versions not compatible in 18.04 Bionic
  Beaver

To manage notifications about this bug go to:
https://bugs.launchpad.net/pstoedit/+bug/1785107/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to