You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, Two of our staff have upgraded from 4.0.2 to the new version of 4.1.2, with the same results. After installation everything seems fine, but after the file is transferred to the server via SFTP, the beach ball appears and Cyberduck becomes unresponsive forcing a manual force quit. Upon relaunch of the program everything seem fine until you transfer a file again and the same occurrence happens again. Our staff members, who upgrade, have trashed the new version and have gone back to using 4.0.2, so I have no log drawer information.
Here is some information about our machines:
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 4 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.25f4
Please let me know if you need additional information to help track down this issues.
The text was updated successfully, but these errors were encountered:
Duplicate for #6183. As a workaround, disable the option Transfers → Remove when transfer completes in Preferences or upgrade to the latest snapshot build available.
Hello, Two of our staff have upgraded from 4.0.2 to the new version of 4.1.2, with the same results. After installation everything seems fine, but after the file is transferred to the server via SFTP, the beach ball appears and Cyberduck becomes unresponsive forcing a manual force quit. Upon relaunch of the program everything seem fine until you transfer a file again and the same occurrence happens again. Our staff members, who upgrade, have trashed the new version and have gone back to using 4.0.2, so I have no log drawer information.
Here is some information about our machines:
Please let me know if you need additional information to help track down this issues.
The text was updated successfully, but these errors were encountered: