bugGNU Octave - Bugs: bug #60933, Unable to save scripts (new or...

 
 

bug #60933: Unable to save scripts (new or after edit) in the 32-bit version

Submitted by:  None
Submitted on:  Sun 18 Jul 2021 06:58:29 AM UTC  
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Need Info Assigned to:  None
Originator Name:  Rio Originator Email:  -email is unavailable-
Open/Closed:  Open Release:  6.3.0
Operating System:  Microsoft Windows

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Sun 25 Jul 2021 07:44:39 PM UTC, comment #24: 

Is this a typo? Or does that really resolve to a different folder?

Markus Mützel <mmuetzel>
Project Member
Sun 25 Jul 2021 07:04:23 PM UTC, comment #23: 

ans = C:\Users\Founders\Documents

Anonymous
Sun 25 Jul 2021 06:57:42 PM UTC, comment #22: 

Is "C:\Users\Founder1\documents" a symlink?
What does the following command return in Octave?

canonicalize_file_name('C:\Users\Founder1\documents')

Markus Mützel <mmuetzel>
Project Member
Sun 25 Jul 2021 05:54:21 PM UTC, comment #21: 

chkdsk command detected no problems.

I created a directory C:\Users\Founder1\test, and the files can be edited and saved as expected.

I tried a file in the directory C:\Users\Founder1\documents, but the file could not be saved. The following popup msg is given by the Octave Editor if I tried to save a new file... "Could not open file C:/Users/Founder1/Documents/test.m for write: The system cannot find the file specified.."

-----------
Note: I'm abandoning working off anything from the Documents directory and downstream from that. Octave seems to work just fine from the "test" directory.

Anonymous
Sun 25 Jul 2021 05:20:47 PM UTC, comment #20: 

That makes more sense.

It might still be good having Windows check your file system with `chkdsk C: /f`.

Like I've written earlier, I can't reproduce with Octave 32bit here. It doesn't matter if I check with a file inside the user folder or somewhere else on the disc. Octave always picks up the changed version.

Could you attach a file that doesn't update for you?

Markus Mützel <mmuetzel>
Project Member
Sun 25 Jul 2021 03:47:42 PM UTC, comment #19: 

I apologize... made a mistake in the previous post.
Both "getenv('USERPROFILE')" and canonicalize_file_name gave the same answers as:
ans = C:\Users\Founder1

The longer one was actually from the "pwd" command.
ans = C:\Users\Founder1\documents\projects\ex5

Running canonicalize_file_name(canonicalize_file_name(getenv('USERPROFILE'))) produced:
ans = C:\Users\Founder1

Running system('dir /AL C:\Users') yielded:
 Volume in drive C is Acer
 Volume Serial Number is B22D-D38C

 Directory of C:\Users
07/12/2019 02:20PM </SYMLINKD>   All Users    [C:\ProgramData]
07/12/2019 02:20PM <JUNCTION>    Default User [C:\Users\Default]
    0 File(s)                     0 bytes
    2 Dir(s)          9,989,669,672 btyes free
ans = 0

Anonymous
Sun 25 Jul 2021 03:18:41 PM UTC, comment #18: 

Hmm... That is interesting.

`canonicalize_file_name` should not return a folder below the folder it got as input.
It should "resolve" symlinks in the path. But I would have thought that having a symlinked folder point to a folder below itself would result in strange recursive behavior.

What does the following commands return for you in Octave?

canonicalize_file_name(canonicalize_file_name(getenv('USERPROFILE')))
system('dir /AL C:\Users')

You might want to check your filesystem by running `chkdsk C: /f` from a command prompt with elevated rights.

Markus Mützel <mmuetzel>
Project Member
Sun 25 Jul 2021 02:26:16 PM UTC, comment #17: 

octave:1> getenv('USERPROFILE')
ans = C:\Users\Founder1

octave:2> canonicalize_file_name(getenv('USERPROFILE'))
ans = C:\Users\Founder1\documents\projects\ex5

Anonymous
Sun 25 Jul 2021 01:55:40 PM UTC, comment #16: 

I understand you don't want to share your user name for some reason. But it is becoming more and more probable that this information will help pinpointing the cause of the issues you are seeing.

Or is the username actually "<name>" (including the chevrons)?

Could you please show what you see for the following in Octave?

getenv('USERPROFILE')
canonicalize_file_name(getenv('USERPROFILE'))

Markus Mützel <mmuetzel>
Project Member
Sat 24 Jul 2021 02:24:55 AM UTC, comment #15: 

