Replacing saved read-only PDF file from within Firefox completely removes file.
Categories
(Firefox :: File Handling, defect)
Tracking
()
People
(Reporter: rosma, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0
Steps to reproduce:
- Open any previously saved PDF document in a Firefox browser window, where the Linux file permissions are owner/user = read-only, group and other = any.
- Save the document into the same location and with the same name.
- When the pop up box asking do you want to replace an existing files appears, click on replace.
- The file appears to be replaced.
Actual results:
- The file is actually removed from the selected location.
Expected results:
- The location should contain a file with the same name but a more recent modification date.
Note: This was only tried only on up to date Linux distributions Linux Mint Mate 21.3 and Manjaro Mate using arm64.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•2 years ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Gtk feels like the right place for this bug, since it's Linux? Trying with File Handling though.
Comment 3•1 year ago
|
||
Hello! Thank you for submitting this issue I have tried to reproduce the issue on my end but unfortunately I wasn't able to with firefox 137.0a1(2025-02-05) on Ubuntu 22.04
Could you please answer the following questions in order to further investigate this issue?
- Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
- Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
- Do you have any addons installed? If yes could you please list them?
Hello,
I am currently using Firefox 134.0.2 and the original problem I reported 10 months ago does not now exist in this version and I believe this has been the case for the last few months. It would appear the problem has been somehow corrected along the way. The problem also did not occur prior to version 123.0. Maybe this report can just be cancelled now, I would hope most people using Linux would be using an up to date version by now. Thanks for your attention in this matter.
Description
•