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 531743 - Browsing a NCPMOUNT returns 0 bytes free
Browsing a NCPMOUNT returns 0 bytes free
Status: RESOLVED DUPLICATE of bug 532965
Product: nautilus
Classification: Core
Component: general
2.22.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on: 532965
Blocks:
 
 
Reported: 2008-05-06 14:04 UTC by Bolderbast
Modified: 2008-05-16 15:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Bolderbast 2008-05-06 14:04:39 UTC 
Please describe the problem:
When mounting a Novell server using NCPMount, Nautilus reports 0 bytes free. So, no data can be copied to the Novell server.

All other operations (such as deleting, renaming, etc.) work fine. Also, copying files to the mounted Novell server from a terminal works fine.

Steps to reproduce:
1. Mount a Novell Fileserver using NCPMount
2. Browse the filesystem from nautilus
3. Try to copy a file to the Novell Fileserver using nautilus


Actual results:
Error occurs that no free space is available

Expected results:
a succesful copy operation :-)

Does this happen every time?
Yes

Other information:
NCPFS version 2.2.6-4ubuntu3 (running Ubuntu Hardy)
Comment 1 A. Walton 2008-05-06 14:21:59 UTC 
This was reported here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/224760

... which suggests that this is probably an NCPFS bug, since it's telling us that we have no free space on the device. I'd agree; if the filesystem says there's no free space, Nautilus should honor that.
Comment 2 A. Walton 2008-05-13 14:55:03 UTC 
Updating dependencies.
Comment 3 Christian Neumair 2008-05-16 15:46:46 UTC 
This is actually a duplicate of bug 532965. The issue is entirely GIO-related, and we have a proposed and working patch.

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