Gui Ssh Client For Mac High Sierra


Well, many Mac users have discovered that Telnet has been removed from modern versions of system software, including macOS Mojave and macOS High Sierra. Presumably this is to encourage using the ssh client instead, but there are many Mac users who need Telnet for a variety of reasons. WinOnMacs released Pterm for Mac 9.1.0 for MacOS today. Pterm 9.1.0 is a major release, we now have full 64bit support for macOS High Sierra and macOS Mojave. Please see the full change-log below for all the changes in this release.

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up 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.

No GUI at all after High Sierra update. Discussion in 'High Sierra Desktop Support' started. Can run the server app on my macbook and connect to it, and it is still working as an email server. I am also able to SSH into it. I can mount the EFI partition manually and work with the clover boot files and directories as well as see the. Dec 20, 2017  Question: Q: ssh failure after upgrading to high sierra. For the other end of the ssh connection, you can ask your ssh client what ciphers, message authentication codes and key exchanges are supported with the following: ssh -Q cipher. Of these, I've been usually been encountering problems with kex.

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


commented Nov 25, 2017
edited by SamuAlfageme

Steps to reproduce

Upgrade to High Sierra
Start owncloud via applications/owncloud
Upgrade (and or remove existing owncload and replace with 2.3.4 or 2.4 (beta)

Any diagonostic advice will be taken. I can't find any logs other than a dmp file.

Expected behaviour

Owncloud desktop app opens and runs and is visible in taskbar

Actual behaviour

Owncloud crashes immediately with error: 'Sorry! Owncloud crashed please tell us about it!...'

Server configuration

Operating system:

mac os 10.13.1

Web server:

PHP version:
ownCloud version: (see ownCloud admin page)
2.3.4 or 2.4
Updated from an older ownCloud or fresh install:
Where did you install ownCloud from:

added Needs infoOSX labels Nov 27, 2017

commented Nov 27, 2017

@migs540 thanks for pointing this out. Did you submit a crash report when the issue happened?

Will take a look at the logs in nextcloud/desktop#57 (comment) to see if something rings a bell in there.

commented Nov 27, 2017

If you are asking whether i clicked on 'send' or 'don't send' I clicked on send. Is that what you mean @SamuAlfageme ?

other open issue referenced:
yeah pretty similar in the log file. Here's mine:

with tail showing:

commented Nov 27, 2017

@migs540 hm. It does look like #6049, we patched a few things up around this in #6161

Could you give 2.4.0 beta1 from a try to see if it solved your problem?

commented Nov 27, 2017

Hi @SamuAlfageme

Sorry, no good, same error with new version (it died a minute ago and I clicked 'send' in the dialogue).

commented Nov 27, 2017

My current workaround is to use file sharing from one mac (high sierra where owncloud own't run) to another mac (previous os version) where the desktop client runs. It's a really clunky workaround. All errors above from high sierra mac.

commented Nov 27, 2017

So we don't need to fish our the crash trace from the crash handler:

Then on crash type:


commented Nov 27, 2017

@guruz damn, could this be an edge case of #5650?

I can't find anything relatable to the logs in high-sierra on sentry

commented Nov 27, 2017

thread apply all bt

isn't recognised. I can get to 'thread' but not 'thread apply' - see below for usage and let me know if you want me to run another command.

commented Nov 27, 2017

@migs540 Mixed up the gdb and lldb syntax :-/

bt all

could work?

commented Nov 27, 2017

@guruz I tried a few things. Out of my depth:

key line: error: Process must be launched.

commented Nov 27, 2017

On 27. Nov 2017, at 13:52, michael grau ***@***.***> wrote: I tried a few things. Out of my depth: key line: error: Process must be launched. (lldb) thread backtrace all error: invalid thread (lldb) thread backtrace error: invalid thread (lldb) thread Commands for operating on one or more threads in the current process. Syntax: thread The following subcommands are supported: backtrace -- Show thread call stacks. Defaults to the current thread, thread indexes can be specified as arguments. Use the thread-index 'all' to see all threads. continue -- Continue execution of the current target process. One or more threads may be specified, by default all threads continue. info -- Show an extended summary of one or more threads. Defaults to the current thread. jump -- Sets the program counter to a new address. list -- Show a summary of each thread in the current target process. plan -- Commands for managing thread plans that control execution. return -- Prematurely return from a stack frame, short-circuiting execution of newer frames and optionally yielding a specified value. Defaults to the exiting the current stack frame. Expects 'raw' input (see 'help raw-input'.) select -- Change the currently selected thread. step-in -- Source level single step, stepping into calls. Defaults to current thread unless specified. step-inst -- Instruction level single step, stepping into calls. Defaults to current thread unless specified. step-inst-over -- Instruction level single step, stepping over calls. Defaults to current thread unless specified. step-out -- Finish executing the current stack frame and stop after returning. Defaults to current thread unless specified. step-over -- Source level single step, stepping over calls. Defaults to current thread unless specified. step-scripted -- Step as instructed by the script class passed in the -C option. until -- Continue until a line number or address is reached by the current or specified thread. Stops when returning from the current function as a safety measure. The target line number(s) are given as arguments, and if more than one is provided, stepping will stop when the first one is hit. For more help on any particular subcommand, type 'help <command> <subcommand>'. (lldb) thread info error: Process must be launched. (lldb) r Process 22529 launched: '/Applications/' (x86_64) 2017-11-27 20:50:29.505929+0800 owncloud[22529:3996608] MessageTracer: load_domain_whitelist_search_tree:73: Search tree file's format version number (0) is not supported 2017-11-27 20:50:29.505976+0800 owncloud[22529:3996608] MessageTracer: Falling back to default whitelist m_crashReporterChar: /Applications/ m_crashReporterWChar: /Applications/ file was written to: /var/folders/y0/3dv2xzq15qq_5qvzwvb1_z3m0000gn/T/689F47E8-52C5-43A5-A3C6-466CA6BA65E1.dmp Process 22529 exited with status = 1 (0x00000001) (lldb) thread info error: Process must be launched. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

commented Nov 27, 2017

Same reason behind: #6074 (comment)

Ssh For Mac

commented Nov 27, 2017

r is short for run so it's the same behaviour see below ...So I should close this one as it's the same as #6074?

added bugp2-high labels Nov 27, 2017

commented Nov 27, 2017

@SamuAlfageme ufff... thanks. Sounds very related then

@migs540 Ah, because the build is compiled with the crash reporter compiled in, you can't use lldb it seems because it will be wrapped and exited. Let me check how you could still do it (and prove it's the same as @xnicolay in #6074 (comment)

commented Nov 27, 2017

Gui Ssh Client For Mac High Sierra

In your home -> Application Support/ownCloud/owncloud.cfg
Section [General]
Add (or set) crashReporter=false

Ssh Client For Mac


commented Nov 27, 2017

I have the same issues on my mac:

commented Nov 28, 2017

@MrBetatester Thanks for the backtrace! So at least part of this is #6123

commented Nov 28, 2017

@guruz with crashreporter set to false

commented Nov 28, 2017

I'm new to github... what's the right thing to do with this now it's listed as a bug? Do I close it, leave it open or amend it in some way?

commented Nov 28, 2017

leave it open until the bug is fixed

I think line 49 is the issue. Maybe the app name is not set because the app isn't finish with the startup. I will build my own client tomorrow and try to fix it by my self.

commented Nov 28, 2017

@[email protected] Can you please test with ?

added ReadyToTest and removed Needs info labels Nov 28, 2017

commented Nov 28, 2017

@guruz Great news, it works for me. Let me know if you want me to run any specific tests.

Awesome stuff.

commented Nov 28, 2017

@migs540 Yay :) You can test if having the client launch on startup/login still works (there is a checkbox setting in the Settings dialog for it)

commented Nov 28, 2017

@guruz OK I'll startup tomorrow. Just paused it because I am getting a massive amount of _conflict files generated.

commented Nov 28, 2017

@guruz yes it is working again. Autostart also works but it was not enabled as default?

commented Nov 29, 2017

Great : now, i can remember what owncloud seems !

commented Nov 29, 2017

Fantastic 👏

commented Dec 28, 2017

I'm experiencing this on a fresh install of High Sierra with the latest stable, and the latest 2.4 nightlies.

commented Dec 28, 2017

I tried installing from homebrew, and that worked Version 2.3.4 (build 8537). Not sure if I want to tempt upgrading to the latest versions.

Mac Os Ssh Client

commented Dec 30, 2017

Ssh Client For Mac Os X

@mazubieta That's a different one which is tracked in #6268
Can you report there something about your setup?
Fresh install of High Sierra with fresh install of 2.4. With homebrew installed too or not? etc
(Discuss in #6268 not here)

Best Ssh Client For Mac

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment