Use gnome-remote-desktop.service #5809
Closed
Conversation
This file contains 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
A couple issues so far with the regular gnome-remote-desktop.service: - does not usew the --headless parameter - does not set HOME to the place we need it to Appears to start, but it does not look like we can connect to it. :P
|
Hello @M4rtinK! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:
|
|
Resolved via: #5842 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The idea is to get ridd of spam on TTY1 & have that redirected to Journal by running the GNOME binaries via systemd services. The only service that looks usable so far is
gnome-remote-desktop.service- lets try to use it first.A couple issues so far with
gnome-remote-desktop.service:$HOMEto/rootAppears to start, but it does not look like we can connect to it. :P
Also it looks like the TTY1 is still full of spam, so it does not look like GNOME Remote Desktop is the actual culprit.