GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. The feature "Dynamic resolution update" was introduced in RDP 8. It enables to resize screen resolution on-the-fly.
Previously, we only set the remote resolution during the initial connection. With this change, the resolution is set at connect time and can be updated when the client-side resolution changes while the app is in full screen mode, or when the app transitions from windowed mode to full screen.
The resolution change is quick enough to be practically the same as a local change. Let's bring this to xrdp if possible. I'm still looking for MS documents about dynamic resolution update.
If anyone know where it is, I'd appriciate leting me know. The RandR extension is there and working. AFAIK, xrdp resizes session but it is only connect time, right? What I want to implement is different from it. Yes, I know what you mean. I can't find it in the protocol docs.
Dynamic resolution update is introduced in RDP 8. Windows 8.At the moment, no valid fix or patch is available. However, the xrdp-installer It seems that the xRDP Team has made the previous version xorgxrdp This means that the custom installation will install the xrdp package 0.
So, Use the information on this post only if you are using the xorgxrdp version 0. If you remember, Ubuntu The latest version of t he xrdp-installer script was taking into account this issue and provided the proper fix for it.
Ubuntu The installation script run as expected no errors shown on the screen. However, users are not able to remote desktop to their Ubuntu machines.
It seems that a change in Ubuntu After collecting some more information about this issue, it seems that the problem occurs only when the user performs a custom installation i. Again, the script run perfectly fine.
The user enters the credentials. The connection start you can see a black screen and after a few seconds, the user is simply disconnected …. In order to identify the issue and assess where the problem might be located, we have performed multiple installation of xRDP on a freshly installed Ubuntu We have performed the following actions.
When there is a problem with xRDP and Ubuntu, we always perform a manual installation using the xrdp packages provided by Ubuntu. If the installation is successful, it means that the xRDP packages are valid and are compatible with Ubuntu To perform the manual installation, we have opened a terminal console and issued the following command. The installation process should be completing successfully.
However, if you check for the xorgxrdp package using the command dpkg, we can see that the xorgxrdp package is not installed. Because xorgxrdp pacakge is missing, when a user tries to connect remotely, only a green background will be displayed.
This command will fail and this is expected. Since Ubuntu So again, from your terminal console, issue the following command.
Logging off from the Ubuntu computer, we can perform a remote desktop connection and the process goes through. To ensure that the script is not causing the issue, we have then performed a standard installation of xRDP through the script. So, to perform the custom installation, we have executed the following command.
The script completed successfully as you can see. Logging off from the machine and trying to perform a remote connection works without an issue…. The standard install mode seems to work as expected and the script as well is working as expected.I use Docker for Windows which works amazingly and has it good perf but sometimes I want to test on a full Ubuntu Desktop.
Here's me installing Ubuntu Umuntu ngumuntu ngabantu! To be frank, historically Ubuntu has sucked on Window's Hyper-V. If you wanted to get a higher read: usable resolution it would take a miracle. If you wanted shared clipboards or shared disk drives, well, again, miracle or a ton of manual set up. It's possible but it's not fun. Why can't it be easy? Well, it is. I installed the Windows 10 "Fall Creators Update" - yes the name is stupid.
It's Windows 10 "" - that's and the 9th month. Just type "Winver" from the Start menu. You may have "" from March.How To install XRDP Server Ubuntu 18.04 LTS Bionic Beaver
Go update. Windows 10 includes Hyper-V Quick Create which has this suspiciously short list under "Select an operating system.
Recently Ubuntu You can quickly and easily create an Ubuntu VM from here and it's all handled, downloading, network switch, VM create, etc. I dig it. So click create, start it up Now, here, make sure you click "Require my password to login.
How to Set A Custom Screen Resolution in Ubuntu Desktop
After you've created your VM and got it mostly setup, close the Hyper-V client window. Just X it out. The VM is still running of course.
You'll see a resolution dialog Go crazy! Do be aware that there are issues on 4k display but you can adjust within Ubuntu itself. Click OK and ConnectBased on the feedback we have received through this blog, it seems that there is some changes that has been introduced in Ubuntu This issue will occur if you perform a manual installation or if you use the latest version of Std-Xrdp-Install Ubuntu Apparently, Ubuntu We have performed a manual installation to see what could be the problem.
So, to perform a manual installation, we have opened a terminal console and we have issued the following command. After having performed the installation, we have checked that the xrdp service was running using the following commane.
So far, everything seems to be working as expected. So, we moved to a windows computer, fired up the remote desktop client and as we can see in the screenshot, we are presented with the xrdp login page. After a certain amount of time several minutesyou should see the following error message.
After looking into the logs, it seems that the xorgxrdp component of xRDP is not working as expected. When we have performed the installation of the xRDP package, we have noticed that information displayed in the console mentionning that xorgxrdp package is needed see screenshot below.
So, when performing the xrdp installation, it seems that the xorgxrdp package is not installed anymore. So, moving forward, we have decided to install the xorgxrdp package manually just after installing the xrdp package. So, we have issued the following command in a Terminal console. Issuing this command will not perform the installation as there are some dependencies errors.
The xorgxrdp package cannot be installed because of some missing dependencies. Because we have no xorgxrdp component installed on the computer, it seems logical that when we perform a remote connection, we are never presented with the Ubuntu desktop….
If you are performing a brand new xRDP installation or if you have installed xRDP and you are encountering the issue, you will need to perform the following actions. To fix this issue, you will have to issue the following command just after this one. If you have performed the installation of xRDP packages on Ubuntu After installing the missing dependencies, you will need to manually install the xorgxrdp package in order to restore the xRDP functionality.
When this is done, you will be able to perform your remote connection against your Ubuntu After installing xRDP package using the recipe above or if you have used the custom installation script version 2. When login in locally on the ubuntu machine, you will notice that you have lost keyboard and mouse interaction. Again, as explained above, the fix is quite simple, rune the following command in the terminal session. Note : As long as you do not reboot after installing the xRDP package, you will not have any problems.
After a reboot, you might loose keyboard and mouse input on your system. So, if you have used the Std-Xrdp-Install If you have used the custom installation script install-xrdp However, you might also have the keyboard and mouse problem. Again, you will need to re-install the xserver-xorg-input-all package. It seems that we will need to update the script in order to provide support for Ubuntu Please be patient as it might take us some time before we can upload the new version of the script….
How to Set A Custom Screen Resolution in Ubuntu Desktop
Thanks Griffon, this issue makes me crazy these days… I did try to install xorgxrdp, but when I saw that so many packages will be removed, I was afraid and stopped. Thank you for the feedback.The current implementation of xrdp only functions properly as an rdp-to-vnc gateway - this is a bit odd and confusing, but what you actually must do is have one or more already-running VNC instances listening on the target computer; xrdp listens for incoming RDP connections and "patches them through" to the target machine's VNC servers.
One thing xrdp does not currently do is provide true terminal server functionality; it cannot spawn new VNC server instances under arbitrary usernames by itself, it can only connect to existing VNC server sessions. What xrdp does do is accelerate remote control sessions by performing the slower VNC control session over the localhost interface, and using the much lower-bandwidth RDP protocol over the network between the client and the server.
The following configuration makes both of the major useful configurations of xrdp available simultaneously - a Vino backend controlling the currently logged in user's desktop, and a vncserver backend controlling a simplified, no-compiz, non-dependent-on-local-login session.
The Vino session is handy because it allows you to control whatever's actually going on with the logged in user - so somebody sitting at the keyboard can see what you're doing, and so that you can interact with programs which were started running locally. But it can be a bit painful to control in some cases: any desktop effects you have enabled get faithfully and slowly! Also, if nobody is locally logged in, Vino won't be running and you won't be able to connect to this session at all.
The vncserver "clean session" is handy because it will have no desktop effects, you can specify an arbitrary, smaller desktop resolution if you like, and it doesn't depend on a user being logged in locally in order for you to access it. It's also convenient if you need to get work done on the target machine without disturbing another user who is sitting in front of it!
First, you'll need to install xrdp and if you don't already have it - such as with Ubuntu Netbook Remix vino. If at some point you have installed tightvncserver - likely as a result of trying to follow another xrdp guide somewhere else - I recommend un installing it now.
Otherwise, you'll need to do a dirty workaround later. The "clean session" setup allows you to log in remotely to a session which is completely unconnected and does not rely on the locally logged in user if there even is one.
Log in as the user who will own that session, start a terminal, and start vncserver for the first time. WARNING: if you want to be able to run your "clean session" even when there is a locally logged on user, you'll need to set up the clean session under a different system user. Otherwise, quite a few applications including Firefox! Now, configure Vino so that you can remotely control the currently logged in session.
Obviously, you can go on and specify other sessions in the same format - you might want to relay VNC sessions to OTHER machines on the LAN from your xrdp host yes, that does work so that you don't have to punch different holes in the firewall for each machine on the inside.
Or you might want "clean" sessions available for multiple user accounts. Last step: you'll need to automatically start vncserver, so that it will be available whenever the machine is up. Don't forget, it won't actually be running until you either reboot, or run that command you just appended to rc.
Also note that if you like, you can set up multiple vncservers, possibly running as different users, so that you've got more than one "clean session" to log into - you just have to make sure that you specify a different desktop number the ":1" at the end of the command for each vncserver session, and add blocks in your xrdp.
Now that you've got vino, vncserver, and xrdp installed, configured and running, make sure they work right. First, check to make sure they're listening:.
If you don't, you'll need to figure out what's not running. Assuming you've got all listeners at, andeverything should be good to go - you can connect to the VNC servers directly with a VNC client, or you can use an RDP client to connect to xrdp, which will give you a drop-down menu to select Active Local Login or Clean Session.
If you've installed tightvncserver on your own at some point, you'll either need to uninstall it audo apt-get remove tightvncserver will do the trickOR if for some reason you absolutely must have tightvncserver, you can do a quick-and-dirty workaround: Start gconf-editor as the user your tightvncserver session runs under do not run as root!
Uncheck the "active" checkbox, and close gconf-editor. Kill and restart the tightvncserver, and your keyboard should work fine now. Most likely, you're running twm and not your normal window manager. Comment out any line invoking twm, and add a line if you don't already have one invoking Xsession.Your preferred screen resolution is not available in the Display settings? On my Ubuntu Though there are options to scale for menu, title bars, and text, I prefer X which is available in Ubuntu When it opens, run command:.
It outputs current screen resolution as well as all available solutions. Replace X in my case in the command to your desired screen resolution. Copy the Modeline words with red underline, see previous pictureand run command to add new mode:. A very cool tip! I now can use a notebook with physical x resolution with x :- Thank you! But as Andrew said, it still work if you continue on the steps.
Thank you — not only is your English perfect, your guidance on screen resolution is also clear and precise. Does not work at all. Xrander not found. And it should be forgiving of your spelling and or typing. I typed Xrander and it gave an error! It should work spelled either way. Then, the thing does not say anything about edp-1 so that does not work.
I got this…. OK so then the cvt thing. AND it simply does not work.Installation Simple setup with no user logged into console This is a simple setup without using TLS and certificates. Also, it requires that no person is logged into the console when attempting to connect. With Ubuntu This can happen if TLS is setup incorrectly.
From Windows, use Remote Desktop Connect to connect, and after inputting the username and password at the xrdp login screen one gets a password prompt noting: Authentication Required Authentication is required to create a color profile However, the prompt reappears after inputting the correct password.
This is due to not adding a polkit rule. From Windows, use Remote Desktop Connect to connect, at the xrdp login screen using Session Xorg, after inputting the username and password one gets a blank screen. This can happen due to how one is logged into Ubuntu at the console.
Unfortunately, by default it does not act like Windows, where the console will become locked, and the console session will be redirected to the RDP connection. One will have to log out first. From Windows, use Remote Desktop Connect to connect, at the xrdp login screen using Session Xorg, after inputting the username and password one logs in but no docks exists.
Partners Support Community Ubuntu. Page History Login to edit.