It's great that Nautilus doesn't crash anymore, but the error message isn't very helpful. Nautilus probably just catches the return value from cp and shows the error message. I'm not confident cp is the best place to fix this, because then cp would need to know about other filesystem limits like vnode count, disk space etc, which would make cp unreasonably complex. Nautilus itself is probably a better place for this.
-- nautilus crashes when copying a 4G file on a vfat volume https://bugs.launchpad.net/bugs/70535 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
