delete does not work on ntfs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eye of GNOME |
Expired
|
Medium
|
|||
| eog (Ubuntu) |
Incomplete
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: eog
(no apport - it failed to ever complete after over a minute, and btw, the cancel button on it doesn't work)
not a dupe of #42571, since that's supposedly fixed - despite reports to the contrary since the claimed fix...
also not a dupe of #192629, since that says "can't move to trash" and then offers delete.
eog in current 9.10 does neither. file on ntfs partition cannot be moved to trash in eog, and can't be deleted outright because eog is also ignoring the preferences specified in nautilus to allow real deletes, and has no such option of its own.
file is 777, and can be rm'd from a terminal. *nautilus* exhibits the (correct) behavior of 192629. eog is simply broken.
> "Error on deleting image <foo bar.tga>"
> "Couldn't access trash."
as an aside, eog also whines for confirmation of "move to TRASH", which is about as redundant and user-time-wasteful as you can get. how many prompts do you need for a RECOVERABLE action?
| Pedro Villavicencio (pedro) wrote | #1 |
| summary: |
- delete does not work + delete does not work on ntfs |
| Changed in eog (Ubuntu): | |
| importance: | Undecided → Low |
| Changed in eog: | |
| importance: | Undecided → Unknown |
| status: | New → Unknown |
| Pedro Villavicencio (pedro) wrote | #2 |
| Changed in eog (Ubuntu): | |
| status: | New → Triaged |
| Changed in eog: | |
| status: | Unknown → New |
| Changed in eog: | |
| status: | New → Confirmed |
| Changed in eog: | |
| importance: | Unknown → Medium |
| Changed in eog: | |
| status: | Confirmed → Incomplete |
| Changed in eog: | |
| status: | Incomplete → Expired |
| Sebastien Bacher (seb128) wrote | #3 |
| Changed in eog (Ubuntu): | |
| status: | Triaged → Incomplete |
| Janis Elmeris (janis-elmeris) wrote | #4 |
This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https:/