octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #56193] print -tight only warns, does not erro


From: avlas
Subject: [Octave-bug-tracker] [bug #56193] print -tight only warns, does not error when ghostscript binary not found
Date: Mon, 22 Apr 2019 12:55:03 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/73.0.3683.86 Chrome/73.0.3683.86 Safari/537.36

URL:
  <https://savannah.gnu.org/bugs/?56193>

                 Summary: print -tight only warns, does not error when
ghostscript binary not found
                 Project: GNU Octave
            Submitted by: kupiqu
            Submitted on: Mon 22 Apr 2019 04:55:01 PM UTC
                Category: Plotting
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: Print
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.1.0
        Operating System: Any

    _______________________________________________________

Details:


I ran the following code in Octave 5.1 (flatpak) and got the following error.

  > plot(1:10)
  > print('-depsc','figname.eps','-tight')
  warning: your version of GraphicsMagick limits images to 8 
  bits per pixel
  warning: print.m: Ghostscript binary is not available.  Only 
  eps output is possible
  warning: called from
      __print_parse_opts__ at line 487 column 7
      print at line 416 column 8
  sh: -h: command not found
  free(): double free detected in tcache 2
  sh lĂ­nia 1:    27 Aborted                /app/bin/epstool -- 
  quiet --copy --bbox /tmp/oct-6PiVJ2.eps 'figname.eps'

This error even occurs if I use a try-catch instruction where the catch
instruction omits the -tight option

I guess the expected behavior should be to warn about the issue, omit the
-tight option and proceed, is this right?

[ This is the issue I filled against flatpak's Octave build
https://github.com/flathub/org.octave.Octave/issues/59 ]




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56193>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]