[Bug 14702] New: corruption of write-protected files when changing permissions or deleting

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14702
Ubuntu | nautilus

           Summary: corruption of write-protected files when changing
                    permissions or deleting
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: nautilus
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: lesmond74 at hotmail.com
         QAContact: desktop-bugs at lists.ubuntu.com


For example, as user I use the rm -R command to delete a directory which
contains some write-protected codec files residing on a flash drive. The
terminal asks me to confirm this action for each write-protected file. But
instead of doing what I wanted the directory is turned into a corrupted,
unreadable one. As root, I am able to remove the directory but to my horror I
find that the entire contents of the flash drive are deleted with it! 

Needless to say, this is very annoying. And it is the more so because this kind
of thing has happened to me a number of times before. Another example is doing a
recursive change of permissions on a directory which contains write-protected
mp3 files. The entire directory becomes corrupted and unreadable.

This kind of corruption has happened regardless of the filesystem used - the
flash drive is vfat, my home partition has been both ext3 and reiserfs, and my
shared hard drive is vfat. 

I'm no expert but my guess is that it is a problem with nautilus, possibly
related to the bug filed earlier about crashes when trying to access the
'Properties' of audio files. Whatever it is, I think I'm going to have to look
into using another file manager.

Thanks for your time.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.