You are currently browsing comments. If you would like to return to the full story, you can read the full entry here: “X11RDP-o-Matic and RDPsesconfig : Updated to Version 2.5”.
|
|||||
X11RDP-o-Matic and RDPsesconfig : Updated to Version 2.5You are currently browsing comments. If you would like to return to the full story, you can read the full entry here: “X11RDP-o-Matic and RDPsesconfig : Updated to Version 2.5”. 136 comments to X11RDP-o-Matic and RDPsesconfig : Updated to Version 2.5Leave a Reply |
|||||
|
Copyright © 2013 Scarygliders - All Rights Reserved Powered by WordPress & Atahualpa |
|||||
Nice work Kevin.
Your script also works in Lubuntu 12.04 LTS
works in Lubuntu 12.10 :D
thanks to :)
Perfect! Works fine in Lubuntu 12.10. Don't worry, when it takes some time to build x11rdp. =)
It can't find X11rdp source:
# svn co svn://server1.xrdp.org/srv/svn/repos/main/x11rdp_xorg71
svn: E170001: Unable to connect to a repository at URL 'svn://server1.xrdp.org/srv/svn/repos/main/x11rdp_xorg71'
svn: E170001: Could not create SASL context: generic failure: No such file or directory
I’m working on a new release which will use the current source from git – probably a few days away so stay tuned.
Regards.
Any updates on this? I’ve been messing around with it for a bit, but always have problems with the PID files and permissions to config files after updating xrdp and X11rdp.
Slowly but surely working on it.
There’s a beta version but being beta, it’s not absolutely ready for prime time just yet.
It’s very difficult to make generic enough to guarantee working on every distro, and testing takes up an inordinate amount of time, because testing involves running it and waiting for compilations to finish.
It would be nice to have more people involved in improving it as well – I have one additional collaborator (Gustavo) who’s recently done some good stuff on the beta development.
The source is up there on GitHub, so feel free to contribute as well :)
Regards
Thanks for the useful tool. It cCompiled, installed, etc. just fine on 12.04 LTS desktop, runs and I can connect from Win 7 client no problem, but how to make RDP grab the session already logged-in at the console?
I log in with same user creds but get a new/different session with a simlar but slightly different desktop than I get when logging in at the console directly. Any ideas?
Hi Joel,
RDP on linux behaves differently to RDP on Windows.
When logging in over RDP, you get a completely seperate X11 session – you don’t get the console session, which explains why you’re seeing that behaviour.
It’s that way by design.
If you want to be able to to continue work on a console session remotely, start a RDP session at the console and do work within that window. When going away, just close the RDP window – don’t log out of the session. Then remotely connect using the same colour depth (e.g. 16 or 24) and resolution, and user name that you started the RDP session with at the console - you will be reconnected to that running session and can continue working on whatever you left running there.
Hope that helps.
Regards!
Just got a new VPS host and went through multiple reinstalls before settling. This script saved me SOOOOOO much time. Donation has been sent and I will be shouting the existence of this tool from the mountains to anyone who will listen.
Jim, thank you!
I’m almost at the point where I can release v3.0 – which now builds packages so you can build on one machine and then just install the generated packages onto another B)
I’ll probably release it as a BETA and try to get plenty of folks to beta-test it and offer fixes/suggestions before it’s unleashed as a fixed release.
Stay tuned ;)
Hi, I am trying to get this running on Mint 14 with Cinnamon. Kind of an xrdp noob. The script successfully installed xrdp, but I see no difference from the version that the package manager installed previously. After running both scripts, when I connect (using Mac MS rdp client) I get the “Logon to xrdp” dialog where you can choose a Module, username, and password. I cannot get it to connect if I go wit the default “sesman-X11rdp” module. If I change the module to console, i can put in the VNC/Desktop sharing password and it will connect. However, it connects with a slow vnc type connection with no menus. Worse than connecting directly to the desktop sharing with Chicken VNC. Does anyone have xrdp running on Mint? Thanks W
Hi, I’m running Ubuntu 12.04. Installed xrdp from Ubuntu packages and used it with Xvnc, worked like a charm. Built X11rdp, but not xrdp, according to your script and installed. Connects, I can choose the X11rdp session and log in, but then only garbage appears (random green and blue patterns, I can see something happen when I press menu button, but nothing else).
Thought it might be due to the Ubuntu package, so I ran your script with downloading and re-compiling everything. Using your version, I can’t even log in: I receive the login screen, but I can’t log in because my password is not recognized. In authlog I find
Mar 7 17:57:15 CBM8032 XRDP-sesman[3444]: pam_unix(xrdp-sesman:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=XXX
although the password is definitely correct. I wonder about the XRDP in capital letters in that message. The file in pam.d is xrdp-sesman, is that the problem?
Any ideas about one of the problems?
Best wishes, Frank
Hello,
Firstly Awesome Script, I just used it to install xrdp/X11rdp on a Roboard RB110 (specialized SoC robotics board i486 (yes 486) instruction set) running Debian 7 (rc1), took a bit of fiddling but I can login from mountain lion using the MS RDP client. However I have two small issues that hopefully you can help me with. Firstly if I log in as root it behaves the same as logging in locally, but logging in as a normal user fails on the first attempt after a reboot (exits right after the connect message) but after that it stays connected in subsequent attempts. Secondly a normal user login does not start the xfce-panel, I have to start it manually other than that it behaves normally.
Cant see anything obvious in the logs or wrong with permissions. I recreated the user account from scratch and reran the RDPsession config tool; no difference in behavior. Any Thoughts?
Cheers
Ray
I understand you want feedback.
Tried it on LMDE MATE (Linux Mint Debian Edition” and the install script worked, as far as I can tell, flawless.
The RDPsesconfig.sh however did not work, not even after adding “LMDE MATE Edition” to SupportedDistros.txt. In both cases it outputs an empty .xsession file. By adding “mate-session” manually to .xsession it’s up and running.
Thanks a lot for this great script.
Ulf, hi..
I’ve been busy working on other things for the moment, and intend to get back to updating/refreshing RDPSesconfig hopefully this week.
Next week sees my son off school for easter holidays so if I can’t get stuff done this week then there may be more delay over the next 2. However, keep looking in from time to time.
Regards
The script worked like a charm, but I have a problem with RDP clients on my iPad. It seems that when i don’t have a physical mouse to move around the cursor point never moves no matter where i tap. On one client if i activate the “mouse” i am able to interact without a problem. I recognize that the script isn’t the problem, but I am wondering if this is a configuration issue, or if it is something to take up with the x11RDP people.
Ryan, hi
Sounds more like a client issue – perhaps take it up with the x11rdp folks as I see from the development mailing-list that there was some recent work on cursors…
Glad the script worked for you though ;)
Regards
Works on Ubuntu 12.04.2 LTS
Hi Kevin,
your scripts looks pretty convenient for my situation, so ty for this!
Unfortunately, I’ve got some troubles with it:
After executing the scripts X11rdp-o-matic and RDPsesconfig (selecting LXDE as wm), all i see after a (successful) login via rdp (win7 standard client) is a blank screen with a bold ‘X’ as cursor and a small terminal window in the upper right corner. There’s no LXDE desktop or sth similar after all.
Before using executing your script, I was using Xvnc as backend for xrdp, this worked so far. However, performance and copy/paste were an issue.
The installation of xrdp and LXDE was straight forward from the Ubuntu Server 12.04.2 package sources.
After your script, Xvnc behaves exactly the same :/ No LXDE desktop anymore, just a small terminal to see.
Any ideas?
Is it possible to get single sign on working (connecting from Windows7 on a domain)?
Worked like a dream on Ubuntu 12.10.
I use ubuntu server and install a minimal Unity desktop. I have used vnc4server for a long time now, but it stopped working for me on ubuntu 12.10 and 13.04.
So, I tried installing xrdp from the repos, but that wouldn’t work on 13.04 either.
Sadly, I thought I would be stuck using 12.04, and wouldn’t get to test the newer releases of ubuntu. Having a gui for virt-manager, and gparted, etc. is very important to me.
Well, I’m happy to report that X11RDP-o-Matic and RDPsesconfig 2.5 installs and works very well on Ubuntu 13.04 Raring Ringtail.
I didn’t bother to remove the repo xrdp package, but X11RDP-o-Matic didn’t complain and now I have a remote desktop.
The clipboard seems to have a problem, but I will research that later.
However, I do have pulseaudio working on my Win 7 Pro 64bit workstation.
That is very cool.
Thanks!
Version 2.5 tested on Edubuntu 13.04 with gnome classic and it worked fine :)
But the script V3 beta didn’t worked for me. It gave me error starting the xrdp service. The error says that libcommon.so.0 file is missing.
Hi Kevin,
Thanks for this great work. It is really appreciate. I am just about ready to make my donation, but I was wondering if you can help me figure out why neither of my RDP clients (CORD and Microsoft RDP) are able to connect to 12.04.
The connection log says:
xrdp_mm_process_login_response: login successful for display
started connecting
connecting…
connected ok
and then after a few seconds, it closes the connection. I have 4 different users, and all 4 of them behave in this way. They get kicked out, even after it appears to connect. The only user that is able to connect is the `root` user. Any ideas why this might be happening? I’d really appreciate your help. Thx.