Hi Tamas, > Now, about my issue: > I am running a virtual SLES 11 SP2 x64 server on a XenServer. The > latest xrdp was built from source on the server, and running fine. We > use sesman-x11rdp sessions, so user are able to login to the same > session from different workstations. However screen resize is an > issue. Basically it is not working at all. If a user starts a 1024x768 > session, and then leaves it and reconnects with a bigger resolution, > the screen wont be resized. You see a 124x768 rectangle inthe bigger > screen resolution (with all the icons, buttons on the Desktop), but > that`s it. It is even worse the other way around: if you reconnect > with a lower screen size, you wont see the taskbar, so you cannot work > at all.
I see this now too. RandR was working, I don't now what happened. The desktop does not resize like it's saposed to. I know it worked in Xorg7.1 but since the move to Xorg7.6, I'm not sure. It does make the desktop unusable when this happens, very annoying. > After some research I figured out that version 0.6 uses randr for > changing screen resolution, so I tested how randr (and xrandr) is > working. But it is not working at all. Executing xrandr -q in a > terminal generates: > Xlib: extension RANDR missing on display :20 > > What I have tired: > I added some extra parameters for the x11rdp daemon in the xrdp.ini > file. These are: > +extension RANDR > -extension XINERAMA > -xinerama > -x RANDR > > I (tried) to disable xinerama as I saw at several places on the > Internet that randr and xinerma doesn`t work together. > I can see that the X11rdp server is called with these parameters > whenever a users connects, but still, xrandr gives the "no RANDR > extension" message. > > > Questions: > 1)Is there a way the create a logfile for X11rdp? Just like xorg has > its own? So I could see if the parameters that I passed are processed > correctly? Or is there any other way to find out what is wrong with > the RANDR extension? I now that if I pass a non existing parameter, > there is a message that the parameter is not correct. So I suppose > that the parameters are processed properly, but I want to be sure of > that. > > 2) Do we need these extra parameters at all for RANDR? If it should > work out of the box, what is going on? > > 3)As I stated, this is a virtual machine on a XenServer. XenServer (or > at least the version I am using: 5.6) doesn`t support GUI for SLES > VMs. Which means that you cannot run the `default` X server. Could > this mean that there is some basic support is missing (like kernel > module, or something) for the RANDR extension to work? > > 4) As a workaround I could make all sessions only connect at fixed > resolution (lets say 1024x768). Is there a way to fix this on server > side? I rather do it on the server, than ask all the users to only > connect with the fixed resolution. RandR should be built into the server. Let me take a look and see whats going on. Jay ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
