-
Notifications
You must be signed in to change notification settings - Fork 284
xrdp connectivity no longer works after apt upgrade
in Ubuntu 18.04.1 LTS
#76
Comments
For reference, I'll my sesman.log, xrdp.log, and .xorgxrdp.10.log: xrdp.log:
xrdp-sesman.log
.xorg.xrdp.10.log
|
apt upgrade
apt upgrade
in Ubuntu 18.04.1 LTS
As a brief update, I built xorg from scratch and the problem has persisted. Xfce4 works in combination with VNC. It seems like it might be a Gnome problem; but nothing in logs jumped out at me in my cursory look. I'm trying to keep this up-to-date in case it helps someone else! |
There's a lot of really great research here @adilwali. Were you ever able to get past it? I'm hoping to be able to spin up VMs for research into various development, but can't get past the poor video performance on these Hyper-V servers. :( |
I'm seeing the same problem. Just finished a very stock OS install by booting from the 18.04.2 ISO (which doesn't seem to be on Quick Create yet), and followed the instructions on the wiki for a manual setup. If I disable "Enhanced Session" on the view menu in Hyper-V client then I can login and connect fine (but obviously not very enhanced an experience). With "Enhanced Session" enabled, after I enter my credentials at the dialog with XOrg selected, it just sits there with a blank blue screen for about 5 mins until I get the error outlined above. I'll try and attach what looks like the relevant log files. Let me know if there is any other way I can help troubleshoot. |
@adilwali @trisco2001 @billti |
Thanks for taking a look. That didn't work for me. I tried from the current state (i.e. having already run it as originally documented), uncommenting that line, rerunning ./install.sh, and rebooting with no difference. I also had a checkpoint on the VM right before doing any xRDP stuff, so I restored to that, modified the script as noted, ran and rebooted - and again got the same behavior. I also tried adding the packages outlined at http://c-nergy.be/blog/?p=13455 , i.e. sudo add-apt-repository ppa:martinx/xrdp-hwe-18.04 ..and then running the ./install.sh script and rebooting. Still no luck :-/ Admittedly I don't know much about how this stuff works, so I'm just throwing crap at the wall and hoping some of it sticks. Let me know if you want the logs again from any of the above attempts. |
Digging through everything I could find again, I noticed the xorgxrdp package wasn't installed, (even though xrdp and xorg were as per the blog). Running So it seems not as simple as that one change to the script, but it is the issue outlined in the blog posts. |
@billti
Maybe it's the best way to solve the problem. It will be better if someone can update the script. |
Just did a clean install of 18.04.2 and not having luck with connection. You mentioned uncomment HWE"= -hwe-18.04" in the script. Can you note location to edit? Sorry new to Ubuntu |
line 14 of the install.sh script. |
Wow, just got my xrdp & enhanced session back for ubuntu 19.10, which was broken by an upgrade from 18.10. |
This worked for me. I had to install the below dependencies as well: Once that's done i executed this: I also changed the HWE parameter to You may modify it in your next commit or at least for my Ubuntu edition (18.04.2). |
I ran into the same issue converting my already manually installed Ubuntu to an xrdp session. I follow your steps and it worked! |
Tank you! It works like a charm! PS: It's not necessary to edit the HWE parameter. |
just in case someone is looking for more info http://c-nergy.be/blog/?p=13390 "Issues with xRDP and Ubuntu 18.04.2 – How to fix it". |
Still not working on 12/22/2019, and with everything( docker minikube ... ) locked in hyper-v ... |
Not working with 18.04.03.... |
Same problem in Archlinux, no clue why xrdp drops connection as soon as it connects... |
Had the same issue with Kali Linux, another Debian derivative. In my case, switching to XFCE4 provided the fasted work-around. I didn't mind, because Gnome wasn't very important to me. Followed these instructions on the Kali FAQ. Also possibly related, a report of this issue to the xrdp team by someone else. |
I've tried the steps from above without the one with HWE parameter. Everything is working just fine!!! Thank you @albadokhon |
this works fine for me. Uncommet HWE couldn't receive any good news. |
Installing |
This repo is being archived, so closing this issue. |
Hey gang! I'm a huge fan of this project, and have been experimenting with coming back to windows after years on Ubuntu.
Context
I'm running Win10 Pro - 17763. I installed the latest Ubuntu 18.04.1 via the "Quick Create" tool. Everything worked perfectly fine for about 2 weeks. Just recently (after the turn of the year), I lost all connectivity to XRDP. The symptoms smell like #49, but I have verified 3x now that autologin is not enabled.
Specifically, the symptoms are as follows:
I'm pretty deep into this VM, with lots of custom-built cpp packages, which is why I haven't just caved and created a new VM. I'm hoping to make the GUI recoverable. It's worth noting that everything else works. (I usually just SSH in, but sometimes I need the GUI to test the GUI I'm working on.)
Stuff I've Tried
I have tried a couple different things to see if I can get things back into a connectable state.
Hypothesis and Open Questions
At this point, I'm down to a couple guesses:
sudo apt upgrade
somewhere along the way. Is the xorgxrdp or xrdp package somehow modified in the Microsoft image? Maybe I shouldn't have updated packages?My Plan Now
I would be very grateful for any guidance you guys might have as to what else I might try. I'm wondering if there is something I don't know (eg, something about the MS Ubuntu build that's different.)
The text was updated successfully, but these errors were encountered: