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
For some weeks (and also with some previous version(s?) of Cyberduck):
1-Cyberduck windows (remote computer directory and transfer window) "almost freeze" at random WHEN A TRANSFER is under work: impossible to select another item WITHIN the cyberduck windows, and sometimes in Finder windows, but the windows can still be moved, and the file name of the files under transfer are updated in the cyberduck transfer window. The problem is solved, again at random, when I can select something elsewhere outside of cyberduyck. In some cases (undetermined; all cases?), it is impossible to switch to any other application while transfer is under progress… until a success obtained at random.
In some rare cases I have been obliged to kill Cyberduck.
REMARK: this problem appears with 2 different computers operated under the same system version OS X 10.11.6. It is thus NOT due to a corrupted system to my point of view.
Two other tickets follow…
The text was updated successfully, but these errors were encountered:
For some weeks (and also with some previous version(s?) of Cyberduck):
1-Cyberduck windows (remote computer directory and transfer window) "almost freeze" at random WHEN A TRANSFER is under work: impossible to select another item WITHIN the cyberduck windows, and sometimes in Finder windows, but the windows can still be moved, and the file name of the files under transfer are updated in the cyberduck transfer window. The problem is solved, again at random, when I can select something elsewhere outside of cyberduyck. In some cases (undetermined; all cases?), it is impossible to switch to any other application while transfer is under progress… until a success obtained at random.
In some rare cases I have been obliged to kill Cyberduck.
REMARK: this problem appears with 2 different computers operated under the same system version OS X 10.11.6. It is thus NOT due to a corrupted system to my point of view.
Two other tickets follow…
The text was updated successfully, but these errors were encountered: