AWS res documentation change
Summary
Added troubleshooting section for VDI blank screen issue with Xorg configuration fixes
Security assessment
The change documents a technical workaround for Xorg configuration issues causing blank screens, but does not address security vulnerabilities or describe security features.
Diff
diff --git a/res/latest/ug/res-troubleshooting-issue-runbooks.md b/res/latest/ug/res-troubleshooting-issue-runbooks.md index 631a6278c..154cd41d4 100644 --- a//res/latest/ug/res-troubleshooting-issue-runbooks.md +++ b//res/latest/ug/res-troubleshooting-issue-runbooks.md @@ -82,0 +83,2 @@ The following section contains issues that may occur, how to detect them, and su + * VDI session goes to a blank screen after logging in + @@ -750,0 +753,2 @@ If both Healthy and Unhealthy entries are 0, that indicates a potential network + * VDI session goes to a blank screen after logging in + @@ -981,0 +986,18 @@ This could be the issue you are facing if the following scenarios are true: +........................ + +### VDI session goes to a blank screen after logging in + +When a VDI session with Console Session type is blank and unresponsive after you log in, this means that the X server is broken. This likely is due to a OS issue where DCV is attempting to stream the desktop, but there isn't one to stream. The most probable cause of this is an issue with the Xorg configuration. The following command can be run to rely less on the default Xorg configuration. + +**Debian based Linux:** + + + dpkg-divert --package nice-xdcv --divert /usr/bin/Xorg.orig --rename /usr/bin/Xorg ln -sf /usr/bin/Xdcv-console /usr/bin/Xorg + +**Red Hat based Linux:** + + + rpm -q --whatprovides /usr/bin/Xorg && \ + cp /usr/bin/Xorg /usr/bin/Xorg.orig && \ + ln -sf /usr/bin/Xdcv-console /usr/bin/Xorg +