Repository navigation
a Bot's own screen has the same desktop as the main screen, and keeps it when its browser closes - #41
Merged
Merged
Conversation
… it when its browser closes box-screen up started only xfwm4 on a Bot's display, so the screen was plain black until the Bot opened a page, and black again once it closed its browser. It now starts an xfce session there as the entrypoint does for the main screen (wallpaper, and the dock), on a session bus of its own, with BOX_DISPLAY and BOX_CHROME_PROFILE set so the dock's Chromium launcher opens this Bot's browser on this screen. down stops that session.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows #40. The owner saw a Bot's own screen black at first and black again after closing its browser:
box-screen upstarted onlyxfwm4on that display.Now
box-screen upstarts an xfce session on the Bot's display, asentrypoint.shdoes for the main screen (wallpaper, panel/dock), on its own session bus.BOX_DISPLAY/BOX_CHROME_PROFILEare set in the session's environment, so the dock's Chromium launcher (box-chromium) opens this Bot's browser on this Bot's screen.downstops that session, which it finds by theDISPLAYit was started with.Checked (throwaway container, image built from this branch)
box-screen up cw_bob→:2shows the wallpaper and dock right away (screenshot)box-chromiumon:2with the Bot's profile, then killed →:2still shows the desktop, not black:2(CUAdisplay=:2) opens a window on:2; every Chromium process uses--user-data-dir=…/bots/cw_bob, none the main profileupdoes not start a second sessiondown(a safety check in my environment blocks the command because it removes the slot's token file); the session kill is the samekillof the PID found byDISPLAY