** Package changed: ntfs-3g (Ubuntu) = rhythmbox (Ubuntu)
--
Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?;
question mark) when ripping to NTFS volumes
https://bugs.launchpad.net/bugs/318625
You received this bug notification because you are a member of Ubuntu
Could someone modify the ntfs-3g package so that the hack is directly
implemented when the fstab is written?
Sadly we can not do anything in NTFS-3G because, as it was earlier
explained and patches submitted, this is not an NTFS-3G bug but a Gnome
one. When it's possible we always workaround
why would users delete files exactly? when there is no trash
available nautilus display a dialog explaining that and ask for
confirmation to the users
By accident. Childen. Elder people. Users who think they can recover
from the Trash if they still change their mind. Software bugs. Hung
ntfs-config
--
Copyng a file to a NTFS drive change the date and the time of the file
https://bugs.launchpad.net/bugs/157396
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for nautilus in ubuntu.
--
desktop-bugs mailing list
Ntfs-3g updates the times the same way as other file systems.
ext3:
# stat test1
File: `test1'
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 805h/2053d Inode: 2275396 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1004/ szaka) Gid: ( 100/
Try to extract some or all the files of a compressed file (.zip, .tar, ...):
in the compressed file You see
the date and the time of the file, and if You extract in a NTFS drive, at
this moment You see the date of
the copy. Expected is the original date (and time), and this is OK if you
Just to clarify: do you want the file change timestamp to be the start
time of the copy, not the end time of the copy? If the driver doesn't do
things this way then that will be fixed (one unrelated ctime update
problem is already fixed).
If you're interested in the creation time then
We've check it out now and NTFS-3G indeed doesn't update the creation
time correctly sometimes (originally you commented the modification
time).
Thank you for the bug report, this is planned to be fixed in the next
NTFS-3G release.
Szaka
==
NTFS-3G Lead Developer: http://ntfs-3g.org
When you /bin/cp a file then it gets new timestamps by default whatever
is the file system. Nautilus maybe redefines this behaviour but not
consistently.
** Changed in: nautilus (Ubuntu)
Sourcepackagename: ntfs-3g = nautilus
--
Copyng a file to a NTFS drive change the date and the time of the
Your setup is broken. See http://ntfs-3g.org/support.html#locale
--
Songs with accented letters in title are not ripped
https://bugs.launchpad.net/bugs/137359
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
ntfs-3g 1.826 supports mount in this case.
--
Usability: 'Cannot mount volume' details are not selectable
https://bugs.launchpad.net/bugs/132279
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
That's interesting because quite many NTFS-3G users complain to us
developers about Nautilus moving deleted files to the .Trash-username'
directory in the root of the NTFS volume they are not aware of:
http://www.ntfs-3g.org/support.html#diskspace
Given that many people are confused in either
Ntfs-3g problem 1 and 2 are fixed in newer releases. The other problems
are unrelated to ntfs-3g and Ubuntu nautilus problems are indeed
reported by many people to ntfs-3g upstream. Please note that I/O errors
are perfectly valid if there are storage problems, e.g. bad sectors,
detached devices.
From ntfs-3g upstream: the I/O problems are related to Seagate devices
and are file system independent. The reason and a potential workaround
is discussed here:
http://www.nslu2-linux.org/wiki/FAQ/DealWithAutoSpinDownOnSeagateFreeAgent
The problem is in the Linux kernel (USB driver, etc).
--
I'm not sure the fix is correct, enough as I explained above. Or does it
work with the fuseblk, fuseblk.ntfs-3g and fuse.ntfs-3g file system
types too?
--
Gnome Trash doesn't show deleted files on ntfs-3g partitions
https://bugs.launchpad.net/bugs/106621
You received this bug notification
From NTFS-3G upstream: the issue is not NTFS-3G but FUSE specific. I explained
it at
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/106621/comments/12
This should be enough for Gnome developers to make the changes to support all
FUSE
file systems on all kernels. Thanks.
--
Gnome
As https://bugs.launchpad.net/ubuntu/+source/gnome-
vfs2/+bug/106621/comments/12 explained, kernel 2.6.20 introduced fuseblk
and that 's what for example ntfs-3g uses mounting all internal and
external disks. Afaik, Ubuntu 7.04 uses kernel 2.6.20, so the problem is
not fixed.
--
Gnome Trash
Depending on the kernel version and other issues, the file system type
(fstype) can be: fuse, fuseblk, fuse.userfs and fuseblk.userfs,
where userfs is FUSE file system type, e.g. ntfs-3g.
The userfs sub part of the fstype should stay in the future but it's
not available yet in stable Linux
It's very simple to test, if one is familiar a bit with the command line. No
need for existing NTFS or Windows:
http://ntfs-3g.org/quality.html#howtotest
--
Gnome Trash doesn't show deleted files on ntfs-3g partitions
https://bugs.launchpad.net/bugs/106621
You received this bug notification
19 matches
Mail list logo
