From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040301 Description of problem: file manager used with firewire partition is broken in RHEL-3 if I try to manage files by drag and drop on the firewire partition, the copy fails consistently. at the same time, file manager changes my firewire partition to read only after I mounted the partition as read/write. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.mount firewire drive 2.use file manager window to manage files.(copy or move) 3. Actual Results: after opening up file manager and cd'ing to firewire partition, the partition is changed to read only after I originally mounted it as read write. Expected Results: after opening file manager and cd'ing to firewire partition, I should be able to copy, move, remove files. Additional info:
I think the file manager you're using is nautilus.
This is very strange, nautilus never mounts anything as readonly. Nor does it remount things. Are you sure the file manager you used was nautilus?
I never mentioned that I was using nautilus. note my original bug. using file manager in KDE. after opening up file manager and cd'ing to firewire partition, the partition is changed to read only after I originally mounted it as read write.
Neither did you menation that you were using KDE.
i have tried to reproduce with your steps. It wokrs for me here. could you please send me the output of 'mount' before/after you opens file manager and cd'ing to firewire partition. Thank
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.