Important note: If you have an issue with o-Matic, please visit the github page and file an issue there, at https://github.com/scarygliders/X11RDP-o-Matic/issues , as I have not been working on o-Matic for a long time now, but it is being actively maintained on Github.
X11RDP-o-Matic Version 3.10 Changes:
- The
--bleeding-edgeswitch has been removed, in favour of a new--branchswitch. - Added new package requirements for compilation
- Generated packages (.deb) will be named according to the chosen branch – see below for further information.
- Previously generated .deb packages will be removed before compilation
- You can now use the
--helpswitch without being root - Script tidy-ups
Branches
There are a number of branches in the neutrinolabs xrdp git repo. Currently there is;
- v0.6
- v0.7
- v0.8
- master
- devel
Branches beginning with “v” are stable, static versions.
The master branch gets continually updated from the devel branch, whenever the xrdp authors think that changes to the devel branch are good enough to be moved into the master branch.
The devel branch is the Bleeding Edge. If you choose to use this branch, things may not work properly, or compile, etc. So, use at your own risk.
By default, o-matic uses the master branch, if you do not specify the branch to use by utilising the --branch <branchname> switch when running o-matic.
e.g.
sudo ./X11rdp-o-matic.sh --justdoit, will use the master branch.
sudo ./X11rdp-o-matic.sh --justdoit --branch v0.8 , will use the stable 0.8 version.
Debian package names
As mentioned in the change summary above, generated .deb package names will depend upon the branch chosen.
When the master branch is used, the resultant .deb package name will be xrdp_0.9.0+master-1_amd64.deb , on a 64-bit version of a Debian-based distribution.
If the devel branch is used, the package name would be xrdp_0.9.0+devel-1_amd64.deb
The “+master” or “+devel” part is now added so that you can distinguish which branch you chose when you invoked o-matic.
If you chose any of the “v” branches – for example, v0.8 – then the package name would be xrdp_0.8.0-1_amd64.deb
The “0.x.0” number for the master and devel branches is obtained from the version number that the xrdp authors have chosen for the new release that they are working on.
Obviously, your resultant debian package name will differ from the examples above, depending upon the CPU architecture your system is running on.
Use the HELP option…
Please do use the --help switch, as it will assist in running o-matic.
The help screen will also retrieve and display a list of the currently available branches.
See the X11RDP-o-Matic Information Page for full details.
X11RDP-o-Matic Version 3.10 Released,Your feedback is valuable and appreciated :)
Works great here on Ubuntu 12.10!
The –withneutrino flag requires you to have compiled and installed neutrinordp before it will build, and this looks like it might conflict with the files provided by the libfreerdp1 package if it’s installed.
Hi Josh, and thanks for the feedback.
Best regards!
This worked on Lubuntu 13.10 with a little tweaking. 1) git wasn’t installed. 2) RDPSession didn’t make a working .xsession file. Shell commands:
sudo apt-get -y install gitgit clone https://github.com/scarygliders/X11RDP-o-Matic.git
cd X11RDP-o-Matic
sudo ./X11rdp-o-matic.sh --justdoit
echo lxsession -s Lubuntu -e LXDE> ~/.xsession
…reboot twice (don’t know why)
BTW, to test this in VirtualBox, you must install virtualbox-guest-x11.
Hi Fearless
Thanks for the feedback – just to note that yes, you need to install git in order to get a hold of o-matic – it’s in the Information page, referenced by the release announcement :) (at the bottom of that page – I put it at the bottom to make sure people read through the page :D )
Best regards!
Kevin, first of all thanks for such a great tool. Maybe you could point me how to make Gnome keyboard layout applet work through XRDP?
hi
my configuration debian 7.4
and this is the error :
/bin/bash: xgettext: command not found
make[2]: *** [sxpm.po] Error 127
make[2]: *** Waiting for unfinished jobs….
make[2]: Leaving directory `/home/X11RDP-o-Matic/xrdp/xorg/X11R7.6/build_dir/libXpm-3.5.9/sxpm’
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/X11RDP-o-Matic/xrdp/xorg/X11R7.6/build_dir/libXpm-3.5.9′
make: *** [all] Error 2
make: Leaving directory `/home/X11RDP-o-Matic/xrdp/xorg/X11R7.6/build_dir/libXpm-3.5.9′
make failed for module libXpm-3.5.9
error building X11rdp
i run as sudo and even as root
Would it be possible to at the end list the packages that were installed during the process so they can be removed afterwards to save space? Some are not really needed afterward (like the development libraries). Maybe save packages the script installed and do an apt-get autoremove .
Hi Faw,
Actually the list of packages are already available to view in the script itself.
Looks for the line which is a comment : “# Declare a list of packages required to download sources/compile them…”
Underneath that, the list of packages required to be installed before compilation is there – you can then pick and choose which ones in that list you no longer need.
I think you raise a good point. It’d be easy enough to include a switch to do that automatically, but I bet there’d be a lot of people who wouldn’t want
a subset of those packages to be removed – and which packages to remove would entirely depend on the particular system of a particular user.
Good question though – but difficult to answer :)
Regards
Hi, thanks for this tool, i’m getting this problem (Debian 7.4 amd64):
root@bob:/X11RDP-o-Matic# sudo ./RDPsesconfig.sh
./RDPsesconfig.sh: line 91: dialog: command not found
./RDPsesconfig.sh: line 192: dialog: command not found
./RDPsesconfig.sh: line 158: ./usernames.tmp: No such file or directory
allusers =
rm: cannot remove `./usernames.tmp’: No such file or directory
./RDPsesconfig.sh: line 267: dialog: command not found
./RDPsesconfig.sh: line 91: dialog: command not found
Hi Bob,
Looks like the dialog package isn’t installed on your system. Which is odd because the X11rdp-o-matic.sh script installs it automatically before it does anything else.
Did you run X11rdp-o-matic.sh first?
Regards
I tried to use the script on Debian 7.4 running on a cubietruck (armhf platform) to build x11rdp.
Unfortunately it stops with this error while configuring xorg-server-1.9.3:
—————————-
checking for DRI… no
configure: error: Package requirements (glproto >= … dri >= …) were not met:
No package ‘dri’ found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables DRI_CFLAGS
and DRI_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
—————————-
I have no idea how to install this “package” and it’s pretty much impossible to
try something, because the script always starts from scratch and it takes like
2-3 hours until it gets to this error (at step 62 of 102 :().
I hope someone has any idea on how to fix this, because x11rdp is my last hope in
getting the shared clipboard working between windows and xrdp (with xvnc+xfce4 it just doesnt work).
James, hi.
Let’s see if we can get to the bottom of this…
Okay. The basics…
X11rdp is a full X server. When you build/compile X11rdp, it’s like building the full Xorg X server.
Building an X server needs header files which are provided by those “-dev” packages you see in the Debian package repositories.
What my script does, is basically perform all this package installing malarky for you, and calls the X11rdp build script, automatically.
So my script is relying on a number of things…
1) Your build system (i.e. the cubietruck) having unrestricted access to the internet.
2) The build system must be running a Debian-bsed distro (yours is)
3) The build system’s access to the Debian-based package system (via apt/dpkg/apt-get)
4) The build system’s repository settings are configured to access the repositories via the internet.
If any of the above are not met, then o-matic – and the subsequent X11rdp build process – will fail.
Also, I know next to nothing about the cubietrack – it looks like it’s another sort of raspberry pi-like gadget (it looks kinda cool actually).
I also don’t know how – if at all – the Debian distro running on that differs from the standard PC Debian distro.
But I hope what I mentioned in this reply will help you.
Let me know how you get on.
Regards
Thanks for the reply. Probably the Debian image I use was the reason for the problem.
I got it working now and I think there is some (indirect) dependency that is not handled by the script.
The script was working fine until it attempted to build xorg-server-1.9.3. The configure part failed, because it could not find a package called “dri”. This is probably something that’s usually just there, but missing in my case. Google results were not really useful (to me) and I could not find which package from the Debian wheezy repositories could be installed to resolve this.
Installing random packages was not really useful anyways because the script failed after like 2 hours and always started from scratch.
So as an alternative I followed this tutorial:
http://scarygliders.net/2011/11/17/x11rdp-ubuntu-11-10-gnome-3-xrdp-customization-new-hotness
At one point I got an #error “GLYPHPADBYTES must be 4”. To fix it, I removed an “#ifdef __arm32__” from the file servermd.h, which apparently was not set by the build environment. Afterwards everything went fine and I got x11rdp running.
Because the versions built by the tutorial were a bit old (x11rdp source file dates are from 2007), I gave the X11RDP-o-Matic 3.10 script another try and around 2-3 hours later it finished successfully :).
So whatever this “DRI” package is, I think it was installed by the build script from the tutorial.
Maybe this information is helpful to someone and maybe it can be used to even improve the script – unfortunately I can’t tell what exactly fixed this, though.
Side note: Clipboard sharing really works with x11rdp, so it was actually the solution to my initial problem :)
Just to let you know, I’m in the process of testing o-matic 3.10 on my Raspberry Pi. Last night I also got the “No package ‘dri’ found” message.
The problem is caused by loads of “-dev” packages not being installed during the initial run of o-matic.
o-matic works like this:
1) Install all packages necessary to compile X11rdp
2) Compile xrdp
3) Make the xrdp package
4) Call the buildx.sh script to build X11rdp
5) Make the X11rdp package
6) Install the packages and start the xrdp service (or don’t install if requested)
o-matic is failing at step 4 both on your cubietruck and on my raspberry pi, because of missing headers required for the X11rdp build.
I spent a few hours last night tracking down what’s not being explicitly installed, manually installing them, and continuing the buildx.sh
build manually (rather than restarting o-matic as that would wipe everything and start from scratch – another thing I want to try to fix).
The buildx.sh process got past the xserver build, but failed much later on due to being out of space (taken up by a whole lot of stuff that’s included in Raspberian by default).
So I’m testing o-matic again by running o-matic on a iSCSI-mounted drive with loads of disk space on my Raspberry Pi. So, so SLOW! ;)
All going well, I will make a new release of o-matic (3.11 is currently living in the devel branch on Github) soon, with everything necessary to build on the RPi – and hopefully meaning on the cubietruck as well.
Regards
Basically, it seems o-matic’s reliance on APT automatically including other -dev packages from its current list of
Hi Kevin, yes, using –> sudo ./X11rdp-o-matic.sh –justdoit
Hmm.
What distribution are you using? I need more information :)
EDIT : scrap that question – I just noticed.
Is your system connected to the internet?
What happens if you try from a terminal :
sudo apt-get install dialog?I just did the following:
add new option:
--cleanuppackages)
CLEANUP_PACKAGES=1 # Remove the packages added during build
echo "Will remove the packages used to build xrdp and x11rdp..."
echo $LINE
;;
at end of install_package():
# check if package was installed ok
if [ $(dpkg-query -W -f='${Status}' $PkgName 2>/dev/null | grep -c "ok installed") -eq 0 ]; then
INSTALLED_PACKAGES="$INSTALLED_PACKAGES $PkgName"
fi
at end of cleanup():
if [ "$CLEANUP_PACKAGES" == "1" ] && [ "$INSTALLED_PACKAGES" != "" ]; then
apt-get autoremove $INSTALLED_PACKAGES
fi
I noticed one thing while looking at the source, it seems –clean only works when –noinstall is selected, is that right?
Faw, greetings!
Thanks for that!
I’m in the process of making a new release (3.11), currently residing in the devel branch at github.
I’ll add your options onto that soon – been kind of busy this week.
I’m having a look at the –clean option as well – that’s been annoying me for a while ;)
Best regards
The lines at end of install_package() have a bug:
# check if package was installed ok
if [ $(dpkg-query -W -f='${Status}' $PkgName 2>/dev/null | grep -c "ok installed") -eq 1 ]; then
INSTALLED_PACKAGES="$INSTALLED_PACKAGES $PkgName"
fi
It would add packages to the cleanup list when they were not installed. Oops. :)
I’ve used it on ubuntu 13.10 and finally xrdp works like it should.
Before i tried this script i had all sorts of strange troubles: tab key did not function normally, icons missing and everytime a new session started instead of the previous.
So thanks a lot for this great installer script!
I used your script on Linux Mint 16 (Petra) Debian Edition. It works!
Although I have to admit my system is not the out-of-the-box configuration. I use XFCE instead of Cinnamon that came packaged (I also have LXDE installed). I also log in using domain user via likewise-open.
I get these errors at the end of o-matic:
./X11RDP-o-Matic/RDPsesconfig.sh: line 263: $homedir/.xsession: ambiguous redirect
Creating .xsession file for in /home/
/home/likewise-open// with entry "startxfce4"..
chown: cannot access '/home/likewise-open///.xsession': No such file or directory
chmod: cannot access '/home/likewise-open///.xsession': No such file or directory
So I created ~/.xsession manually
# After changing this file, you may need to perform the following command to restart the server:
# sudo service xrdp restart
#
startxfce4 # works! (some errors and warnings in ~/.xsession-errors)
#startlxde # works!
#mate-session
#cinnamon
#startkde
#gnome-session
#gnome-fallback
Thanks for the feedback ;)
Yeah, one of these days I need to go give RDPsesconfig some long-needed TLC.
Trying to take into account lots of different system configurations is…. challenging ;)
Regards
I get the same on debian 7.4
I also had the same error “No package ‘dri’ found” on a Beaglebone Black running Debian Wheezy.
apt-get install driconf libgl1-mesa-dev
seems to do the trick. Probably just installing libgl1-mesa-dev might be enough to meet the requirements.
At the moment, the thing is still compiling…
Thanks for providing us with this script!
Kind regards,
Chris
Hi, Many thanks for the utility – I was able to install it on Xubuntu 14.04 using the –justdoit flag and everything went fine.
I also ran the RDPsesconfig.sh after the installation succesfully. After that I reebooted the machine and was trying to connect via the windows RDP client but i just get the message “Your Remote Desktop Services session has ended.”.
The connection log window says
“xrdp_mm_process_login_response:login successful for display 10”
“started connecting”
“connected ok”
Do you have any debugging ideas on how to proceed?
Thanks,
Jalpesh
I have the same problem with fresh installed Ubuntu 14.04LTS and Ubuntu 13.10.
X11RDP compiles and installs with the option –justdoit without any problem and I think it ist right runnign, because the RDP connections is possible without errors. But I get/see only a black screen without any think, so that the only option ist to terminate the running RDP connection.
With ubuntu 12.04LTS all ist right function, but if you update/upgrade it to ubuntu 13.10 or 14.04LTS you get only the a black screen with the RDP connection too.
How do you download? There is no link just a circular reference to alternating pages.
Hi Larold
Wow, really? I don’t think so. In fact I know that’s not the case.
At the bottom of this post you’ve posted this comment in is a link to the Information Page.
You obviously haven’t read the Information Page, as that supplies the Information you need on how to download the latest version.
I place it at the bottom of that page to ensure that users of o-Matic READ the page and KNOW how to use o-Matic. It also roots out the lazy and impatient users who don’t give a flying fig about how much time I’ve put into making the tool, and this web site, and BINGO there you are!
This means you didn’t read that Information Page – which I might add is designed to be read quickly, is understandable, and has been given a suitably high rating by other users.
Thanks for your rating of 1 for this announcement post, by the way – nothing makes me feel better than to be downvoted by someone who obviously doesn’t have the patience to get to know the tool they’re intending to use. I have the warm fuzzies right now knowing that I’m being penalised for your laziness! :D
I’ll reply my self:
Kevin, please have a look at:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281
I think this can help us, to overcome the problem with the problem, but I understud not all what I could or should to do.
Just I have Xubuntu 14.04 running with coLinux at Windows 7 Pro and can use RDP-Connection from Windows to Xubuntu on the same computer:
https://farm3.staticflickr.com/2915/14229119834_9b33bcceea_o.png
It was not simple to install all, but it is running without problems.
Many thanks for X11RDP-o-Matic scripts, which make it easier.
Working for LinuxMint 17 Mate RC x64.
Had to do a ‘touch ~/.Xauthority’ to get mintMenu to display as per
Did not work with LinuxMint 17 Cinnamon RC x64. Only got black screen after login.
Hi Kevin, thank you for these awesome tools!
I’ve tried on Debian Wheezy and runs great.
A little suggestion: could be a list of dependencies added to README.md?
I had to run several times X11rdp-o-matic.sh to get everything compiled because missing packages.
I solved them all… but with a list of dependencies less experienced users can check if their system is ready to start building up.
Thanks again!
OK, I messed up the href link. The link to the mintMenu fix is:
Hi Kevin,
I’ve installed X11rdp with –justdoit on Ubuntu 13.10 running on an ESX-server.
In the .xsession file I’ve added ‘startxfce4’, ‘setxkbmap be’ and ‘numlockx on’ to configure my azerty keyboard and set the numlock default to ON.
When I log on via my Windows machine this works (azerty and numlock), but when I exit the session (not log out) and connect to this session again, the keyboard is changed to qwerty and the numlock is off !
The keyboard settings in the xfce gui is layout Belgian, variant pc105.
I’ve also checked the settings in /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml and keyboards.xml.
Regards, Yvo
Hi Yvo,
This looks like an xrdp problem. I suggest you ask in the xrdp-devel mailinglist; how to do that is mentioned #4 on my FAQ page.
Regards
I’m utilizing Xubuntu 14.04 x64 as a guest OS of Microsoft Hyper-V.
When you utilize X11RDP-o-Matic.sh with the flag ‘–withsound’ do you still have to follow the instructions on this link?
http://www.xrdp.org/index.php?option=com_content&view=article&id=19:xrdp-pulse-sink&catid=2:documents&Itemid=7
The reason I ask, is that I utilized X11RDP-o-Matic.sh –justdoit –withsound to build Xubuntu 14.04 and I sometimes have issues with audio. For example, when I download a video in 720p .MP4 quality and watch it on Parole Media Player or VLC, it can intermittenly have issues with audio. If I try youtube or vimeo and try to stream a video, there is a 3-5 second delay on audio, with the audio sometimes not even functioning at all. Do you know of any tips or advice to fix this?
I’ve not tried the audio stuff with xrdp (except for an article I wrote a long while back on how to tunnel pulseaudio through ssh to get audio with xrdp – back then there was no pulseaudio sink) – and I’ve had no use for the pulseaudio sink since then, so, no, I currently have not enough experience on that side of things to help I’m afraid. I tend to just get my o-matic suite working to actually compile and install xrdp/X11rdp – that itself is time consuming enough ;)
I suspect you’re best asking in the xrdp-devel mailinglist – see my RDP FAQ page (menu at top of my blog, question 4), for details of how to get in touch with the xrdp authors by using that mailing list. They should be able to provide the help you need.
Regards
Thanks for the reply Kevin, I appreciate you making this script, I’ve tried unsuccessfully to port it openSuSE 12.1/12.3, didn’t try too hard. When I get some more time I’ll try harder lol. Thanks for all your articles though, I’ve used your resources for the past 3 years.
Regards
Appreciated!
I need to write more articles – but I’ve been working on something for the last 8 months or so which has taken up a lot of my time – I’ve started to post teasers on the blog ;)
I just have to work out a few more things, and do a lot of typing, and all will be revealed when it’s all good to go. For now it’s teasers up until then ;)
Regards
Hi,
Unfortunately this will not work on a Ubuntu 14.04 server at all. For a working solution goto http://c-nergy.be/blog/?p=5305
Now how do I remove and erase everything that X11RDP-o-Matic installed?
Regards
GCR, hi.
When you say “at all” , do you mean that neither xrdp or X11rdp will compile or install?
I ask this because I just tested o-matic on a fresh install of Ubuntu 14.04 LTS Server, and o-matic works as advertised, in that it compiled both Xrdp and X11rdp.
What I did have problems with, was when using RDPsesconfig to select the Xfce4 desktop. In this case, it installed some but not all of the Xfce4 packages. I had to manually install xfce4-session. After that I could log into the server and get a fully working Xfce4 desktop.
I read that – it’s similar to one or two articles I wrote from about 2 years ago up till now – it works, but in a very different way, in that 1) He uses the distro-provided Xrdp package, and 2) Because of that, you have to use the VNC back-end.
X11RDP-o-Matic is for people who want to have the X11rdp back-end, and/or the latest version of Xrdp. The version of Xrdp supplied by 14.04 LTS is still v0.6.0 … this, frankly, is ancient – the latest stable release of xrdp is currently v0.8, and v0.9 is being worked on right now :)
So, o-matic did in fact work and it installed stuff?
Removing the o-matic-installed xrdp is as simple as using the
command…
apt-get remove --purge xrdpapt-get remove --purge x11rdpRegards,
Kevin.
I just realised I tried my development version (3.11) of o-matic.
I’ll try v3.10 too and report back.
Yep, v3.10 of o-matic worked fine as well.
It works on Xubuntu 14.04 x64 with very little issues, by little issues, I have an issue with the PulseAudio xrdp sink/source, but no issues with xrdp and x11rdp. I also made sure to update all my packages on that distro. I’m actually using a VM this moment with Xubuntu 14.04 and X11RDP-o-matic utilized to build xrdp and x11rdp multiple times on that particular VM.
Thanks for the feedback – nice to have my own biased observations confirmed ;)
The pulseaudio stuff is still a bit of a work in progress I think with the xrdp/x11rdp author, who is trying to sort a few issues out with the pulseaudio authors.
Regards
Hello Kevin,
I get the new log in but when I log in I get a terminal prompt… Any sugestions? THank you in advamced…
Also… What does the –withsound exactly do? Does it really push sound through? Can wait to test…. Thank you again.
Hi Jonathan,
The
--withsimplesoundswitch provides the xrdp source ./configure script with the “--enable-simplesound” switch, which you’d do manually. There are other switches in o-matic which do similar things (--withdebugfor example )Got it… Had not been able to solve the terminal prompt once I log in. Please any suggestions….
Have you configured a desktop session?
Do you have a .xsession file in your home directory, and if so, what’s in that?
Regards
Yeup I have run the post RDPsesconfig.sh and the file has gnome-session –session=gnome-fallback. Have tried another ubunto 12.04 and same result.
Bump… I have compiled 2 times and installed the repository xrdp to no avail. I still keep getting a terminal prompt at after credentials at login. Pleasse help. Done the .xsession file thing too. Plelase help/
Hi Jonathan,
Sorry about the delay in reply – I’ve been terribly busy over the weekend and beyond.
Let me have a look to see what’s going on with this – I’ll run a VM and test on the same distro and get back to you, bear with me.
Regards
Kevin
Jonathan,
Try completely removing the .xsession file then logging in.
I just ran O-Matic on a fresh Linux Mint 16 MATE 64bit installation, and tried logging in without running RDPsesconfig, and got straight into a MATE desktop.
By the way, I ran my devel version of o-matic, give that a try;
Regards
I am having the same problem that was reported by domenico early in this comments thread:
/bin/bash: xgettext: command not found
make[2]: *** [sxpm.po] Error 127
make[2]: Leaving directory `/root/X11RDP-o-Matic/xrdp/xorg/X11R7.6/build_dir/libXpm-3.5.9/sxpm’
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/X11RDP-o-Matic/xrdp/xorg/X11R7.6/build_dir/libXpm-3.5.9′
make: *** [all] Error 2
make: Leaving directory `/root/X11RDP-o-Matic/xrdp/xorg/X11R7.6/build_dir/libXpm-3.5.9′
make failed for module libXpm-3.5.9
I have tried twice, both of which failed. The first time without specifying –branch, the second time specifying v0.8 (as per the Information page):
./X11rdp-o-matic.sh –justdoit –branch v0.8
OS is Debian 7.5
Any thoughts/suggestions gratefully received.
Hi David,
I’ve looked at what package supplied xgettext;
It’s probably the case that in previous versions of Debian, xgettext used to be supplied in another X-related package that was automatically installed by O-Matic as part of the group of package dependencies, and was probably moved to this other package – either that, or, the gettext package was previously marked as a dependency for one of the auto-installed packages, but is no longer so – in which case, what I’ll do is add gettext to the package requirements… in fact I just did so to the devel branch of o-matic – how’s that for service ;)
I wonder if you could try out the devel version for me by cloning it from the github repo?
That’s got the fix in it for gettext, as well as an improved method of package creation for xrdp, amongst other enhancements.
Please let me know how you get on.
Regards
Hi Kevin,
Many thanks for having a look at this for me – fantastic service I have to say!
I kicked it off again this morning but it has now served me up a new exception:
*** processing module intltool-0.41.1 (65 of 102) *** x
x x
x downloading file http://server1.xrdp.org/xrdp/X11R7.6/intltool-0.41.1.tar. x
x executing ./configure –prefix=/opt/X11rdp x
x checking for a BSD-compatible install… /usr/bin/install -c x
x checking whether build environment is sane… yes x
x checking for a thread-safe mkdir -p… /bin/mkdir -p x
x checking for gawk… no x
x checking for mawk… mawk x
x checking whether make sets $(MAKE)… yes x
x checking for perl… /usr/bin/perl x
x checking for perl >= 5.8.1… 5.14.2 x
x checking for XML::Parser… configure: error: XML::Parser perl module is r x
x configuration failed for module intltool-0.41.1 x
m
Perl looks OK, so I’m not sure what the error is trying to tell me.
Hi David,
Downloading a Debian Wheezy ISO as I type this.
I’ll install it in a VM in the morning and unleash o-matic devel on it.
But it’s now 0122hrs here in Scotland and I want some sleep ;)
I want to get to the bottom of these errors and fix them for the devl-to-3.11 official release, which is shaping up nicely (apart from this pesky Debian 7.5.
Give me some time for sleep, breakfast, Debian installation, and o-matic testing, and I’ll get back to you some time tomorrow.
G’night ;)
Hi again Kevin,
I understand you’re keen to get a clean release, and thank you for following this up, but please don’t overdo things on my account!
I can confirm I have Debian 7.5 installed:
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.5 (wheezy)
Release: 7.5
Codename: wheezy
Hi David,
No worries about overdoing things – it’s not just about you ;) , I always like to check how any changes I make affect how things run on older distros (Yes even Debian stable is old to me as I use Sid [ I like living dangerously ;) ] ). Already one or two things cropped up, such as dh_make (the new way I create an xrdp package in the devel version of o-matic) having a “–yes” option in current versions, but stops if it sees that option which is unrecognised in older versions.
So when people such as yourself pop up with Things Not Going Right, that gives me an excuse to try o-matic out in that version.
Anyway back to what you reported – I installed Wheezy 7.5 in a VM and after installing the guest additions and making sure it was up to date with the latest packages, downloaded my devel branch of o-matic and ran it.
It successfully completed compiling X11rdp and xrdp, created the packages, installed them, and I’m sitting here looking at an Xfce4 desktop in an RDP session.
So I can’t explain why it’s not working on your Wheezy 7.5 system.
I noticed all those “x”‘s at each end of your pasted output – it looks like you ran o-matic in interactive mode at that point?
Can you do the following for me….
1) Remove the X11RDP-o-Matic directory altogether – you may have to use sudo to do this as there might be files and directories underneath that which were written as root.
2) Download X11RDP-o-Matic devel
3) Run o-Matic in recommended non-interactive mode
4) Use RDPsesconfig to configure an Xfce4 desktop environment for your user
Tell me how you got on. It should work. If it’s not working, then perhaps something’s not right with your Debian installation?
Regards
how about .9? Can I upgrade to it via rdp-0-matic?
Daniel, hi
.9 of what? xrdp? as in v0.9? yes – just use the –justdoit switch and o-matic uses the master branch, which is the v0.9 Work In Progress version at this time.
Regards
Hi Kevin,
Many thanks again for looking into this.
The Debian install is a fresh one, but it appears that although perl was installed, it was a very minimal installation and was missing the XML parser. After installing the complete perl package the compilation was able to proceed to package 67 where it threw another exception.
It now appears that some X Windows libraries are required – in particular it fails when it cannot find ucs2any:
*** processing module font-adobe-75dpi-1.0.3 (67 of 102) ***
…
checking for ucs2any… no
configure: error: ucs2any is required to build font-adobe-75dpi.
configuration failed for module font-adobe-75dpi-1.0.3
error building X11rdp
One of our IT people is looking into this, and I hope to be able to retry later today. Most of my problems appear to be with missing dependencies that weren’t installed with the OS. I will let you know as soon as I have succeeded in building xrdp.
Hi David and I do appreciate the feedback. :)
That’s odd that dependencies are missing… the fresh WHeezy installation I tested o-matic on yesterday got all the dependencies downloaded – is your installation configured to receive Debian packages from the Debian repos? Oh also, is that system behind a proxy? Can’t remember if I mentioned this, but I remember someone else had problems downloading source tarballs because they had to set HTTP_PROXY and similar environment variables. His problem as I recall was that he needed to set both “http_proxy” and “HTTP_PROXY” as some utilities use the small-letter version and others the capital-letter versions. I’m not saying that is your problem, it’s just that I’m finding it odd that all the dependencies aren’t being installed on your Wheezy system when they are on mine ;)
Anyway, the proxy stuff is interesting and more info can be found here : https://wiki.archlinux.org/index.php/Proxy_settings
Let me know if you get to the root of your problem, especially if it’s an o-matic thing, then I can fix that ;)
Regards
Oh also, ucs2any is provided by the xfonts-utils package. Again, I don’t (yet) understand why your Wheezy installation doesn’t have that or why (yet) it wouldn’t install it whilst o-matic was installing the list of package dependencies at the start of its run.
This installation of Wheezy – it wasn’t a minimal install was it? That might have consequences, come to think of it, as if it was a bare bones installation with no desktop packages yet, then that might have an impact on what packages get installed when o-matic is first run. I’m going to test that right now in fact.
Good morning (NZ-time) Kevin,
Many thanks for the detailed replies – they are sure helping me understand what is going on in the background!
Good news is that the xrdp install completed after installing xfonts-utils. As per your instructions, I then ran the config script which claimed to have succeeded. Finally rebooted the machine and attempted to connect from my laptop using MSTSC. So far with no joy.
I am on the train at the moment, but will meet with the IT guys when I get to the office and see if they have any ideas.
In answer to your question regards how minimal the Wheezy install was – I am afraid I don’t know precisely, other than that it was described as ‘minimal’. I’ll also see if I can get a bit more detail on just how ‘minimal’!
Again, thanks for all your help.
David, good evening from Scotland ;)
Which desktop did you select from RDPsesconfig?
Try removing that .xsession file that RDPsesconfig.sh created in that user’s home directory, then try logging in again via RDP – it might work.
RDPsesconfig.sh is getting long in the tooth and is difficult and time consuming to maintain, because different debian-based distros can have different ways of starting a desktop session, and even the same distribution can differ in the ways it starts a session, between versions.
Creating a .xsession file will override the startwm.sh script in /etc/xrdp – it’s really meant to customize individual user’s choice of desktop when they log in via RDP – this can come in handy for example on the latest distros where the default desktop system is Gnome 3 or Unity on Ubuntu, which do not play well with xrdp and hence a different desktop session is required.
I’m currently thinking of rewriting RDPsesconfig in Python, with a GUI. But that won’t happen till I get the time (which this week has been taken up mainly by issues with X11RDP-o-Matic.sh – it’s been a right ol’ pain).
Regards
Hi again Kevin,
Still unable to get an RDP session started from a Windows machine. I have checked through all the documentation (.txt and .md) that I could find in the X11RDP-o-Matic directory and searched for any scripts that might start an xrdp service to no avail. I have re-run RDPsesconfig (as root).
For the re-run, I selected the Xfce desktop. Instead of all users (which was what I did first time), I selected just one. The script reported success when it completed and I noted fleetingly that it was creating a .xsession file in /home/[user]. However, when I check, there is no such file.
I’m sure there should be a service running, but there isn’t (ps -ef | grep xrdp returns nothing). And the directory /etc/xrdp does not exist.
BTW – I checked, and the Debian install was ‘minimal’ in the sense that it was just the defaults.
I must still be doing something stupid!
Hi David
It’s kind of frustrating for me too, as I’d really need to be actively on your system to see what the heck is going on there.
At the moment, I got nuthin’ , as they say, somewhere…
Regards
Hi Kevin,
I am back to looking into this again after being otherwise occupied for a couple of days. I would love to be able to enable access for you, but the system is purely internal to our organisation.
I have run the RDPsesconfig script again for a single user and find that it has correctly created the .xsession file in the specified users home directory. The .xsession file contains a single line: startxfce4.
But I think the problem is more fundamental than that. The -o-matic script appears to have built everything correctly to /opt/X11rdp/. However there is no /etc/xrdp/ directory (which you say should contain a script named startwm.sh for /home/[user]/.xsession to override).
For comparison, I have xrdp running correctly on a Raspberry Pi at home and have compared a few things. On the Pi there is an /etc/xrdp/ directory, and there are a number of processes associated with xrdp:
xrdp 2000 1 0 May22 ? 00:05:27 /usr/sbin/xrdp
root 2005 1 0 May22 ? 00:00:02 /usr/sbin/xrdp-sesman
pi 4959 4944 0 00:41 pts/0 00:00:00 grep –color=auto xrdp
There is definitely something not wired up correctly on my office machine.
I’d be really grateful if you could tell me which directories should be created by the build process and what the installation should do by way of creating an /etc/xrdp/ directory and adding a start script to /etc/init.d.
Thank you again in advance.
David, hi
Okay here’s the thing…
After running o-matic, you should have two Debian packages which were created upon successful compilation. They should be located in their own subdirectories, under a directory called “packages”, in the X11RDP-o-Matic directory.
One package should be called
x11rdp_[version]_[arch].deb– this is the X11rdp back-end X server, and all the stuff it has is under /opt/X11rdp.The other package should be called
xrdp_[version]_[arch].deb– this is the xrdp front-end. That one when installed, should have the files in /etc/xrdp you speak of, plus other binaries and files in other system locations.If you’re not seeing anything in /etc/xrdp, then Something Is Wrong. It looks like either the compilation of xrdp (the front-end stuff) failed, or the building of the xrdp package after compilation failed – either way, you only have one half of the equation; it looks like only X11rdp compiled.
If there is no
xrdp.deb in an xrdp subdirectory, then one of the above has occurred.If that’s the case, can you do this for me… can you git clone a fresh copy of X11RDP-o-Matic (really wish I’d chosen a better name for that but that’s what I get for my sense of humour), make sure it’s the devel branch of o-matic.
Then bring up a terminal application, make sure it has infinite scroll-lines (because I want to see all of the output).
Then type
sudo ./X11RDP-o-Matic.sh --justdoit --nox11rdp, and let it do it’s thing.The
--nox11rdpswitch will tell o-matic to just build xrdp.Then if you could please copy and paste the entire output to pastebin.com and give me a link to it.
Hi Kevin.
Can you help me resolve my problem that is BLACK SCREEN after login to Ubuntu 14.04 from Windows Remote Desktop.
I’ve done everything exactly on Ubuntu 14.04 Server, installed xfce4 (xubuntu-desktop), X11DRP-o-matic, compile, make session for xfce4.
Everything with no problem at all but after login from Windows remote desktop I got BLACK SCREEN.
What else should I do?
Alec,
Try
sudo apt-get install xfce4-sessionThen edit the file called
.xsessionin your user’s home directory, changestartxfce4, to sayxfce4-sessionThen reboot your Ubuntu system, then try logging in via RDP again.
Regards
Thank you! Thank you! I have been banging my head on this for days. Just used your –justdoit method with no tweaking and it worked. Linux Mint 15 KDE. Now trying it on Linux Mint 17 xfce. Thanks!
Good morning Kevin,
Thank you once again for following through.
I have done as you instructed, and although success is reported right at the end of the script output, there are indeed errors a bit earlier. I have pasted the entire session to pastebin.com. The reference is p6dXfLJE.
Please ignore all the find ‘permissions’ errors early in the trace – I was just checking for the .deb files – which weren’t there.
Best Regards
David,
I can see what the problem is straight away.
Your Debian installation does not appear to be set up with the Debian repositories.
Fire your sysadmin ;)
Also, have you read the Information Page? http://scarygliders.net/x11rdp-o-matic-information/
Especially the section entitled “System Requirements”?
It looks awfully like 2 or 3 of those requirements are not being met.
Regards
It also worked on Linux Mint 17 xfce with no tweaking. Thanks again!
Thanks for the feedback :)
Regards
Hi Kevin,
With all your help I think I finally got there.
I took your advice, sacked the sysadmin and took over figuring out what was going on myself ;)
The key to success in the end was the /etc/sources.list file which was configured to only look at the cdrom (presumably from where the Debian install was originally done). I don’t know if that’s a default, but once I had commented that line out and added all the wheezy ones (deb http://http.debian.net/debian wheezy main etc…).
My sincerest apologies for hassling you over this, and my sincerest thanks for all your help.
Hi David
Glad that got sorted out in the end – another satisfied customer ;)
Regards
Can you tell me why it can not work with Cyrillic clipboard on Debian 7? Or tell me who to turn to, you can.
Try asking on the xrdp-devel mailing list. A link to that is shown on my FAQ page.
Regards
It also worked on Linux Mint 17 KDE with no tweaking. Only had to install git. Thanks again!
No, thank YOU for taking the time to provide the feedback – much appreciated!
Regards
What is the reason for including Python in the process instead of installing it with apt-get?
Absolutely no idea… it’s the xrdp-supplied buildx.sh which o-matic calls, which includes that. I have recently tried taking the Python download/compilation out and xrdp builds with no problems. Perhaps the next release of o-matic will include an altered version of buildx.sh with some of the stuff removed – I’m still experimenting with it when I get the spare time. Fonts, for example, could also be supplied by the distribution repo as well.
Cool, thanks for the reply. BTW on debian-armel I had to manually apt-get install mesa-common-dev – without it the build script failed at one of the configure steps with missing DRI/glproto.
This rocks. Works perfectly on Mint.
I tried the build script on a new Xubuntu 14.04 (xfce4) that I was previously using X11VNC and xrdp.
It kind of worked in that I can connect and get the lightdm greeter, but none of the fonts on the greeter display, the dropdown and whatever you type is blank. If I log in blindly it seems to be trying to work, but has some error (which I can’t see since the fonts don’t work) and clicking on OK returns to the greeter.
Any idea what is up or missing with the fonts?
I’m trying to get this to work with debian jessie running on rackspace. The build worked and I’ve backed up the deb files so any new instances I create I can just copy the deb files to. BUT I’ve got a problem of it not working at the moment. The service is running and the port 3389 is listening but when I try to connect I just get a white screen.
I’ve installed xfce4 and the xrdp from the repo and that works fine. I then remove the repo xrdp and install the debs that have been created and I’m back to the white screen.
Any ideas?
The deb files created were;
x11rdp_0.9.0+master-1_amd64.deb and xrdp_0.9.0+master-1_amd64.deb
Also after installing the deb files how do I use RDPsesconfig.sh?
I’ve just tried this again from my windows laptop (win7) and it works! I tried from my Mac and Android using Microsoft RDP and they both don’t work for some reason (white screen on Mac and Android just fails on negotiating).
If I install this on an blank Debian box again, can you confirm if this is how I should set it up please?
apt-get install xfce4 xfce4-goodies
Copy the deb files to the new Debian box
dpkg -i x11rdp_0.9.0+master-1_amd64.de
dpkg -i xrdp_0.9.0+master-1_amd64.deb
echo startxfce4 >> ~/.xsession
Or should I be doing it a different way?
Damian, hi
Odd about that white screen – have you tried setting a different colour depth in your RDP client?
Also, installing the packages the way you suggest should work fine – as long as the system architecture is the same on the target system (amd64)
Regards
Thanks for the reply – I’ll try the colour depth on my mac when I get home. Just looked for it on Android and that doesn’t appear to be a setting.
What does the RDPsesconfig.sh do? If I install the deb files and it is missing (I searched / and never found it) what do I need to do? Does it create the .xsession file? Is there anything else that should be in the file other than startxfce4?
Thanks,
Damian
Yes, basically RDPsesconfig sets up the .xsession file – and installs the chosen desktop’s packages – this information is all in the Information Page y’know ;)
Regards
Hi Again,
Been doing loads of testing and thought I’d let you know the outcome. Compiled both master and devel branch and installed on Debian Jessie test machines running xfce4, results;
Master; windows 7 mstsc works
mac os x 10.10 negotiating issues
Android negotiating issues
Devel; windows 7 mstsc works
mac os x 10.10 username and password filled in = black screen
username and no password filled in = black screen
no username no password = logon box presented and works!
Android still issues due to the app asking for username and password before connecting.
I found a thread somewhere (which I can’t find now) that you had fixed something in devel for mac handling negotiation.
Awesome work! I’ve now got my devel debs backed up so that my rackspace debian servers only need the debs copying and installing.
Thanks for all your effort on this Kevin and hopefully that last little login bugs will get fixed soon.
Thanks,
Damian
Hi Damian, thanks for the feedback.
I think you’re under the impression that I wrote xrdp/x11rdp? I didn’t – o-matic merely downloads the source code, installs the necessary packages needed to compile it, compiles it, and creates packages ;)
Regards
Kevin
I installed it on Mint 17 Mate and it works perfectly. Thanks for the great job.
I have one question.
What is the “xrdp_client” folderr in every user’s home folder ?
It shows up in the Desktop as mounted. I cannot unmount it and it seems it’s alwyas empty.
What’s the purpose of this folder ?
Hi, and thanks ;)
The xrdp_client directory is used for drive redirection, like what you can achieve with RDP on Microsoft OS’s
So I gather then that you’d be able to transfer files from your client machine to your home directory on the RDP target machine.
See http://www.xrdp.org/index.php?option=com_content&view=article&id=17:drive-redirection&catid=2:documents&Itemid=7
Regards
Thanks for the quick reply. Now I understand what this is for. Still, I don’t understand, however, how to use it. Your suggested link doesn’t seem to have much info either.
Let me clarify my question in a little more detail.
1. How would I mount my C: drive (or a folder therein) to xrdp_client folder ? I don’t see any option in M$’s remote desktop connection program to do this.
2. If I’m not interested in file sharing between host window pc and remote linux machine, can I simply delete this folder ? (it has root privileges and asking before actually attempting to remove it. ^^)
3. I’m more interested in clipboard sharing than file sharing. For example, is there a way to copy an html address and paste it to remote linux machine’s mozilla address line ?
Sorry for asking many questions.
cheere.
Those are all very good questions, and to be honest I don’t know the answers :)
You’re better off asking the xrdp authors – how to contact them (via the mailing list) is in the RDP FAQ page linked at the top of my blog.
Regards
#Linux Mint 17 Cinnamon(Ubuntu 14.04)
#After running
sudo ./X11rdp-o-matic.sh –justdoit
sudo ./RDPsesconfig.sh
#XRDP would crash after connecting. Even though RDPsesconfig.sh downloaded XFCE something wasn’t correct(perhaps in .xsession). so I ran the following
#commands and everything worked fine
sudo apt-get install mint-meta-xfce
sudo reboot
Also had a question about the mouse pointer. When I just install tightvncserver and xrdp my mouse pointer is normal when I login. When I use your method the mouse pointer has a big black square around it. Is anyone else having this problem? If so how did you fix it.
Also I donated to you for this awesomeness
Thank you :)
The black square means your RDP client doesn’t support the “new” mouse cursor method the newer xrdp’s use.
You can fix that by placing “new_cursors=no” in the [Globals] section of your xrdp.ini file. Restart xrdp, log back in again, and that should be fixed.
Regards
Hello Kevin
I have just installed it on Ubuntu 14.04 but I the only thing I get is the black screen and cursor. This is probably a small issue but I am not being able to figure this one out.
Could you give me a hand?
Best
Isaac
Hiya,
You haven’t told me which xrdp branch you’ve selected, so I’ll assume it’s the default “master” branch.
Whatever the version of xrdp you’re running anyway, on Ubuntu, if you haven’t ran RDPSesconfig.sh, then
the system will try to run the default Unity desktop when you log in over RDP. Unity doesn’t work with
the x11rdp back-end X server. Nor does the more recent Gnome desktop. I suggest you try selecting Xfce4,
or even KDE works fine.
Hope this helps.
Rgds
I have actually seen this with 14.04 as well. Ubuntu is not reading .xsession correctly for some reason. I found that if i ssh in and then export DISPLAY=:10 and then run xfce4 the black window is then replaced with a working session. I have tried many combinations in the .xsession file to no avail.
Hmmm…
Don’t you just love it when behaviour changes between distros?
I’ll install 14.04 in a VM and have a look – there’s always a solution somewhere. Always! ;)