secana / enhancedsessionmode Goto Github PK

I have followed the steps and installed xrdp on my fedora 29 workstation in hyper v.
Finally enabled the ESM via powershell for my above virtual machine.

Now i get the ESM popup to choose resolution but after that throws up error
"Video remoting was disconnected"

Can you help.

The command at line 25: rpmbuild -bb ~/rpmbuild/SPECS/xrdp.spec ends with the message:

+ --with-socketdir=/run/xrdp
/var/tmp/rpm-tmp.Dl6sJK: line 55: --with-socketdir=/run/xrdp: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.Dl6sJK (%build)

As a result, the package build fails.

Attached the full console output.
install_esm_centos7.sh_output.txt

I get to the xrdp screen and it says xvnc I type in my credential that I know are correct and it says login failed invalid credentials. I am trying to set this up on fedora 35

Hi

Thanks for making this script. I noticed that the fedora31 script works fine on Fedora 32.

1. Install fedora 34 in hyper-v.
2. Run the Enhanced session mode script.
3. The connection works without SO update.
4. Run and install the last SO update for fedora 34.
5. Restart the virtual machine.
6. I can't connect anymore in enhanced session. The enhanced session is enable but login not found, always fail.

If there is a way to get this working with 34 already that I don't know about that works too! I don't mind so long as it's not too complex a process to follow.

Hello,
I found out that in F30 there is no Xwrapper.conf file, it should be named Xwrapper.config
(see man Xorg.wrap). I sunk half a day on a thing this simple.

Less simple: see neutrinolabs/xrdp#1403
I rolled back https://src.fedoraproject.org/rpms/xrdp to the last commit before 0.9.11 and built it with fedpkg local.
I also switched the build phase inside a container with podman.

Hi,
I am following installation scripts on a Fedora29 on Win10 and everything goes well till I
got stuck when connecting to the host after rebooting. It repeatly pop up the reconnect window prompts:
" could not connect to the virtual machine. try reconnet again. If the problem persists, contack your
system administrator."

I have tried just changing install script from the line
dnf download --source xrdp-0.9.9-2.fc30
to dnf download --source xrdp-0.9.9-2.fc31

But it says package not found.
I also tried to use the old rpm (for Fedora 30) that was built when I had Fedora 30,
and install it on Fedora 31, but it errors out with a conflict that xrdp-selinux is not of the expected version
(that's because when the source RPM package from which xrdp was built, had an older xrdp-selinux in the package spec).

So at the moment, my recommendation is not to upgrade for Fedora 31, as the Hyper-V enabled xrdp would not work (it also had to be explicitly de-installed prior to Fedora 30 to 31 upgrade due to broken dependency on xrdp-selinux)

I do not know how to fix at the moment, so may be @secana could suggest what to look for.
If I find how to get it to work, will post here.

The current xrdp packages in EPEL 7 and EPEL 8 have been built using the VSOCK option.

See https://bugzilla.redhat.com/show_bug.cgi?id=1787953

xrdp 0.9.11 introduced a bug which breaks vsock, preventing the daemon to start (see neutrinolabs/xrdp#1403 ). Apparently it's Microsoft's lack of pull-request

As a workaround, we should force the download of the sources of the previous available version, which for F30 is xrdp-0.9.9-2.fc30 (unfortunately at the time of writing version 0.9.10 is not available).

P.S.
Also the f30 script should be executable

I had tried to bake this in some time ago but I utterly failed in my attempt. I imagine it is fairly trivial to add based on this, https://github.com/neutrinolabs/pulseaudio-module-xrdp/wiki/README but alas I could not get it to go. This would fill a substantial gap in my opinion to push even further enhanced usage. I will start poking at this again myself.