ghostscript in Ubuntu 18.04 [on hold]
up vote
1
down vote
favorite
I am experiencing lots of issues with postscript files since I upgraded to Ubuntu 18.04. I cannot visualize them with gv, evince, or other similar programs. I cannot parse them into ImageMagick. Here are some examples of the error messages I get:
$ convert test1.ps test1.png
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
convert-im6.q16: no images defined `test1.png' @ error/convert.c/ConvertImageCommand/3258.
This is the error message I get with gv:
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stoppeGPL Ghostscript 9.25: Unrecoverable error, exit code 1
d_push --nostringval-- --nostringval--
Dictionary stack:
--dict:969/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
The problem is not in the file, I tested it with many files where it used to work with Ubuntu 16.04. I believe that this is in line with the various security measures adopted with ghostscript 9.25 in Ubuntu 18.04, and I suspect that it's the same root cause of other problems recently discussed in this site.
Is there a workaround?
Thanks!
18.04 ghostscript postscript
asked Oct 22 at 7:59
Deky740
163
put on hold as off-topic by Zanna, Tom Brossman, MadMike, Thomas, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – MadMike, Eric Carvalho
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Zanna, Tom Brossman, Thomas
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
1
down vote
favorite
I am experiencing lots of issues with postscript files since I upgraded to Ubuntu 18.04. I cannot visualize them with gv, evince, or other similar programs. I cannot parse them into ImageMagick. Here are some examples of the error messages I get:
$ convert test1.ps test1.png
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
convert-im6.q16: no images defined `test1.png' @ error/convert.c/ConvertImageCommand/3258.
This is the error message I get with gv:
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stoppeGPL Ghostscript 9.25: Unrecoverable error, exit code 1
d_push --nostringval-- --nostringval--
Dictionary stack:
--dict:969/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
The problem is not in the file, I tested it with many files where it used to work with Ubuntu 16.04. I believe that this is in line with the various security measures adopted with ghostscript 9.25 in Ubuntu 18.04, and I suspect that it's the same root cause of other problems recently discussed in this site.
Is there a workaround?
Thanks!
18.04 ghostscript postscript
asked Oct 22 at 7:59
Deky740
163
put on hold as off-topic by Zanna, Tom Brossman, MadMike, Thomas, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – MadMike, Eric Carvalho
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Zanna, Tom Brossman, Thomas
If this question can be reworded to fit the rules in the help center, please edit the question.
Post the output ofcat /etc/ImageMagick-6/policy.xml | grep '"PS"'
– abu_bua
Oct 29 at 12:49
$ cat /etc/ImageMagick-6/policy.xml | grep '"PS"' <policy domain="coder" rights="read|write" pattern="PS" /> Thank you for your interest!
– Deky740
Oct 30 at 8:04
that's ok, seems really to be a bug.
– abu_bua
Oct 30 at 8:34
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am experiencing lots of issues with postscript files since I upgraded to Ubuntu 18.04. I cannot visualize them with gv, evince, or other similar programs. I cannot parse them into ImageMagick. Here are some examples of the error messages I get:
$ convert test1.ps test1.png
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
convert-im6.q16: no images defined `test1.png' @ error/convert.c/ConvertImageCommand/3258.
This is the error message I get with gv:
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stoppeGPL Ghostscript 9.25: Unrecoverable error, exit code 1
d_push --nostringval-- --nostringval--
Dictionary stack:
--dict:969/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
The problem is not in the file, I tested it with many files where it used to work with Ubuntu 16.04. I believe that this is in line with the various security measures adopted with ghostscript 9.25 in Ubuntu 18.04, and I suspect that it's the same root cause of other problems recently discussed in this site.
Is there a workaround?
Thanks!
18.04 ghostscript postscript
asked Oct 22 at 7:59
Deky740
163
I am experiencing lots of issues with postscript files since I upgraded to Ubuntu 18.04. I cannot visualize them with gv, evince, or other similar programs. I cannot parse them into ImageMagick. Here are some examples of the error messages I get:
$ convert test1.ps test1.png
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
Dictionary stack:
--dict:972/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
convert-im6.q16: no images defined `test1.png' @ error/convert.c/ConvertImageCommand/3258.
This is the error message I get with gv:
Error: /nocurrentpoint in --currentpoint--
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 2015 1 3 %oparray_pop 2014 1 3 %oparray_pop --nostringval-- 1998 1 3 %oparray_pop 1884 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stoppeGPL Ghostscript 9.25: Unrecoverable error, exit code 1
d_push --nostringval-- --nostringval--
Dictionary stack:
--dict:969/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)--
Current allocation mode is local
Current file position is 774
The problem is not in the file, I tested it with many files where it used to work with Ubuntu 16.04. I believe that this is in line with the various security measures adopted with ghostscript 9.25 in Ubuntu 18.04, and I suspect that it's the same root cause of other problems recently discussed in this site.
Is there a workaround?
Thanks!
18.04 ghostscript postscript
18.04 ghostscript postscript
asked Oct 22 at 7:59
Deky740
163
asked Oct 22 at 7:59
Deky740
163
asked Oct 22 at 7:59
Deky740
163
asked Oct 22 at 7:59
Deky740
163
asked Oct 22 at 7:59
Deky740
163
163
put on hold as off-topic by Zanna, Tom Brossman, MadMike, Thomas, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – MadMike, Eric Carvalho
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Zanna, Tom Brossman, Thomas
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by Zanna, Tom Brossman, MadMike, Thomas, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – MadMike, Eric Carvalho
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Zanna, Tom Brossman, Thomas
If this question can be reworded to fit the rules in the help center, please edit the question.
Post the output ofcat /etc/ImageMagick-6/policy.xml | grep '"PS"'
– abu_bua
Oct 29 at 12:49
$ cat /etc/ImageMagick-6/policy.xml | grep '"PS"' <policy domain="coder" rights="read|write" pattern="PS" /> Thank you for your interest!
– Deky740
Oct 30 at 8:04
that's ok, seems really to be a bug.
– abu_bua
Oct 30 at 8:34
add a comment |
Post the output ofcat /etc/ImageMagick-6/policy.xml | grep '"PS"'
– abu_bua
Oct 29 at 12:49
$ cat /etc/ImageMagick-6/policy.xml | grep '"PS"' <policy domain="coder" rights="read|write" pattern="PS" /> Thank you for your interest!
– Deky740
Oct 30 at 8:04
that's ok, seems really to be a bug.
– abu_bua
Oct 30 at 8:34
Post the output of
cat /etc/ImageMagick-6/policy.xml | grep '"PS"'– abu_bua
Oct 29 at 12:49
Post the output of
cat /etc/ImageMagick-6/policy.xml | grep '"PS"'– abu_bua
Oct 29 at 12:49
$ cat /etc/ImageMagick-6/policy.xml | grep '"PS"' <policy domain="coder" rights="read|write" pattern="PS" /> Thank you for your interest!
– Deky740
Oct 30 at 8:04
$ cat /etc/ImageMagick-6/policy.xml | grep '"PS"' <policy domain="coder" rights="read|write" pattern="PS" /> Thank you for your interest!
– Deky740
Oct 30 at 8:04
that's ok, seems really to be a bug.
– abu_bua
Oct 30 at 8:34
that's ok, seems really to be a bug.
– abu_bua
Oct 30 at 8:34
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
Thanks to abu_bua and karel for their feedback.
The latest patch of updates fixed the problem, now ghostscript works as expected.
edited Nov 21 at 11:52
abu_bua
3,05381023
answered Nov 21 at 8:56
Deky740
163
1
This seems to be an answer... the problem went away after a system update. Maybe the problem can be considered not-reproducible.
– Zanna
Nov 21 at 9:29
add a comment |
up vote
0
down vote
convert doesn't work in 18.04 for either .ps or .eps files. This is a bug in 18.04. Open the .ps file in GIMP image editor instead. GIMP can convert .ps and .eps files to any of its supported image formats.
answered Oct 29 at 7:53
karel
55.1k11121139
Thank you for the suggestion! Unfortunately, that doesn't work either. The problem is that gimp also relies on ghostscript to interpret ps files.
– Deky740
Oct 30 at 8:06
@Deky740 My GIMP works OK in 18.04 and I also tested Inkscape in 18.04 which works at converting .ps files too. I made the .ps file I tested using a graphical programming language called dot, so I know the .ps file that I tested is not corrupted.
– karel
Oct 30 at 8:13
Thanks for the suggestion, @karel. I tried again, both GIMP and Inkscape, and in both cases it fails to import the ps file, with the same error.
– Deky740
Oct 31 at 11:41
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Thanks to abu_bua and karel for their feedback.
The latest patch of updates fixed the problem, now ghostscript works as expected.
edited Nov 21 at 11:52
abu_bua
3,05381023
answered Nov 21 at 8:56
Deky740
163
1
This seems to be an answer... the problem went away after a system update. Maybe the problem can be considered not-reproducible.
– Zanna
Nov 21 at 9:29
add a comment |
up vote
1
down vote
Thanks to abu_bua and karel for their feedback.
The latest patch of updates fixed the problem, now ghostscript works as expected.
edited Nov 21 at 11:52
abu_bua
3,05381023
answered Nov 21 at 8:56
Deky740
163
1
This seems to be an answer... the problem went away after a system update. Maybe the problem can be considered not-reproducible.
– Zanna
Nov 21 at 9:29
add a comment |
up vote
1
down vote
up vote
1
down vote
Thanks to abu_bua and karel for their feedback.
The latest patch of updates fixed the problem, now ghostscript works as expected.
edited Nov 21 at 11:52
abu_bua
3,05381023
answered Nov 21 at 8:56
Deky740
163
Thanks to abu_bua and karel for their feedback.
The latest patch of updates fixed the problem, now ghostscript works as expected.
edited Nov 21 at 11:52
abu_bua
3,05381023
answered Nov 21 at 8:56
Deky740
163
edited Nov 21 at 11:52
abu_bua
3,05381023
edited Nov 21 at 11:52
abu_bua
3,05381023
edited Nov 21 at 11:52
abu_bua
3,05381023
3,05381023
answered Nov 21 at 8:56
Deky740
163
answered Nov 21 at 8:56
Deky740
163
answered Nov 21 at 8:56
Deky740
163
163
1
This seems to be an answer... the problem went away after a system update. Maybe the problem can be considered not-reproducible.
– Zanna
Nov 21 at 9:29
add a comment |
1
This seems to be an answer... the problem went away after a system update. Maybe the problem can be considered not-reproducible.
– Zanna
Nov 21 at 9:29
1
1
This seems to be an answer... the problem went away after a system update. Maybe the problem can be considered not-reproducible.
– Zanna
Nov 21 at 9:29
This seems to be an answer... the problem went away after a system update. Maybe the problem can be considered not-reproducible.
– Zanna
Nov 21 at 9:29
add a comment |
up vote
0
down vote
convert doesn't work in 18.04 for either .ps or .eps files. This is a bug in 18.04. Open the .ps file in GIMP image editor instead. GIMP can convert .ps and .eps files to any of its supported image formats.
answered Oct 29 at 7:53
karel
55.1k11121139
Thank you for the suggestion! Unfortunately, that doesn't work either. The problem is that gimp also relies on ghostscript to interpret ps files.
– Deky740
Oct 30 at 8:06
@Deky740 My GIMP works OK in 18.04 and I also tested Inkscape in 18.04 which works at converting .ps files too. I made the .ps file I tested using a graphical programming language called dot, so I know the .ps file that I tested is not corrupted.
– karel
Oct 30 at 8:13
Thanks for the suggestion, @karel. I tried again, both GIMP and Inkscape, and in both cases it fails to import the ps file, with the same error.
– Deky740
Oct 31 at 11:41
add a comment |
up vote
0
down vote
convert doesn't work in 18.04 for either .ps or .eps files. This is a bug in 18.04. Open the .ps file in GIMP image editor instead. GIMP can convert .ps and .eps files to any of its supported image formats.
answered Oct 29 at 7:53
karel
55.1k11121139
Thank you for the suggestion! Unfortunately, that doesn't work either. The problem is that gimp also relies on ghostscript to interpret ps files.
– Deky740
Oct 30 at 8:06
@Deky740 My GIMP works OK in 18.04 and I also tested Inkscape in 18.04 which works at converting .ps files too. I made the .ps file I tested using a graphical programming language called dot, so I know the .ps file that I tested is not corrupted.
– karel
Oct 30 at 8:13
Thanks for the suggestion, @karel. I tried again, both GIMP and Inkscape, and in both cases it fails to import the ps file, with the same error.
– Deky740
Oct 31 at 11:41
add a comment |
up vote
0
down vote
up vote
0
down vote
convert doesn't work in 18.04 for either .ps or .eps files. This is a bug in 18.04. Open the .ps file in GIMP image editor instead. GIMP can convert .ps and .eps files to any of its supported image formats.
answered Oct 29 at 7:53
karel
55.1k11121139
convert doesn't work in 18.04 for either .ps or .eps files. This is a bug in 18.04. Open the .ps file in GIMP image editor instead. GIMP can convert .ps and .eps files to any of its supported image formats.
answered Oct 29 at 7:53
karel
55.1k11121139
answered Oct 29 at 7:53
karel
55.1k11121139
answered Oct 29 at 7:53
karel
55.1k11121139
answered Oct 29 at 7:53
karel
55.1k11121139
55.1k11121139
Thank you for the suggestion! Unfortunately, that doesn't work either. The problem is that gimp also relies on ghostscript to interpret ps files.
– Deky740
Oct 30 at 8:06
@Deky740 My GIMP works OK in 18.04 and I also tested Inkscape in 18.04 which works at converting .ps files too. I made the .ps file I tested using a graphical programming language called dot, so I know the .ps file that I tested is not corrupted.
– karel
Oct 30 at 8:13
Thanks for the suggestion, @karel. I tried again, both GIMP and Inkscape, and in both cases it fails to import the ps file, with the same error.
– Deky740
Oct 31 at 11:41
add a comment |
Thank you for the suggestion! Unfortunately, that doesn't work either. The problem is that gimp also relies on ghostscript to interpret ps files.
– Deky740
Oct 30 at 8:06
@Deky740 My GIMP works OK in 18.04 and I also tested Inkscape in 18.04 which works at converting .ps files too. I made the .ps file I tested using a graphical programming language called dot, so I know the .ps file that I tested is not corrupted.
– karel
Oct 30 at 8:13
Thanks for the suggestion, @karel. I tried again, both GIMP and Inkscape, and in both cases it fails to import the ps file, with the same error.
– Deky740
Oct 31 at 11:41
Thank you for the suggestion! Unfortunately, that doesn't work either. The problem is that gimp also relies on ghostscript to interpret ps files.
– Deky740
Oct 30 at 8:06
Thank you for the suggestion! Unfortunately, that doesn't work either. The problem is that gimp also relies on ghostscript to interpret ps files.
– Deky740
Oct 30 at 8:06
@Deky740 My GIMP works OK in 18.04 and I also tested Inkscape in 18.04 which works at converting .ps files too. I made the .ps file I tested using a graphical programming language called dot, so I know the .ps file that I tested is not corrupted.
– karel
Oct 30 at 8:13
@Deky740 My GIMP works OK in 18.04 and I also tested Inkscape in 18.04 which works at converting .ps files too. I made the .ps file I tested using a graphical programming language called dot, so I know the .ps file that I tested is not corrupted.
– karel
Oct 30 at 8:13
Thanks for the suggestion, @karel. I tried again, both GIMP and Inkscape, and in both cases it fails to import the ps file, with the same error.
– Deky740
Oct 31 at 11:41
Thanks for the suggestion, @karel. I tried again, both GIMP and Inkscape, and in both cases it fails to import the ps file, with the same error.
– Deky740
Oct 31 at 11:41
add a comment |
Post the output of
cat /etc/ImageMagick-6/policy.xml | grep '"PS"'– abu_bua
Oct 29 at 12:49
$ cat /etc/ImageMagick-6/policy.xml | grep '"PS"' <policy domain="coder" rights="read|write" pattern="PS" /> Thank you for your interest!
– Deky740
Oct 30 at 8:04
that's ok, seems really to be a bug.
– abu_bua
Oct 30 at 8:34