Please note that on Linux, only the owner of a file and root are allowed to set
the timestamps of a file to a value different from the current time. So there
are three options :
1) disabling permissions checks (no uid, gid, dmask, fmask and umask options)
2) make the user appear as the owner
Also after a clean installation of ubuntu 10.4 I have the same problem.
However, when I remove the uid and gid tag of the fstab line it seems the
problem is solved.
And it seems that USB NTFS harddisks work fine.
--
New timestamp when copying to NTFS partition
I have enhanced the script so that the base directory is corrected as
well, and dangling symlinks are tolerated now.
** Attachment added: timesync.py
http://launchpadlibrarian.net/37349437/timesync.py
--
New timestamp when copying to NTFS partition
https://bugs.launchpad.net/bugs/314860
You
This bug only occurs with NTFS partitions, so I change the package
accordingly. The Ubuntu installers need to be fixed too, because the
fstab options are not complete (only gid is set). But if I understand
the issue correctly, a new version of ntfs-3g, 2009.11.14, would help
tremendously in
I have a multiboot system with three operating systems:
A) Windows XP SP3
B) Windows 7
C) Ubuntu 9.10
On every OS I have created a user. These three users have to be mapped
to one *identity* (me), so that the security features work flawlessly.
If, for example, I restrict read access to one
Maybe this is too much to ask for at the moment. Even the Windows
systems do not allow to connect the users of different Windows
installations to one identity. A SID change would be necessary to have
exactly the same SID on all Windows systems, but this can have security
implications in an Active
With root privileges the timestamp is preserved, this can be achieved by
using 'sudo':
sudo cp -a srcdir targetdir
sudo nautilus
I have written a Python script to correct the timestamps. The files need
not be copied again! I have appended the script.
** Attachment added: a Python script which
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
New timestamp when copying to NTFS partition
https://bugs.launchpad.net/bugs/314860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is not a Nautilus bug, since it also applies to the cp -a command,
with an error message: cp: preserving times for
`/mnt/Windisk/Me/Bug311567Demo.gnumeric': Operation not permitted. See
http://tuxera.com/forum/viewtopic.php?f=2t=2405 for details, especially
my reply of Sat Dec 05, 2009
I can add something to this.
This is happening in Jaunty as of today. If you rely on the fstab entry
as set up by the Jaunty installer for an internal partition (device
mountpoint ntfsdefaults,nls=utf8,umask=007,gid=460 1), you
get:
Nautilus file copy ext3 partition - NTFS partition
I followed the advice of Mr.Walton and let strace monitor the copying of a file
to a NTFS partition.
The log is attached.
I did the following:
I opened gnome-commander with /data/Antoon/Temp/Test on the left (this is a
folder on a NTFS partition) and
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
--
New timestamp when copying to NTFS partition
https://bugs.launchpad.net/bugs/314860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: nautilus (Ubuntu)
Sourcepackagename: None = nautilus
--
New timestamp when copying to NTFS partition
https://bugs.launchpad.net/bugs/314860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I re-linked this bug with Nautilus because this problem (also) shows up
in Nautilus.
When Nautilus uses another package to copy files, then maybe the problem
is caused by that other package, but as I'm just a simple Ubuntu desktop
user who is trying very hard to stop using XP, I have no idea what
If it's happening in GNOME commander it means that it's happening in
something below both file managers (which traverses from GLib down to
the kernel). Where the bug exists below is a good question, but it's not
one we can answer without a lot more information about how this change
occurs. Your
you get the bug in GNOME commander so that's clearly not a nautilus
issue
** Changed in: ubuntu
Sourcepackagename: nautilus = None
--
New timestamp when copying to NTFS partition
https://bugs.launchpad.net/bugs/314860
You received this bug notification because you are a member of Ubuntu
Bugs,
I get the bug in BOTH Nautilus and GNOME Commander. As Nautilus is the
native Ubuntu file manager, I filed the bug under Nautilus.
When you can tell me which package is causing the problem, please let me
know and I will change that.
--
New timestamp when copying to NTFS partition
** Attachment added: Screenshot of the problem
http://launchpadlibrarian.net/20993151/NTFS_copy_problem
** Attachment removed: Screenshot of the problem
http://launchpadlibrarian.net/20993151/NTFS_copy_problem
--
New timestamp when copying to NTFS partition
** Attachment added: Screenshot of the problem
http://launchpadlibrarian.net/20993181/NTFS_copy_problem.png
--
New timestamp when copying to NTFS partition
https://bugs.launchpad.net/bugs/314860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
19 matches
Mail list logo
