After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 312768 - Error "Not on the same file system" creating new document.
Error "Not on the same file system" creating new document.
Status: RESOLVED DUPLICATE of bug 309592
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.11.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-08-06 16:55 UTC by Robert Ford
Modified: 2005-08-06 17:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Robert Ford 2005-08-06 16:55:08 UTC
Please describe the problem:
I have been building the snapshot/developmnet packages from the garnmone prodject.
Since the release of the 2.11.90 branch, nautilus's ability to create a new
"Empty File" has been broken. The right-click option 'Create Document/Empty
File' fails reporting this "Error creating new document. Error "Not on the same
file system" creating new document.". This is shared in both nautilus versions
2.11.4 and 2.11.90, but when reverting back to version 2.11.3 the error
disappears and the function works again.

Steps to reproduce:
1. build and install nautilus-2.11.4/90 (or the garnome development branch)
2. right-click, 'Create Document/Empty File"
3. 


Actual results:
Does not create a new file, reports error

Expected results:
this "Error creating new document. Error "Not on the same file system."

Does this happen every time?
yes, every time

Other information:
Im using Arch Linux (x86) Current and the Garnome development build system
Comment 1 Sebastien Bacher 2005-08-06 17:15:15 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of 309592 ***