Short explanation of the working stack that avoids the i915/GEM shmem leak by using the NVIDIA render node for XRDP.
This gist was drafted with help from an AI assistant based on a live debugging session on this host. Verify details before applying to your system.
| #!/usr/bin/env bash | |
| set -Eeuo pipefail | |
| # Colors for output | |
| RED='\033[0;31m' | |
| GREEN='\033[0;32m' | |
| YELLOW='\033[1;33m' | |
| BLUE='\033[0;34m' | |
| NC='\033[0m' # No Color |
| #!/usr/bin/env bash | |
| # export-copilot-chat.sh | |
| # Interactive script to list and export VSCode Copilot chat sessions to Markdown | |
| # --- Detect default baseDir depending on OS --- | |
| detect_default_basedir() { | |
| case "$(uname -s)" in | |
| Linux) | |
| echo "$HOME/.config/Code/User/workspaceStorage" | |
| ;; |
Documenting XRDP setup which worked for me on Ubuntu Mate 20.04.
Some parts are taken from: http://c-nergy.be/blog/?p=14093.
sudo apt install xrdp
| <?xml version="1.0"?> | |
| <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | |
| <fontconfig> | |
| <alias> | |
| <family>monospace</family> | |
| <prefer><family>Symbols Nerd Font</family></prefer> | |
| </alias> | |
| <alias> | |
| <family>Heavy Data</family> | |
| <prefer><family>Symbols Nerd Font</family></prefer> |
| { | |
| "window.commandCenter": 1, | |
| "makefile.configureOnOpen": false, | |
| "git.confirmSync": false, | |
| "window.zoomLevel": 0, | |
| "workbench.editor.enablePreview": false, | |
| "files.exclude": { | |
| "**/.git": true, | |
| "**/.DS_Store": true, | |
| "**/.history": true, |
| tee /tmp/grd.te << EOF > /dev/null | |
| module grd 1.0; | |
| require { | |
| type system_dbusd_t; | |
| type unconfined_service_t; | |
| type xdm_t; | |
| class tcp_socket { getattr getopt read setopt shutdown write }; | |
| } | |
| allow system_dbusd_t unconfined_service_t:tcp_socket { read write }; | |
| allow xdm_t unconfined_service_t:tcp_socket { getattr getopt read setopt shutdown write }; |
| After searching around, I found the following bug, which explains the cause of the problem and documents a workaround: | |
| https://bugzilla.rpmfusion.org/show_bug.cgi?id=7090 | |
| Following the advice in that bug report, I successfully worked around the problem as follows: | |
| $ sudo systemctl edit systemd-homed | |
| Then add these lines to the config file: | |
| [Service] | |
| Environment="SYSTEMD_HOME_LOCK_FREEZE_SESSION=false" |
| #!/usr/bin/env sh | |
| curl -s -L https://nvidia.github.io/libnvidia-container/stable/rpm/nvidia-container-toolkit.repo | \ | |
| sudo tee /etc/yum.repos.d/nvidia-container-toolkit.repo | |
| sudo dnf install -y nvidia-container-toolkit | |
| sudo nvidia-ctk runtime configure --runtime=docker | |
| sudo systemctl restart docker |