grabbad.blogg.se

+ display = self.get_unused_display_number() – raise Exception("Could not start Xvfb.") – screen_option = "%dx%dx24" % (max_width, max_height) – ("Starting %s on display :%d" % (xvfb, display)) – while os.path.exists(X_LOCK_FILE_TEMPLATE % display): """Return a candidate display number for which there is currently no

# Amount of time to wait between relaunching processes. SYSTEM_SESSION_FILE_PATH = "/etc/chrome-remote-desktop-session" SCRIPT_DIR = -90,7 +90,7 SESSION_FILE_PATH = os.path.join(HOME_DIR, ".chrome-remote-desktop-session") # If RANDR is not available, use a smaller default size. # defaults can be overridden in ~/.profile. # resolutions that will be made available if the X server supports RANDR. Now it attaches to Unity’s existing X Server on display :0.Ĭredit to the discussion of these post !topic/chrome/LJgIh-IJ9Lkĭiff –git a/chrome-remote-desktop.orig b/chrome-remote-desktop opt/google/chrome-remote-desktop/chrome-remote-desktop –startĭONE. Self.child_env = “:%d” % display #Pls change the quotes to plain quotes Alter launch_session() by commenting out launch_x_server() and launch_x_session() and instead setting the display environment variable, so that the function definition ultimately looks like the following:ĭisplay = self.get_unused_display_number()

Reuse the existing X session instead of launching a new one. #while os.path.exists(X_LOCK_FILE_TEMPLATE % display): Set the X display number to the current display number (obtain it with echo $DISPLAY from any terminal).Ĭomment out sections that look for additional displays: opt/google/chrome-remote-desktop/chrome-remote-desktop –stopĬp /opt/google/chrome-remote-desktop/chrome-remote-desktop /opt/google/chrome-remote-desktop/chrome-remote-desktop.origĮdit: /opt/google/chrome-remote-desktop/chrome-remote-desktop The default configuration of Chrome Remote Desktop in Ubuntu opens a new session instead the same desktop currently running.