New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"GPL Ghostscript 9.21: Can't find initialization file gs_init.ps." error #20

Closed
apjanke opened this Issue Jun 23, 2018 · 7 comments

Comments

1 participant
@apjanke
Contributor

apjanke commented Jun 23, 2018

The error "GPL Ghostscript 9.21: Can't find initialization file gs_init.ps." crops up a bunch when running the test suite.

  plot/util/copyobj.m .........................................GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
 PASS      1/2
                                                                  FAIL    1
...
  plot/util/hgsave.m ..........................................GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
 PASS      3/4
                                                                  FAIL    1
...
  publish.tst .................................................GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
 PASS      2/2
  args.tst .................................................... PASS     26/26
@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

I have a separate Ghostscript installed on my machine (I think as part of MacTeX), which could be interfering with things.

Contributor

apjanke commented Jun 23, 2018

I have a separate Ghostscript installed on my machine (I think as part of MacTeX), which could be interfering with things.

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

Yep, it's the non-Homebrewed Ghostscript confusing things. Here's what my brewed Ghostscript looks like:

$ /usr/local/Cellar/ghostscript/9.23/bin/gs -h
GPL Ghostscript 9.23 (2018-03-21)
...
Search path:
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/9.23/Resource/Init :
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/9.23/lib :
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/9.23/Resource/Font :
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/fonts :
   /usr/local/Cellar/ghostscript/9.23/share/fonts/default/ghostscript :
   /usr/local/Cellar/ghostscript/9.23/share/fonts/default/Type1 :
   /usr/local/Cellar/ghostscript/9.23/share/fonts/default/TrueType :
   /usr/lib/DPS/outline/base : /usr/openwin/lib/X11/fonts/Type1 :
   /usr/openwin/lib/X11/fonts/TrueType

And the brewed Ghostscript under /Applications/Octave-4.4.0.app is also Ghostscript 9.23. Note that the error message is from Ghostscript 9.21. This means that at some point, Octave is calling out to the system-installed Ghostscript instead of the one installed as part of the Homebrew build and pointed to during the configuration process.

Contributor

apjanke commented Jun 23, 2018

Yep, it's the non-Homebrewed Ghostscript confusing things. Here's what my brewed Ghostscript looks like:

$ /usr/local/Cellar/ghostscript/9.23/bin/gs -h
GPL Ghostscript 9.23 (2018-03-21)
...
Search path:
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/9.23/Resource/Init :
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/9.23/lib :
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/9.23/Resource/Font :
   /usr/local/Cellar/ghostscript/9.23/share/ghostscript/fonts :
   /usr/local/Cellar/ghostscript/9.23/share/fonts/default/ghostscript :
   /usr/local/Cellar/ghostscript/9.23/share/fonts/default/Type1 :
   /usr/local/Cellar/ghostscript/9.23/share/fonts/default/TrueType :
   /usr/lib/DPS/outline/base : /usr/openwin/lib/X11/fonts/Type1 :
   /usr/openwin/lib/X11/fonts/TrueType

And the brewed Ghostscript under /Applications/Octave-4.4.0.app is also Ghostscript 9.23. Note that the error message is from Ghostscript 9.21. This means that at some point, Octave is calling out to the system-installed Ghostscript instead of the one installed as part of the Homebrew build and pointed to during the configuration process.

@apjanke apjanke added the bug label Jun 23, 2018

@apjanke apjanke added this to Needs triage in Octave.app via automation Jun 23, 2018

@apjanke apjanke added this to the 4.4.0 milestone Jun 23, 2018

@apjanke apjanke moved this from Needs triage to High priority in Octave.app Jun 23, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

Fixed this by modifying the octave formula to pass "GHOSTSCRIPT=#{Formula["ghostscript_9.23"].opt_bin}/gs" to make, pointing it at the bundled Ghostscript.

In octave-app/homebrew-octave-app@3aaade8.

Contributor

apjanke commented Jun 23, 2018

