-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling write protected media #3446
Comments
Are you using copy - perhaps in nemo or are you using dd to write to a device? |
No, I used dd (in terminal) to write some image files to floppy disk, just I mentioned that I ran in the same issue when the floppy was set to write protect even with dd. The nemo symptom exist regardless of this. |
With the nemo problem, are you using a hardware switch on the device for the write protection? I would guess that low-end devices don't inform the OS that they are in a read-only state, so nemo waits for an attempted write operation to complete. Similar considerations would apply to dd. |
The USB floppy drive is a low-end hardware of course, but the SD-card drive in a HP laptop maybe not. But anyway, nemo displays a "write protected media" message, as wrote, so the read-only state is detected. After this message the copy process is not stopped... |
Distribution
Mint 22 (but 21.x too)
Package version
6.2.8 (but olders too)
Frequency
Always
Bug description
Write protected SD card, or write protected floppy (I Have an USB floppy drive also).
Try to copy something to a write protected media. An error message says the media is write protected - OK.
But the copy process still working, and not stopping. Anytime after, try to shut down, or restart the system, got a warning message: copy process running, do you want to kill it or cancel the shut down/restart....
Steps to reproduce
For first sorry, I am using a localized Mint, so I don't know the exact messages in English.
Expected behavior
kill the copy process when write protected media detected.
Additional information
There is also some kind a semantic bug in general I think, if you try to write images with dd to a protected media, the process is going on even the write protected state is detected, you must unmount the drive to stop it.
The text was updated successfully, but these errors were encountered: