Loop: WARNING! Could not retrieve the X server authentication cookie.įork: WARNING! Function fork failed. Assuming agent session.Īuth: WARNING! Failed to read data from the X auth command.Īuth: WARNING! Generating a fake cookie for X authentication. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'.
The Windows client generates the following in the file. Could it be something about the X server that is running on the x2go server? (It is running but with no sessions, just the login greeter). Since the maximum resolution reported by xrandr corresponds to dpi of 192*1920/2560=144 x 192*1200/1440=160, I wondered if it had something to do with the local X session on the server which is at 149 dpi closing that session, however, makes no difference. I get the same behavior if I try sessions with KDE or XFCE instead of MATE. MATE Settings->Hardware->Displays returns error "RANDR extension is too old (must be at least 1.3)" Xrandr -size 1920x1200 works but keeps same actual dpi of 96 (so desktop is larger than my screen) Thus the actual dpi being used by the display is 192*1280/2560 = 96, not the 192 sent to x2goagent and reported by xdpyinfo.Īttempting to change the resolution from inside the session. Xrandr: Failed to get size of gamma for output default Screen 0: minimum 320 x 240, current 1280 x 720, maximum 1920 x 1200 default connected 1280x720+0+0 0mm x 0mm
Jpdavis: ps -waux | grep $DISPLAY | grep x2goagent with following information obtained inside a MATE terminal: The session starts just fine, filling the screen with the MATE desktop, except that the display resolution is incorrect. Session Type = MATE (automatically changes to "Custom desktop" with command "MATE") Display = Fullscreen Set display DPI = 192 Server = RHEL 7, running local GNOME-3 session at native 3840x2160 (dpi 149) of attached 4K display Installed Packages: I'm hoping that someone out there with more experience will be able to solve this problem!