[Top][All Lists]

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

[Octave-bug-tracker] [bug #57528] imread always fails when Octave was st

From: Hartmut
Subject: [Octave-bug-tracker] [bug #57528] imread always fails when Octave was started with the "--traditional" option
Date: Fri, 3 Jan 2020 11:52:46 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0


                 Summary: imread always fails when Octave was started with the
"--traditional" option
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Fri 03 Jan 2020 04:52:44 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.1.0
        Operating System: Any



I have copied this presumably buggy behavior from the mailing list:

I can reproduce the behavior, here is how to do it:
* create an image file somewhere, e.g. "test.png" (it seems to happen with any
image file)
* start Octave from the commandline with the traditional option: "./octave
* (Set the Octave variable "filename" to the full filename of your image file
from above.)
* try to use imread to load this image file: "im = imread(filename);"

Here is the error message I then get using Octave 5.1.0 on linux:

>> im = imread(filename)
error: __magick_read__: unknown datatype for Region option
error: called from
    __imread__ at line 131 column 26
    imageIO at line 118 column 28
    imread at line 106 column 33

Using the imread command in the very same Octave installation, just without
the --traditional option, works fine.


Reply to this item at:


  Message sent via Savannah

reply via email to

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