Comment 34 for bug 70535
Revision history for this message
| Erik Cederstrand (erik-cederstrand) wrote | #34 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
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.