Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #7112


Ignore:
Timestamp:
Mar 8, 2013 4:38:39 PM (8 years ago)
Author:
dkocher
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7112

    • Property Owner set to yla
  • Ticket #7112 – Description

    initial v1  
    11Cyberduck 4.2.1 installed on Windows 7 Pro SP1 64-bit machine with Intel i5-3570 CPU. Worked relatively fine yesterday morning--by "relatively," I mean that the app could not connect with an S3-compatible site (objects.dreamhost.com) despite the correct keys. On a predecessor machine, running Windows XP Pro SP3, Cyberduck could connect to the site fine. The bookmark data is identical. In any event, after a few tries, Cyberduck stopped launching. An error popped up, indicating that the program "has recently crashed." The problem details are as follows:
    22
     3
     4{{{
    35Problem signature:
    46  Problem Event Name:   CLR20r3
     
    1820  Additional Information 3:     0a9e
    1921  Additional Information 4:     0a9e372d3b4ad19135b953a78882e789
     22}}}
     23
    2024
    2125The problem persists even after warm and cold reboots, and even after uninstalling and reinstalling (although I didn't reboot between the uninstall and reinstall...). Nothing was installed between the time the app worked and the time it stopped working.