bugGNU Octave - Bugs: bug #64625, Not working some function such as...

 
 

bug #64625: Not working some function such as plot(), figure() and etc.

Submitter:  None
Submitted:  Wed 06 Sep 2023 12:40:20 PM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  Need Info Assigned to:  None
Originator Name:  Originator Email:  -email is unavailable-
Open/Closed:  * Open Release:  * 8.3.0
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 23 Jan 2024 03:50:18 PM UTC, comment #12: 

Octave 9 is now on the stable branch for which nightly builds can be downloaded from here:
https://buildbot.octave.space/#/download

Could you please test if paths with non-ASCII characters are working better for you with a nightly build?

Markus Mützel <mmuetzel>
Group administrator
Sun 17 Sep 2023 12:48:25 PM UTC, comment #11: 

Thank you for testing.

There have been some changes to how the load path is handled on Windows that will be part of Octave 9. It would be nice to see if those changes made any difference for you.

However, testing that is a little bit more complicated. You'd need to be a bit familiar with working with a terminal.

Shy of compiling Octave from scratch on Windows or with MXE Octave, you could test with the build artifacts from the GitHub CI. See:
https://wiki.octave.org/Continuous_Build#GitHub_build_artifacts

Differing from those instructions, you'd need to unzip the build artifact to a folder with non-ASCII characters (such as d:\Programosė). (But still install MSYS2 to its default location.)

Markus Mützel <mmuetzel>
Group administrator
Sun 17 Sep 2023 08:05:28 AM UTC, comment #10: 

A path with a space (for example "d:\Progra mos\octave-8.3.0-w64\") does not affect how Octave works. But the paths

"d:\Programosė\octave-8.3.0-w64\"

etc. (any non-Latin letter in the path) makes Octave not fully functional. Output after launch

warning: load_path: D:\Programosė\octave-8.3.0-w64\mingw64\lib\octave\8.3.0\site\oct\x86_64-w64-mingw32: No such file or directory
warning: load_path: D:\Programosė\octave-8.3.0-w64\mingw64\lib\octave\site\oct\api-v58\x86_64-w64-mingw32: No such file or directory
...
warning: load_path: D:\Programosė\octave-8.3.0-w64\mingw64\share\octave\8.3.0\data: No such file or directory

Total 270 directories.

The figure command works (but outputs 270 warnings described above). The command plot([1,2,3]) does not work. Output below:

warning: load_path: D:\Programosė\octave-8.3.0-w64\mingw64\lib\octave\8.3.0\site\oct\x86_64-w64-mingw32: No such file or directory
warning: load_path: D:\Programosė\octave-8.3.0-w64\mingw64\lib\octave\site\oct\api-v58\x86_64-w64-mingw32: No such file or directory
...
warning: load_path: D:\Programosė\octave-8.3.0-w64\mingw64\share\octave\8.3.0\data: No such file or directory
warning: ft_manager: unable to load font: D:\Programosė\octave-8.3.0-w64\mingw64\share\octave\8.3.0\fonts\FreeSans.otf
warning: called from
    axes at line 107 column 8
    newplot at line 161 column 10
    plot at line 234 column 9

warning: ft_text_renderer: unable to load appropriate font
warning: called from
    axes at line 107 column 8
    newplot at line 161 column 10
    plot at line 234 column 9

warning: ft_manager: unable to load font: D:\Programosė\octave-8.3.0-w64\mingw64\share\octave\8.3.0\fonts\FreeSans.otf
warning: called from
    axes at line 107 column 8
    newplot at line 161 column 10
    plot at line 234 column 9

warning: ft_text_renderer: unable to load appropriate font
warning: called from
    axes at line 107 column 8
    newplot at line 161 column 10
    plot at line 234 column 9

warning: ft_manager: unable to load font: D:\Programosė\octave-8.3.0-w64\mingw64\share\octave\8.3.0\fonts\FreeSans.otf
warning: called from
    axes at line 107 column 8
    newplot at line 161 column 10
    plot at line 234 column 9

warning: ft_text_renderer: unable to load appropriate font
warning: called from
    axes at line 107 column 8
    newplot at line 161 column 10
    plot at line 234 column 9

error: _go_axes_: ft_text_renderer: invalid bounding box, cannot render, unable to create graphics handle
error: called from
    axes at line 107 column 8
    newplot at line 161 column 10
    plot at line 234 column 9

Anonymous
Thu 14 Sep 2023 11:07:14 AM UTC, comment #9: 

Thank you.

Could you please check if it is the letter 'ė' or 'į' that caused the issue? I.e., could you add either of them to the path where Octave is installed and check if it still works? E.g., d:\Programosė\octave-8.3.0-w64\ and d:\Programosį\octave-8.3.0-w64\.

If both of these work, could you please check if adding a space in the path makes it fail for you? E.g. "d:\Program os\octave-8.3.0-w64\".

Markus Mützel <mmuetzel>
Group administrator
Thu 14 Sep 2023 09:38:40 AM UTC, comment #8: 


>> _locale_charset_

ans = CP1257

Anonymous
Mon 11 Sep 2023 01:33:55 PM UTC, comment #7: 

It shouldn't have failed as miserably as you described just because of the space in the file path.

Maybe, it has something to do with non-ASCII characters.

What does `__locale_charset__` return for you in Octave?

Markus Mützel <mmuetzel>
Group administrator
Mon 11 Sep 2023 12:44:04 PM UTC, comment #6: 

Ok, glad to hear it works now. Closing report.

Nicholas Jankowski <nrjank>
Group Member
Mon 11 Sep 2023 12:42:14 PM UTC, comment #5: 

ok - yes - It depends on whether short 8.3 names work on a drive for if spaces in the octave install paths will work.

John Donoghue <lostbard>
Group Member
Mon 11 Sep 2023 09:57:53 AM UTC, comment #4: 

The extraction path was:
d:\Programinė įrasnga\octave-8.3.0-w64\

After changing path to (removed non-Latin letters and space)
d:\Programos\octave-8.3.0-w64\
everything works.

THANK YOU.

Anonymous
Fri 08 Sep 2023 01:25:59 PM UTC, comment #3: 

What path did you  extract the files to ?

John Donoghue <lostbard>
Group Member
Fri 08 Sep 2023 01:14:27 PM UTC, comment #2: 


> Your comment seems to missing the output.

No. "Path" list is empty.


> How did you install octave, how are you starting octave?

I did not install Octave. I unfolded from https://ftpmirror.gnu.org/octave/windows/octave-8.3.0-w64.7z.
I used "%Octave%octave.vbs" and "%Octave%octave-launch.exe" to launch Octave.

Anonymous
Wed 06 Sep 2023 01:20:31 PM UTC, comment #1: 

Your comment seems to missing the output.

How did you install octave, how are you starting octave?

John Donoghue <lostbard>
Group Member
Wed 06 Sep 2023 12:40:20 PM UTC, original submission:  

Warrning windows (see attached file) are displayed when starting Octave.
In Octave enviroment functions such as figure(), plot() and etc. are undefined.
Function "path" output is:

Octave's search path contains the following directories:
.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #55120:  cannot_open_collection_file.png added by None (13KiB - image/png)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by nrjank (Posted a comment)
  • -email is unavailable- added by lostbard (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-09-11 mmuetzel StatusFixed Need Info
        Open/ClosedClosed Open
    2023-09-11 nrjank StatusNeed Info Fixed
        Open/ClosedOpen Closed
    2023-09-07 lostbard StatusNone Need Info
    2023-09-06 None Attached File- Added cannot_open_collection_file.png, #55120

    Back to the top

    Powered by Savane 3.13-b921.
    Corresponding source code