Fixed this by modifying the octave formula to pass "GHOSTSCRIPT=#{Formula["ghostscript_9.23"].opt_bin}/gs" to make, pointing it at the bundled Ghostscript.

In octave-app/homebrew-octave-app@3aaade8.

@apjanke apjanke closed this Jun 23, 2018

Octave.app automation moved this from High priority to Closed Jun 23, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

While this got rid of the warning messages in the GUI, they still appear when running the test suite in the CLI.

  plot/util/copyobj.m .........................................GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
 PASS      1/2
                                                                  FAIL    1
  plot/util/figure.m .......................................... PASS      5/5
...
  plot/util/hgsave.m ..........................................GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
 PASS      3/4
                                                                  FAIL    1
  plot/util/hold.m ............................................ PASS      2/2

Needs further investigation. Re-opening.

This didn't fix the test failures with copyobj or hgsave, either. They're still failing, with the error messages from #18.


  plot/util/hgsave.m ..........................................
set term qt
         ^
line 0: unknown or ambiguous terminal type; type just 'set terminal' for a list

WARNING: Error during initialization

  ./base/gsicc_manage.c:1172: gsicc_open_search(): Could not find default_rgb.icc
| ./base/gsicc_manage.c:1838: gsicc_set_device_profile(): cannot find device profile
 PASS      3/4
                                                                  FAIL    1
Contributor

apjanke commented Jun 23, 2018

While this got rid of the warning messages in the GUI, they still appear when running the test suite in the CLI.

  plot/util/copyobj.m .........................................GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
 PASS      1/2
                                                                  FAIL    1
  plot/util/figure.m .......................................... PASS      5/5
...
  plot/util/hgsave.m ..........................................GPL Ghostscript 9.21: Can't find initialization file gs_init.ps.
 PASS      3/4
                                                                  FAIL    1
  plot/util/hold.m ............................................ PASS      2/2

Needs further investigation. Re-opening.

This didn't fix the test failures with copyobj or hgsave, either. They're still failing, with the error messages from #18.


  plot/util/hgsave.m ..........................................
set term qt
         ^
line 0: unknown or ambiguous terminal type; type just 'set terminal' for a list

WARNING: Error during initialization

  ./base/gsicc_manage.c:1172: gsicc_open_search(): Could not find default_rgb.icc
| ./base/gsicc_manage.c:1838: gsicc_set_device_profile(): cannot find device profile
 PASS      3/4
                                                                  FAIL    1

@apjanke apjanke reopened this Jun 23, 2018

Octave.app automation moved this from Closed to Needs triage Jun 23, 2018

@apjanke apjanke self-assigned this Jun 23, 2018

@apjanke apjanke moved this from Needs triage to High priority in Octave.app Jun 23, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke
Contributor

apjanke commented Jun 24, 2018

@apjanke apjanke added the upstream label Jun 24, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 24, 2018

Contributor

Fixed in 5f3cd46.

This turned out to be an error I introduced in the GS_OPTIONS paths: I switched to versioned formulae, but didn't update the paths in GS_OPTIONS to respect it; they were still pointing at plain "ghostscript" instead of "ghostscript_". Fixed.

Contributor

apjanke commented Jun 24, 2018

Fixed in 5f3cd46.

This turned out to be an error I introduced in the GS_OPTIONS paths: I switched to versioned formulae, but didn't update the paths in GS_OPTIONS to respect it; they were still pointing at plain "ghostscript" instead of "ghostscript_". Fixed.

@apjanke apjanke closed this Jun 24, 2018

Octave.app automation moved this from High priority to Closed Jun 24, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 24, 2018

Contributor

(It's still a mystery to me why the error message is referencing Ghostscript 9.21, instead of the 9.23 which is currently bundled with Octave.app. That may be a moot point, though.)

Contributor

apjanke commented Jun 24, 2018

(It's still a mystery to me why the error message is referencing Ghostscript 9.21, instead of the 9.23 which is currently bundled with Octave.app. That may be a moot point, though.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment