[GPL GS WORKS] gs-esp in dapper (gs-esp_8.15) not working

[Roland Orre]

gs-esp in dapper does not open a window. Try e.g. cd /usr/share/cups/data
gs-esp testprint.ps
it hangs.
gs-gpl testprint.ps
works fine.
I tried to downgrade through breezy-backports
by downloading
gs-esp_7.07.1-9ubuntu5_i386.deb
libcupsys2-gnutls10_1.1.23-10ubuntu4_i386.deb
but that causes conflict with libcupsys2, which
it shouldn't, as this should be a backport (downloaded by searching with web interface)
For now I copied the gs-esp (7.07) binary from another
machine running breezy, that works.

[Ante Karamatić (ivoks)]

It doesn't hang. It's fully functional. It just doesn't open a window. I'm actully not sure it should open window...

[Roland Orre (roland-orre)]

gs-esp has always worked equivalent to gs-gpl before, and
it is also considered to be an alternative ackording to
/etc/alternatives/gs
if I have understood it right, which may point to
/usr/bin/gs-gpl or /usr/bin/gs-esp
This gs is also used by gv, so if you bind /etc/alternatives/gs
to the dapper version of gs-esp gv is no longer working.

It is from all points of view good to have more than one
postscript interpreter available when having problem with
a postscript file (even though the main purpose of gs-esp
may be to be a printer interface).

On 6/4/06, Ante Karamatić <email address hidden> wrote:
> It doesn't hang. It's fully functional. It just doesn't open a window.
> I'm actully not sure it should open window...
>
> ** Changed in: cupsys (Ubuntu)
> Status: Unconfirmed => Confirmed
>
> ** Changed in: cupsys (Ubuntu)
> Sourcepackagename: cupsys => gs-esp
>
> --
> gs-esp in dapper (gs-esp_8.15) not working
> https://launchpad.net/bugs/47458
>

[Tiago Cogumbreiro (cogumbreiro)]

On my computer gs-eps hangs and hogs the system resources. gv and epstopdf were hanging and slowing the system alot. Don't know if it is the same problem though. Changing to gs-gpl fixes problem.

[Roland Orre (roland-orre)]

It showed to not really be a bug, just that default device was not x11,
it was bbox. This could be fixed by either
gs-esp -sDEVICE=x11
or
export GS_DEVICE=x11
but for convenience I preferred the following change in
/usr/share/gs-esp/8.15/lib/gs_init.ps

% Acquire environment variables.
%currentdict /DEVICE known not
% { (GS_DEVICE) getenv { /DEVICE exch def } if } if

/DEFAULTDEVICE (x11) def

currentdict /DEVICE known not
 { (GS_DEVICE) getenv {/DEVICE exch def }
                      {/DEVICE DEFAULTDEVICE def } ifelse } if