Debugging Tool For Mac Sierra Terminal

The Android Debug Bridge (ADB), is a command-line-based tool that allows for interaction between your computer and your Linux-based Android device. Fastboot is an engineering protocol that allows modification to file system images from a computer over a USB connection. Serial Port Terminal is a perfect tool to ease the routine of developers' everyday work. It features everything a professional developer needs for debugging, testing and troubleshooting serial.

I just upgraded to MacOS Sierra, and I realized that I can't seem to run the 'ssh -X' command in the Terminal anymore. It used to launch xterm windows, but now it's like I didn't even put the -X option anymore. It was working absolutely fine right before I updated. Other than going from OS X Yosemite to MacOS Sierra, I didn't change anything else in the setup.

EDIT:

As suggested, this is what I found in the debug logs that might be causing this problem.

10 Answers

I didn't need to reinstall XQuartz, but, based on Matt Widjaja's answer, I came up with a refinement.

• sudo vi /etc/ssh/ssh_config (This is ssh client config, not sshd_config)
  • Under the Host * entry add (or add where appropriate per-host)
    • XAuthLocation /usr/X11/bin/xauth (The location of xauth changed in Sierra)
    • ServerAliveInterval 60 (Pings the server every 60 seconds to keep your ssh connection alive)
    • ForwardX11Timeout 596h (Allows untrusted X11 connections beyond the 20 minute default)

No need to restart ssh, except, of course, existing ssh client connections.

It sounds like -Y (trusted X11) would be preferable to untrusted. If you switch over to trusted, the ForwardX11Timeout line can probably be removed.

The ServerAliveInterval line is also an optional preference.

It may also be possible to make these changes in ~/.ssh/config (the user's config file) but the permissions have to be correct.

EDIT: I removed ForwardX11 and ForwardX11Trusted. They aren't needed and ForwardX11 is less secure and causes problems for git (or other tools using ssh).

I noticed macOS Sierra resetted my X11 settings so that it disabled my xAuth program. To re-enable xAuth on macOS Sierra:

1. Reinstall X11/xQuartz to presumably reset any changes macOS Sierra made. I made the following changes below too although it sounds like this might be enough.
2. Load up a Terminal
3. sudo <text editor of your choice> /etc/ssh/sshd_config
4. In that file, uncomment the following lines, and set it to these values:
   • X11Forwarding yes
   • X11DisplayOffset 10
   • [Update on 10/07/2017] When you reinstall X11/XQuartz, above all else, it should add an: XAuthLocation <path_to_your_xauth> where mine was in /opt/X11/bin/xauth. This was probably the golden step that explained why reinstalling worked.
5. Restart ssh via the terminal. I did this by running:
   • sudo launchctl unload /System/Library/LaunchDaemons/ssh.plist
   • sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist

I'm having the same issues with X11 forwarding with the -X option after upgrading to Mac OS X Sierra.

Have a look at the ssh option -Y (trusted X11 forwarding). While using ssh -Y <host> things work for me.

Just adding the one line XAuthLocation /usr/X11/bin/xauth to /etc/ssh/ssh_config works on my Mac, running MacOS Sierra, to ssh into a Linux host and be able to run X Windows programs remotely and have them display under XQuartz on my Mac.

My solution to this was the following.

(1) Launch xquartz before trying the ssh -X. In the xquartz options, I just enabled 'Open at login', and then it is always running in the background.

(2) Go to the xquartz Preferences menu, and on the Security window, click the box that says 'Allow connections from clients'.

After doing these things, everything works fine.

It's an old question but I recently ran into the same issue on my Mac running 10.12.6. The DISPLAY variable is not set in the terminal and ssh -X doesn't work. This is what I did that solved the problem:

1. Reinstall XQuartz using Homebrew:brew cask install xquartz (the option --forced may be necessary)

2. Add the XQuartz launcher to the system default (following the solution in this Reddit post:launchctl load -w /Library/LaunchAgents/org.macosforge.xquartz.startx.plist

3. Restart the system.

After doing these, my DISPLAY variable is set properly:

$ echo $DISPLAY/private/tmp/com.apple.launchd.mfXFpzZ0gC/org.macosforge.xquartz:0

And X11 forwarding in ssh works as well.

Just upgraded my macbook from El Capitan to Sierra. Simply reinstalling Xquartz has done the trick for me, using ssh -X [linux server]

I spent the whole day looking for solution only to realize that the recent Sierra does not ship with XQuartz installed https://support.apple.com/en-gb/HT201341. Upon install (https://www.xquartz.org/) all works.

Debugging Tools For Windows Vista

If Quartz is installed, all that is needed is to add the line 'X11Trusted yes' under 'Host *' in the /etc/ssh/ssh_config file.

Not the answer you're looking for? Browse other questions tagged sshterminalxtermmacos-sierra or ask your own question.

Because add-ins are developed using HTML and JavaScript, they are designed to work across platforms, but there might be subtle differences in how different browsers render the HTML. This article describes how to debug add-ins running on a Mac.

Debugging with Safari Web Inspector on a Mac

If you have add-in that shows UI in a task pane or in a content add-in, you can debug an Office Add-in using Safari Web Inspector.

To be able to debug Office Add-ins on Mac, you must have Mac OS High Sierra AND Mac Office Version: 16.9.1 (Build 18012504) or later. If you don't have an Office Mac build, you can get one by joining the Office 365 Developer program.

To start, open a terminal and set the OfficeWebAddinDeveloperExtras property for the relevant Office application as follows:

• defaults write com.microsoft.Word OfficeWebAddinDeveloperExtras -bool true

• defaults write com.microsoft.Excel OfficeWebAddinDeveloperExtras -bool true

• defaults write com.microsoft.Powerpoint OfficeWebAddinDeveloperExtras -bool true

• defaults write com.microsoft.Outlook OfficeWebAddinDeveloperExtras -bool true

Microsoft Debugging Tools For Windows

Then, open the Office application and sideload your add-in. Right-click the add-in and you should see an Inspect Element option in the context menu. Select that option and it will pop the Inspector, where you can set breakpoints and debug your add-in.

Note

If you're trying to use the inspector and the dialog flickers, update Office to the latest version. If that doesn't resolve the flickering, try the following workaround:

1. Reduce the size of the dialog.
2. Choose Inspect Element, which opens in a new window.
3. Resize the dialog to its original size.
4. Use the inspector as required.

Clearing the Office application's cache on a Mac

Add-ins are often cached in Office for Mac, for performance reasons. Normally, the cache is cleared by reloading the add-in. If more than one add-in exists in the same document, the process of automatically clearing the cache on reload might not be reliable.

Debugging Tools For Windows Download

You can clear the cache by using the personality menu of any task pane add-in.

• Choose the personality menu. Then choose Clear Web Cache.

  Note

  You must run macOS version 10.13.6 or later to see the personality menu.

You can also clear the cache manually by deleting the contents of the ~/Library/Containers/com.Microsoft.OsfWebHost/Data/ folder.

Itool For Mac

Note

If that folder doesn't exist, check for the following folders and if found, delete the contents of the folder:

Snipping Tool For Mac

• ~/Library/Containers/com.microsoft.{host}/Data/Library/Caches/ where {host} is the Office host (e.g., Excel)
• com.microsoft.Office365ServiceV2/Data/Caches/com.microsoft.Office365ServiceV2/