bugGNU Octave - Bugs: bug #65550, Odd error running octave-gui.exe...


bug #65550: Odd error running octave-gui.exe –gui

Submitter:  Vincent Fatica <vefatica>
Submitted:  Wed 03 Apr 2024 02:06:17 AM UTC
Category:  Other Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * 9.1.0 Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup

Fri 05 Apr 2024 03:59:46 PM UTC, comment #4: 

comment #2:

> Is the TCC shell using a different environment, like, e.g. %TEMP%, which might not be available or user accessible?

TCC uses TEMP=C:\Users\vefatica\AppData\Local\Temp (the default)

Vincent Fatica <vefatica>
Wed 03 Apr 2024 08:32:16 AM UTC, comment #3: 

@OP: Are you @vefatica on Discourse? If so, please try to avoid double-posting. Or at least, leave a reference if you asked the same question in multiple places.

In any case, this might be related:

Assuming that the Discourse thread is about the same issue, I'm closing this report as invalid.
Some environment variables need to be set correctly on Windows before running `octave-gui` (or `octave-cli` or `octave`). The launcher does that for users.

Markus Mützel <mmuetzel>
Group administrator
Wed 03 Apr 2024 04:44:36 AM UTC, comment #2: 

Is the TCC shell using a different environment, like, e.g. %TEMP%, which might not be available or user accessible?

Torsten Lilge <ttl>
Group Member
Wed 03 Apr 2024 03:37:15 AM UTC, comment #1: 

I failed to mention two things.

After Octave starts poorly (having produced the previously mentioned message box and with its help pane empty), the next time I start it, this


has been changed to this


in %USERPROFILE%\AppData\Roaming\octave\octave-gui.ini.

And although Octave doesn't crash visually, the experiment causes Windows to create, for example,


Vincent Fatica <vefatica>
Wed 03 Apr 2024 02:06:17 AM UTC, original submission:  

Octave 9.1.0 on Windows 10. Here’s the text of an error message box from Octave.

Could not copy help collection to temporary
file. Search capabilities may be affected.
Cannot open collection file: \scratch\build\mxe-octave-w64\usr\x86_64-w64-mingw32\share\octave\9.1.0\doc\octave_interpreter.qhc

That message only appears when I issue this command in the TCC (JPSoft) shell.

    start D:\octave\mingw64\bin\octave-gui.exe --gui

The error does not occur if I issue the same command in another Windows shell (CMD, Powershell, PWSH) or if I use it (without “start”) in Window’s Start\Run dialog.

Two observations: “scratch” does not seem appropriate for Windows. Perhaps the value of %TEMP% belongs there. And Octave does not try to access that file in that location when it starts without error (so says SysInternals’s ProcessMonitor).

And a question: What would trigger that error? If the TCC shell is (partially) at fault, an answer to that question might help bring about a fix.

Vincent Fatica <vefatica>


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

Attach Files:

No files currently attached


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 ttl (Posted a comment)
  • -email is unavailable- added by vefatica (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 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-04-03 mmuetzel StatusNone Invalid / Not an Octave Bug
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code