artifex | a library for constructing geometric data | Data Manipulation library

The following command outside python runs for me no problem.

There are several ways to convert image to PDF and this is possibly not the best way to convert Jpeg to PDF in Ghostscript, but you asked why it did not work for you.

The following should in a cmd file, first work per the example, once proven then try changing the <> of the last line that you think need altering. Note that long lines are very fragile and there must be NO space after ^

Also the order and combinations can easily throw GS into an error state. CMD Filenames are best always "FullPath\quoted" and if you don't want to inititally CD to the output directory (to make it much easier to avoid using escaped name) then change the start of last line to

-c "("C:\\Users\\kbged\\Pictures\\group_image.jpg") <<......

Beware the much simpler method would be to write your own input.PS to avoid potential command line truncation.

My original theory that pdfTex was not available to the nginx user was correct.

In my script, I logged the result of which pdftex. This command returned not found. The solution was to create a symlink to the pdftex script. I did this by adding the following to my script.

I managed to figure out a solution. Looking for the code for the Rghost, what I saw in its spec is that the path expected was different than the path the ghostscript really is. When I run whereis or which on my terminal, it returns:

I was working on a company machine. The comment from @Cyrus showed that which is aliased to alias. Doing this worked as it should have:

Recent versions of Ghostscript (unfortunately you've trimmed off the version from stdout, but it's (C) 2020 so it must be fairly recent) have altered the default behaviour, because of security vulnerabilities. The default is now to run in SAFER mode (previously the default was NOSAFER). This means that PostScript programs are not permitted to open/read/write/delete files on disk.

It looks like the file you are running is encountering an invalidfileaccess error when trying to write a file. The filename it's trying to write '00002dc' isn't mentioned as the output file on the Ghostscript command line, and that's the only way Ghostscript has of inferring that a file access should be permitted. Basically if the file isn't named on the command line, and you haven't told GS that it has permission to read/write to the given directory, then it's not permitted to access that file.

You could try using -dNOSAFER, I've no real idea how to add this to gsprint, which is not part of Ghostscript, but possibly (reading the gsprint.htm file) -option "-dNOSAFER" might work.

I wouldn't really recommend that as a long-term solution though.

You have started arbitrary PostScript by using the -c switch. From then on everything until the next switch is treated as PostScript.

Your command line does not include any '-' between the closing " and the input filename, so the input filename is treated as part of the PostScript program. Since there is no PostScript token 'E;\temp\myFile.ps' the interpreter gives you an undefined error.

Try putting a -f (-f means treat the next thing as a filename) after the "...setpagedevice".

That said, I'm dubious this will achieve what you want anyway, it depends on what's in the input file. You've used -dEPSCrop yet the filename has a .ps extension. Unless the file is really an EPS then EPSCrop won't have any effect. If it is an EPS then the media size will be the dimensions of the EPS BoundingBox and (I believe) the Orientation will be ignored. If the input file is not an EPS then the EPSCrop will be ignored.

You are using a very elderly version of Ghostscript (7 years old) you should really update.

In the absence of an example file (and ideally the actual command line being sent to Ghostscript) as well as the lack of the back channel output (stout and stderr) the only observation I can make is that the 'option' you refer to (actually a piece of PostScript programming) introduces PostScript input with the -c switch but does not terminate it with -f. That means anything which folows this on the comand line will be treated as more PostScript, which is likely to either lead to an error or a 'hang', awaiting more input.

Ghostscript doesn't process .bmp files, it accepts PDF or PostScript. You could write a PostScript program to place a .bmp image (see for example viewgif.ps) but that's not the same thing at all.

You need an image processing application such as ImageMagick, as suggested by Mark Setchell above.