Handling write protected media
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.6k
- Forks
- 368
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 2
Description
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.
- switch an SD card or floppy to write protected state.
- Put in the drive
- Nemo window appears
- try to drag some files here or try to copy in another way to media.
- Write protected warning message appears
- copy progress bar still working
- close the copy progress window with progress bar
- wait a bit, or more.
- try to restart or shut down the system
- See the warning about copy progress....
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the report. Reproduce the write-protected SD card or floppy copy in Nemo, then trace the copy operation and its shutdown-in-progress handling; done means the operation stops after the write-protection error and no copy warning remains on shutdown or restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100