[Cyberduck-trac] [Cyberduck] #7774: Transfer does not include directory content

Cyberduck trac at trac.cyberduck.io
Tue Feb 4 06:45:28 UTC 2014


#7774: Transfer does not include directory content
---------------------------+------------------------
 Reporter:  ronan_paul     |         Owner:  dkocher
     Type:  defect         |        Status:  new
 Priority:  normal         |     Milestone:
Component:  ftp            |       Version:  4.4.3
 Severity:  blocker        |    Resolution:
 Keywords:                 |  Architecture:  Intel
 Platform:  Mac OS X 10.9  |
---------------------------+------------------------

Comment (by ronan_paul):

 As requested, I installed Cyberduck Version 4.4.4 (14300)
 I initiated again the transfer of a directory, and only the directory was
 trasnfered, not its content.

 I looked in the system log, here are the last entries:
 04/02/2014 07:38:40,284 launchservicesd[112]: Application App:"Cyberduck"
 asn:0x0-39b39b pid:12962 refs=7 @ 0x7fb52e2c08d0 tried to be brought
 forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x495495
 pid=19263 "SecurityAgent"")), so denying. : LASSession.cp #1481
 SetFrontApplication() q=LSSession 100005/0x186a5 queue
 04/02/2014 07:38:40,284 WindowServer[134]: [cps/setfront] Failed setting
 the front application to Cyberduck, psn 0x0-0x39b39b,
 securitySessionID=0x186a5, err=-13066
 04/02/2014 07:38:40,335 authexec[19272]: executing /bin/mv
 04/02/2014 07:38:40,381 authexec[19274]: executing /bin/mv
 04/02/2014 07:38:40,429 authexec[19275]: executing /bin/rm
 04/02/2014 07:38:40,895 authexec[19276]: executing /usr/sbin/chown
 04/02/2014 07:38:41,017 Cyberduck[12962]: [background-1] ERROR
 ch.cyberduck.core.Resolver - Error awaiting lock for resolver null

 java.lang.InterruptedException
         at
 java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:996)
         at
 java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
         at
 java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
         at ch.cyberduck.core.Resolver.resolve(Resolver.java:98)
         at
 ch.cyberduck.core.LoginConnectionService.connect(LoginConnectionService.java:124)
         at
 ch.cyberduck.core.LoginConnectionService.check(LoginConnectionService.java:95)
         at
 ch.cyberduck.core.threading.SessionBackgroundAction.connect(SessionBackgroundAction.java:175)
         at
 ch.cyberduck.ui.threading.BrowserBackgroundAction.connect(BrowserBackgroundAction.java:57)
         at
 ch.cyberduck.core.threading.SessionBackgroundAction.call(SessionBackgroundAction.java:158)
         at
 ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:159)
         at java.util.concurrent.FutureTask.run(FutureTask.java:262)
         at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
         at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
         at
 ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
         at java.lang.Thread.run(Thread.java:724)
 04/02/2014 07:38:41,031 Cyberduck[12962]: CoreAnimation: warning, deleted
 thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in
 environment to log backtraces.
 04/02/2014 07:38:44,437 WindowServer[134]:
 _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
 04/02/2014 07:38:45,669 WindowServer[134]: disable_update_timeout: UI
 updates were forcibly disabled by application "Cyberduck" for over 1.00
 seconds. Server has re-enabled them.
 04/02/2014 07:38:48,059 WindowServer[134]: common_reenable_update: UI
 updates were finally reenabled by application "Cyberduck" after 3.39
 seconds (server forcibly re-enabled them after 1.00 seconds)
 04/02/2014 07:39:50,719 Mail[11210]: CFNetwork SSLHandshake failed (-9807)
 04/02/2014 07:39:54,022 Mail[11210]: [<_MCLibSasl2SaslClient:
 0x6080006a5be0> mechanism: PLAIN security layer: no] Failed to start the
 SASL connection
 SASL(-1): generic failure:
 04/02/2014 07:39:55,857 Mail[11210]: [<_MCLibSasl2SaslClient:
 0x6080004a7d40> mechanism: PLAIN security layer: no] Failed to start the
 SASL connection
 SASL(-1): generic failure:

 Hope this helps.

 Ronan

-- 
Ticket URL: <https://trac.cyberduck.io/ticket/7774#comment:4>
Cyberduck <http://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list