(09-28-2024, 12:09 PM)stevef Wrote: Thank you for trying.
Just to confirm, did you use the Lite Updates Tool to create a new directory or select a directory that already existed ?
I think I see your point.
Might there be a flaw in the script?
As I said, I used a partition that was already there and saved inside a directory on that partition (/video/Dell-T-1700/*).
I do this with almost all the files I save, then I move them where suitable. Having the files in /video/ spares me of taking care of the file sizes (there are over 300 GB available there).
I will check at the next update to see if I use the Lite Dialog if this goes as "root". As far as I remember, this is possible since the MkDir is issued from inside the script and it used "sudo apt install *". Since the persistence of the Root session is long enough to allow the updates, we can have an answer here.
The only way out in this case, is adding a ChOwner after the Dir creation and before saving the file. A delay before the save instruction might also be necessary to allow the system to update the directory structure and prevent the "File Missing" error.
Also, invoking "SaveAs" dialog as Root (this is the case as I see it), will generate a chain of Root processes, hence the Dir owner is Root and the file owner is also Root.
Best regards, Șerban.
PS: I checked the file attributes. The owner is "serban". The glitch might be somewhere else. Anyway, I'll check again with the Lite Updates. Maybe if the Dir owner is Root, the file will inherit the ownership.
"It's easy to die for an idea. It's way harder TO LIVE for your idea!"
Current Machine:
Dell Precision T1700, 16 GB RAM, SSD Kingston A400, 480 GB.
Laptop:
ASUS X200MA , Intel® Celeron® N2830, 2 GB RAM, SSD Kingston A400, 480 GB.
Current Machine:
Dell Precision T1700, 16 GB RAM, SSD Kingston A400, 480 GB.
Laptop:
ASUS X200MA , Intel® Celeron® N2830, 2 GB RAM, SSD Kingston A400, 480 GB.