KamoCRM

Xrdp was told its session backend was itself, so nothing ever rendered

FixKlusterServices
Spegnimento
24 settembre 2026 alle ore 04:12 UTC
Autore
Kamo
Impegno
1dba600

Opening a computer gave a black screen that never became a desktop. The cause is one unanchored sed in this file: sed -i 's/^port=.*/port=3389/' /etc/xrdp/xrdp.ini It was meant to set the listener. xrdp.ini has FIVE port= lines and only the first is a listener; the rest are the backend each session type connects to. [Xorg] ships `port=-1`, meaning "sesman allocates the display and xrdp reaches it over the local socket". Rewritten to 3389 next to its `ip=127.0.0.1`, it tells xrdp that its session backend is the listener — itself. Every connection then dials 3389, reads its own protocol back as garbage, and dies on the first packet: [ERROR] libxrdp_force_read: header read error [ERROR] [ITU-T X.224] Connection Sequence: CR-TPDU (Connection Request) failed Confirmed against the distribution's own file: [Xorg] port=-1 there, port=3389 in the image. EVERY SYMPTOM POINTED SOMEWHERE ELSE. guacd logs "RDP server closed/refused connection: Manually logged off", which reads as the guest hanging up on purpose. xrdp-sesman.log records no session at all, so there is no authentication failure to find. /home/<member>/ has no .xsession-errors and no .xorgxrdp log, because nothing ever got as far as starting a session — which also makes every desktop, Xwrapper and polkit theory unfalsifiable by inspection, since none of them was ever reached. The sed is now anchored to the first match, and the build FAILS if [Xorg] has lost port=-1. Without that check this is invisible until somebody opens a computer, which is the whole problem with it.

Tutte le modifiche

Come quello che vedi la spedizione?

Tutto questo arriva nel vostro spazio di lavoro da solo. Iniziare sul piano gratuito e leggere di nuovo questa pagina in un mese.

Inizia gratis per sempreVisualizza il prezzo