Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Crash with Cannot listen on pipe name error #11641

Closed
cyberduck opened this issue Apr 6, 2021 · 4 comments
Closed

Crash with Cannot listen on pipe name error #11641

cyberduck opened this issue Apr 6, 2021 · 4 comments
Labels
bug core fixed

Comments

@cyberduck
Copy link
Collaborator

fc6fc5a created the issue

This just started happening.
The timing was right after I removed an s3 bucket from AWS that was included in a Cyberduck shortcut

The workaround is that I just ignore the crash dialog and leave it open ( if I click send or dont send report it closes the whole app. If I ignore the dialog and leave it open, I can work in the app without a problem)
However this a nuisance despite the workaround.
I just upgraded to the latest version to no avail

Attachments
@cyberduck
Copy link
Collaborator Author

3cbfc3c commented

Hi,

Please attach the latest crash report for further investigation. You can reach the crash report

  • on macOS by navigating to ~/Library/Logs/DiagnosticReports - the crash report is named Cyberduc_*.crash.
  • on Windows by navigating to %AppData%\Cyberduck\CrashReporter.

– Sofie

@cyberduck
Copy link
Collaborator Author

@dkocher commented

15	[Exception Info 1]
16	
17	Top-level Exception
18	Type:        System.IO.PipeException
19	Message:     Cannot listen on pipe name 'net.pipe://localhost/iterate/cyberduck.io' because another pipe endpoint is already listening on that name.
20	Source:

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you reproduce the crash after restarting your computer?

@cyberduck
Copy link
Collaborator Author

fc6fc5a commented

Thanks. Rebooting the computer fixed the problem.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug core fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck