cherrytree in Kali Linux cannot write to folder/file

[fpmw]

All,

I just updated my Kali (Linux vkali 6.11.2-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.11.2-1kali1 (2024-10-15) x86_64 GNU/Linux) in which cherrytree was automatically update to 1.2.0.

Issue: Cannot write to the same file after an update to the cherrytree file.

Some details:
I cannot write to the same file (after changes were applied) after opening it.

1. save-as (shift-ctrl-S), 'single XML file (.ctd)'
2. Hitting save, i.e. no change of the filename.
   --> Wanring: "The file/folder is use cannot be overwritte! Please use a different name or location"

Note that the file is writeable to me. The folder (e.g. Destop) is writeable to me since I can cp/mv files from the CLI to the location where the .ctd is located.
Note2: My way of working has not changed, prior to version 1.20 there was no problem at all. It clearly seems to be related to version 1.20 in Kali.

Any thoughts?

Regards,
Frank Wetzels

[gitvectors]

+1
It is annoying, I agree. My workaround is to keep two copies in my folder.
MyCT.ctd
MyCT-bak.ctd
And just save into one or other. I can see file properties in my File Manager (Krusader).

[giuspen]

I'm not understanding... why would you Ctrl+Shift+S (File--Save As) selecting the same filepath?
You should Ctrl+S instead (File--Save).

[gitvectors]

Because .. in menu .. not by shortcuts
Save .. is not clickable
Save As .. is clickable

But using Ctrl+S might do the job as suggested. There is simply no tactile feedback.

[giuspen]

Save becomes indeed not clickable after you save / before you change something, but it becomes clickable when you edit something.
If you edit something and Save does not become clickable, then that would certainly be a bug, but you have to help me reproduce it.
Also ensure that you have the autosave not enabled in the preferences because that saves automatically for you so that would certainly cause the save to be disable as it likely did already save.

[gitvectors]

I will try to reproduce when I have time. Personally for important notes I prefer to have the auto backup hidden files plus saving to a twin file (different name), for now. The least that might be added is a popup message saying "file saved" to give user feedback on clicking Save that some action was taken. Notes are too important to guess if they have been backed up, so I add double backup security in my workflow

[fpmw]

Thanks all for your replies. It seems that - indeed - ctrl-S does the job. Easy fix for now and I have to keep copies to prevent things get lost AND I have to re-program my fingers to hit different keys :-)

Regards,
Frank