Description of problem: Attempting to copy files larger than 64K from Fedora 26 to a Windows network share using Nautilus fails with "Invalid argument" error message. There is nothing in the debug messages to indicate a problem. gio copy reports the same error: $ gio copy large.data smb://server/data/temp gio: file:///home/user/large.data: Invalid argument Copying file smaller than 64K works however: $ gio copy small.data smb://server/data/temp $ Also, if one uses regular cp and copies a large file to a gvfs mounted share, operation works: $ cp large.data '/run/user/1000/gvfs/smb-share:server=server,share=data/temp' $ This worked with the same server on the same hardware running Fedora 25. It got broken with the Fedora 26 upgrade. The same problem occurs on all Fedora 26 boxes so far. Note that this problem has exactly the same symptoms as the bug #598620: https://bugzilla.redhat.com/show_bug.cgi?id=598620 Version-Release number of selected component (if applicable): samba-client-libs-4.6.5-0.fc26.x86_64 samba-common-libs-4.6.5-0.fc26.x86_64 samba-common-4.6.5-0.fc26.noarch samba-client-4.6.5-0.fc26.x86_64 libsmbclient-4.6.5-0.fc26.x86_64 nautilus-3.24.2.1-1.fc26.x86_64 gvfs-smb-1.32.1-2.fc26.x86_64 How reproducible: Always Steps to Reproduce: 1. Open Windows network share using Nautilus by browsing to smb://server/share/directory 2. Copy file larger than 64K to this remote share directory 3. "Invalid argument" message box pops up Actual results: Pop up message box (error) that says "Invalid argument" Expected results: File should be copied Additional info: Exactly the same problem has been reported in Fedora 13 as bugs #598620 and #615332. It was also in Gnome bugzilla as bug #588391. This might be a regression? https://bugzilla.redhat.com/show_bug.cgi?id=598620 https://bugzilla.redhat.com/show_bug.cgi?id=615332 https://bugzilla.gnome.org/show_bug.cgi?id=588391
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.