[Bug]: File may be written as read-only

typeling1578 commented 1 month ago

Pre-Submission Checklist

[X] I have checked the existing/closed issues to ensure this issue has not already been reported.
[X] I am using the latest version of Floorp Portable.
[X] I have tried disabling all browser extensions/add-ons to rule out interference from these.
[X] I have tried clearing the browser cache and cookies.
[X] I have checked with a new profile and the issue still occurs.
[X] I have checked that this problem is not occurring in the latest version of non-portable Floorp.
[X] I have checked that this problem is not occurring in the latest version of Firefox ESR.
[X] I have provided detailed step-by-step instructions on how to reproduce the issue.
[ ] I have included relevant screenshots or console outputs.
[ ] I will implement this by myself and send a pull request.

Bug Summary

see: https://github.com/Floorp-Projects/Floorp-Portable/issues/48#issuecomment-2451919288

Reproduction Steps

Download the update.
Restart the browser and attempt to apply the update.
Update is not applied.

Expected Behavior

Files are written with write permission, not read-only.

Actual Behavior

File may be written as read-only

Screenshots or Console outputs (recommended)

No response

Browser Version

11.20.0

Operating System (for example: Windows 10 Home, Debian 12, Fedora 40)

Windows 10

Additional Context

No response

typeling1578 commented 4 weeks ago

https://www.dell.com/support/kbdoc/000137238/understanding-file-and-folder-permissions-in-windows

By default, permissions are inherited from a root folder to the files and subfolders beneath it

Perhaps access permissions are not appropriate depending on where the file is located.

Permissions assigned directly to a particular file or folder (explicit permissions) take precedence over permissions inherited from a parent folder (inherited permissions).

In that case, setting appropriate permissions on the parent folder will work around this.

uugaabuugaa commented 4 days ago

Same issue for the latest version installation.

Perhaps access permissions are not appropriate depending on where the file is located.

This seems to be the case

In that case, setting appropriate permissions on the parent folder will work around this.

For some reason giving current user the permission to write/modify is not succeeding. It will show as permission given and after a refresh it goes back to read only mode. The culprit is probably windows and not Floorp. For now the temporary solution seems to be if I notice the notification I can run Floorp as admin on next startup and it will work. The problem is I have my windows notification turned off so it's hard to know when I need to run as admin. One way for me to notice particularly is when an update is downloaded but I keep using Floorp for a long time it starts to lag a lot.

Floorp-Projects / Floorp-Portable