Merge pull request microsoft#35 from MicrosoftDocs/master

Updated linux details

docs/troubleshooting.md

@@ -52,6 +52,7 @@ The following are troubleshooting tips for sign in problems.
 | All | You signed up and were accepted into the preview using an <strong>email address not tied to a Microsoft work, school, or personal account or GitHub account</strong>. | A simple resolution is to add this email address as a secondary email to your GitHub account and sign in that way. VS Live Share simply validates that an accepted email is in your profile when you sign in with GitHub. (Note: Use Tools > Options > Live Share > User account to sign in via GitHub from Visual Studio.) <br /><br /> If that won't work, send a mail to [vsls-feedback@microsoft.com](mailto:vsls-feedback@microsoft.com) and we will switch out your email address.<br /><br />If you have not signed up, you can do so [here](https://aka.ms/vsls-signup) and we will let you know when you've been accepted. |
 | All | When signing in using a Microsoft backed **work or school email address** you see a message saying, **"Need admin approval"**. | Your Azure AD tenet is setup to require “admin consent” for new applications accessing the contents of the directory. Your AD admin would need to resolve this for you but it would only need to be done once for anyone using Live Share. See [here](https://stackoverflow.com/questions/39861830/azure-ad-admin-consent-from-the-azure-portal) and [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-scopes#admin-restricted-scopes).<br /><br /><ul><li>Application Name: Visual Studio Live Share (Insiders)</li><li>Application Type: Web App</li><li>Applications Status: Production</li><li>Delegated Permissions: User.Read</li><li>Application URL: https://insiders.liveshare.vsengsaas.visualstudio.com/</li><li>Reply URL: https://insiders.liveshare.vsengsaas.visualstudio.com/auth/redirect/windowslive/</li></ul><br /> If this is not possible, contact vsls-feedback@microsoft.com and ask to switch to a personal Microsoft account or a GitHub account instead. |
 | VS Code (**macOS**) | When signing in you see an error stating **SecKeychainAddGenericPassword() failed**. | This is almost always due to a common problem with macOS where password changes are not reflected in the login keychain. Try going into "Keychain Access", locking the login keychain and then unlocking it again. This may be enough to resolve the problem, but if you are unable to unlock it with your current password, try your previous one. If that works, change the login keychain password to your current password. See [here](https://support.apple.com/en-us/HT201609) for details. |
+| VS Code (**Linux**) | When entering in the user code after signing in via the browser you see an error stating **secret_password_store_sync() failed with error code XX**. | This is typically due to `gnome-keyring` and/or `libsecret` not being installed. You can validate gnome-keyring is properly configured by installing `seahorse` and then using the "Passwords and Keys" application in your desktop environment. Read more about [Linux pre-requisites here](use/vscode.md#install-linux-prerequisites). |
 | VS Code (**Linux**) | You are <strong>prompted to enter a user code</strong> but no browser appears to allow you to get one. | We are working to eliminate the user code requirement on Linux. In the mean time, a browser window should appear for you to use to sign in. If not, the browser window may be hidden under VS Code. See the next tip if this is not the case.  |
 | VS Code | After clicking "Sign in" (or using the "Live Share: Sign in" command), <strong>no browser window appears to allow you to enter your credentials</strong>. | 1. Sign in at https://insiders.liveshare.vsengsaas.visualstudio.com/auth/login<br />2. After signing in, click "Having trouble?"<br /> 3. Follow the directions to enter a temporary user code into the tool.<br /><br />Please also run the "Live Share: Export Logs" command and include the zip and a comment on [this bug](https://github.com/MicrosoftDocs/live-share/issues/89). |
 

docs/use/vscode.md

@@ -43,7 +43,7 @@ Before you begin, you'll need to be sure you've got a version of Visual Studio C
 - **Linux**: 64-bit Ubuntu Linux 16.04+, see [below](#linux-install-steps) for information on other distributions.
 
     - **Be sure to install [needed Linux prerequisites](#install-linux-prerequisites)**.
-    - Testing has also occurred on 64-bit Mint 18.3, Fedora 27, CentOS 7, and SuSE 12, and Manjaro 17.1 (though Arch and Manjaro are not officially supported by either VS Code or .NET Core).
+    - Testing has also occurred on 64-bit Mint 18.3, Fedora 27, CentOS 7, and SuSE 12, and Manjaro 17.1 (though ArchLinux and Manjaro are not officially supported by either VS Code or .NET Core).
     - However, given the rate of change in the Linux world, your mileage may vary. See [below](#linux-install-steps) for details.
     - _32-bit Linux is not supported due to [.NET Core 2.0 requirements](https://go.microsoft.com/fwlink/?linkid=872314)_
 
@@ -69,16 +69,18 @@ Some distributions of Linux are missing needed libraries for Live Share. The fol
 
 | Distribution | Missing libraries |
 |--------|-------------------|
-| Ubuntu 17.10 (64-bit) | libunwind8, liblttng-ust0 |
+| Ubuntu 17.10 (64-bit) | `libunwind8 liblttng-ust0` |
 | Ubuntu 16.04 (64-bit) | <none> |
-| Kubuntu 16.04 (64-bit) | libunwind8, liblttng-ust0, gnome-keyring, desktop-file-utils |
-| Xubuntu 16.04 (64-bit) | libunwind8, liblttng-ust0 |
-| Mint 18.3 - Cinnamon (64-bit) | libcurl3 |
+| Kubuntu 16.04 (64-bit) | `libunwind8 liblttng-ust0 gnome-keyring desktop-file-utils` |
+| Xubuntu 16.04 (64-bit) | `libunwind8 liblttng-ust0` |
+| Mint 18.3 - Cinnamon (64-bit) | `libcurl3` |
 | Fedora 27 (64-bit) | <none> |
 | openSuSE 12 (64-bit) | <none> |
 | CentOS 7 | <none> |
 
-Note that the Linux ecosystem moves quickly, and your results may vary. Additional details can be found below on the libraries typically required.
+Note that the Linux ecosystem moves quickly and that the package names may vary in certain distributions, so your results may vary. Additional details can be found below on the libraries typically required.
+
+For example, *ArchLinux* is not officially supported by VS Code or .NET Core (and thus by extension Live Share), but there are community packages for them and we have found that the `gnome-keyring` and `libsecret` libraries are often missing from these as the community has opted to try out Live Share. You should also be aware libraries like gnome-keyring may require additional [setup steps](https://wiki.archlinux.org/index.php/GNOME/Keyring) in some desktop environments so check your distribution's documentation for details.
 
 ##### List of needed libraries
 
@@ -102,13 +104,14 @@ Visual Studio Live Share uses the .NET Core runtime which requires a number of l
 In addition, the following are libraries **Live Share itself depends on** that may be missing in some instances (e.g. distributions not using Gnome):
 
 - gnome-keyring
+- libsecret-1-0
 - desktop-file-utils
 
 Libraries may be installed on Debian/Ubuntu based distributions by running `sudo apt install <library-name>` in a terminal. For example, this will install everything for Ubuntu/Xubuntu/Kubuntu 16.04 or Mint 18.3:
 
-    sudo apt install libunwind8 liblttng-ust0 libcurl3 libssl1.0.0 libuuid1 libkrb5-3 zlib1g gnome-keyring desktop-file-utils gettext apt-transport-https libicu55
+    sudo apt install libunwind8 liblttng-ust0 libcurl3 libssl1.0.0 libuuid1 libkrb5-3 zlib1g gnome-keyring libsecret-1-0 desktop-file-utils gettext apt-transport-https libicu55
 
-You will need to replace the last library (libicu55) with the appropriate version for your distribution (e.g. libicu57 for Ubuntu 17.10).
+You will need to replace the last library (`libicu55`) with the appropriate version for your distribution (e.g. `libicu57` for Ubuntu 17.10).
 
 **Fedora/CentOS/RHL** requires similar packages but with slightly different names:
 
@@ -124,13 +127,14 @@ You will need to replace the last library (libicu55) with the appropriate versio
 As with Debian/Ubuntu, **Live Share itself** depends on the following:
 
 - gnome-keyring
+- libsecret
 - desktop-file-utils
 
-Libraries may be installed on Fedora/CentOS/RHL based distributions by running `sudo yum install <library-name>` in a terminal. For example, this will install everything: 
+Libraries may be installed on Fedora/CentOS/RHL based distributions by running `sudo yum install <library-name>` in a terminal. For example, this will install everything:
 
-    sudo yum install libunwind lttng-ust libcurl openssl-libs libuuid krb5-libs libicu zlib gnome-keyring desktop-file-utils
+    sudo yum install libunwind lttng-ust libcurl openssl-libs libuuid krb5-libs libicu zlib gnome-keyring libsecret desktop-file-utils
 
-You can [read more about .NET Core 2.0 prerequisites for other distributions here](https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x#linux-distribution-dependencies).
+Other distributions will require the same libraries, but the package names may be subtly different. You can [read more about .NET Core 2.0 prerequisites for other distributions here](https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x#linux-distribution-dependencies).
 
 #### Linux browser integration