- CHROME REMOTE DESKTOP CHANGE PIN HOW TO
- CHROME REMOTE DESKTOP CHANGE PIN CODE
- CHROME REMOTE DESKTOP CHANGE PIN WINDOWS
It says "No such file or directory", so I created that directory, as described in the steps at the top, and that fixed the problem. It may take up to five minutes for the Chrome Remote Desktop to exit on this machine and for local login to start working again.įailed to load config: No such file or directory: '/home/username/.config/chrome-remote-desktop/host#98a9a95d871bdecaeb1ebddc57c9cdfe.json' If you run into this issue, you can stop Chrome Remote Desktop by visiting on another machine and clicking the delete icon next to this machine. Some GDM versions have a bug that prevents local login while Chrome Remote Desktop is running. 17:15:10,835:WARNING:WARNING: This system uses GDM. Now, let's see the contents of that log file: cat /tmp/chrome_remote_desktop_20200724_171216_b4R1oT Jul 24 17:12:16 hostname systemd: Started LSB: Chrome Remote Desktop service. Jul 24 17:12:16 hostname chrome-remote-desktop. Jul 24 17:12:16 hostname sudo: pam_unix(sudo:session): session closed for user username Jul 24 17:12:16 hostname user-session: pam_unix(chrome-remote-desktop:session): session closed for user username Jul 24 17:12:16 hostname chrome-remote-desktop: Cleanup. Jul 24 17:12:16 hostname chrome-remote-desktop: WARNING: This system uses GDM. Jul 24 17:12:16 hostname user-session: pam_unix(chrome-remote-desktop:session): session opened for user username by (uid=1000) Jul 24 17:12:16 hostname chrome-remote-desktop: Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20200724_> Jul 24 17:12:16 hostname sudo: pam_unix(sudo:session): session opened for user username by (uid=0)
Process: 125177 ExecStart=/etc/init.d/chrome-remote-desktop start (code=exited, status=0/SUCCESS)
In order to get it to start logging, I had to do: usermod -a -G chrome-remote-desktop sudo service service statusĪctive: active (exited) since Fri 17:12:16 EDT 13s ago
CHROME REMOTE DESKTOP CHANGE PIN WINDOWS
Jul 24 17:11:25 hostname systemd: Started LSB: Chrome Remote Desktop service. Video conferencing app Zoom has reached new heights with a big chunk of people switching to remote learning or working due to the viral pandemic In the settings picker, select Windows Hello For Business > Enable Pin Recovery Open Chrome Remote Desktop on the host system Select Reset password, enter a username and a password, and then select. Jul 24 17:11:25 hostname systemd: Starting LSB: Chrome Remote Desktop service. Loaded: loaded (/etc/init.d/chrome-remote-desktop generated)Īctive: active (exited) since Fri 17:11:25 EDT 22s agoĬGroup: /system.slice/rvice rvice - LSB: Chrome Remote Desktop service.First, we need to get the status log: service status The solution to my problem might not be the solution that works for you, so let me show you how I found my solution so you can find your own.
CHROME REMOTE DESKTOP CHANGE PIN HOW TO
If you encounter errors, prefix each command (line of text) that errored with sudo) How To Perform Your Own Assessment Of The Problem (Open the terminal with Ctrl+Alt+T, then paste the above commands into the terminal. I Ctrl+F5 at before trying to reinstall it.I ran dpkg -pure chrome-remote-desktop to remove the former installation.I made sure I was logged into my Google Account both in my browser's profile and at.I uninstalled the Chrome-Remote-Desktop extension.
I had a highly specific issue with ~/.config/chrome-remote-desktop not being found, and fixed it with: mkdir -p ~/.config/chrome-remote-desktopĬhown "$USER:$USER" ~/.config/chrome-remote-desktopĬhmod a+rx ~/.config/chrome-remote-desktop This tutorial can be used for both " real PC" and " virtual PC" installations.~/.config/chrome-remote-desktop Not Found We hope that points mentioned on this page can also help the Chrome Remote Desktop developer in so way.
Product which can be used across all platforms. We think the Chrome Remote Desktop developers are really doing a great job and are developing a fantastic Unpleasant bugs we would like to solve before publishing the solution on this page.Ĭhrome Remote Desktop for Linux is still in its beta phase, so we can expect bugs. While preparing this tutorial, we found a few
CHROME REMOTE DESKTOP CHANGE PIN CODE
We really learned a lot while studying the Chrome Remote Desktop code and are also looking into applying this solution in other areas. We hope that this tutorial will save others the time. We took about a week to get a usable system running. This tutorial is one of the cases, where we required a certain functionality, did the standard installation which didn't work, and then searched the internet for solutions and tried everything weĬould think of.
0 kommentar(er)