Don't know if this helps but it seems relevant. I just noticed that even the complete DOS filepath is alphanumeric only... i.e. C:\Users\name\Documents\Projects, Window File Explorer has another representation for C:\Users\name as an account name (i.e. Joe P). AND in this case, it does have a blank space in there.

The C:\Users\name is actually represented by Joe P. You only see this with File Explorer. Octave GUI only has the DOS filepath.

Anonymous
Sat 24 Jul 2021 02:08:55 AM UTC, comment #14: 

Only English alphabets and number digits are in the file path, directory name, or file name...

Anonymous
Fri 23 Jul 2021 07:23:44 PM UTC, comment #13: 

Does "<name>" contain any non-ASCII characters or whitespace characters?

Markus Mützel <mmuetzel>
Project Member
Fri 23 Jul 2021 07:16:54 PM UTC, comment #12: 

That's very interesting... The problem seems to happen only in subfolders after C:/Users/<name>. For example, won't work if in:
C:/Users/<name>/Documents
or
C:/Users/<name>/Documents/projects
etc.

No problems in the parents like C: or C:/Users folders.

Anonymous
Fri 23 Jul 2021 04:57:17 PM UTC, comment #11: 

Is the problem limited to one folder or one partition?

Markus Mützel <mmuetzel>
Project Member
Fri 23 Jul 2021 03:35:30 PM UTC, comment #10: 

The problem is not isolated to just one particular file. Trying to create and save a new file also runs into the problem.

Anonymous
Fri 23 Jul 2021 01:12:43 PM UTC, comment #9: 

Does the error occur with any file or only with that particular file?

Markus Mützel <mmuetzel>
Project Member
Fri 23 Jul 2021 01:10:32 PM UTC, comment #8: 

I was working on an existing file from the local hard drive to which changes would not be saved. But the user wouldn't know it until the file is reloaded or if the script shown in the Editor is run (i.e. new Octave codes would not be executed).

Anonymous
Fri 23 Jul 2021 12:14:43 PM UTC, comment #7: 

That looks ok to me.

Where is the file located? Is it on a local disc, on a thump drive or a network share? Do you know the file system?

Markus Mützel <mmuetzel>
Project Member
Fri 23 Jul 2021 08:37:05 AM UTC, comment #6: 

Thanks so much for following up on this, Markus. Answers to your questions:

I'm running Octave 32-bit on Window 10 Home 32-bit on an older laptop QuadCore with only 2GB Memory.

_mfile_encoding_ ==> ans = system
_locale_charset_ ==> CP1252

Anonymous
Fri 23 Jul 2021 07:32:25 AM UTC, comment #5: 

I can't reproduce with Octave 6.3.0 32bit installed on Windows 10 64bit.

Which OS and OS version are you using?

What do the following commands return for you?

__mfile_encoding__
__locale_charset__

Markus Mützel <mmuetzel>
Project Member
Sun 18 Jul 2021 08:02:09 AM UTC, comment #4: 

Just alphanumerals in the filename and directory names.

Anonymous
Sun 18 Jul 2021 07:59:04 AM UTC, comment #3: 

comment #2:

> Thanks for the report. Does the path of the file include special characters?

Anonymous
Sun 18 Jul 2021 07:23:46 AM UTC, comment #2: 

Thanks for the report. Does the path of the file include special characters?

Torsten Lilge <ttl>
Project Member
Sun 18 Jul 2021 07:02:05 AM UTC, comment #1: 

Not sure if this is a bug or simply an isolated problem with my older laptop. I encountered this bug when forced to use Octave on an older computer running a 32-bit version. I didn't have this problem on my 64-bit laptop before it failed and became unusable.

Anonymous
Sun 18 Jul 2021 06:58:29 AM UTC, original submission:  

Scripts can be edited on the Octave editor but the changes are not saved. The user would be mistakenly believe that new changes are saved after clicking the SAVE FILE icon. If the "saved" file is reloaded into the editor, changes are lost. There are no error messages indicating the SAVE didn't work.

No error message either if opening a completely new file and then saving it. The new file, in fact, is not even saved.

An error message, however, would be displayed if trying to save an existing file under a different name. In this case, there is pop-up message from the Octave Editor saying:
Could not open file <PATH/FILENAME> for write:
The system cannot find the file specified..

Anonymous

 

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

Attach Files:
   
   
Comment:
   

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 None (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-07-23 mmuetzel StatusNone => Need Info

    Back to the top


    Powered by Savane 3.6