Package clash with Arch; Enhanced session not working in Arch #127
Comments
|
If I run... ...and reboot, I successfully reach twm using either the xorg or xvnc logins from the xrdp slash screen, so that much is working. |
|
@multipitch this may have relevance: https://bbs.archlinux.org/viewtopic.php?id=258716. In particular response #8 and 9 by usul0184. I can confirm that the fix he suggests also works for me. In short, it appears to be due to a change to a PAM config (which I would not have guessed)? |
Thanks. It still remains the case that linux-vm-tools does not work out of the box for a clean install of arch due to the package conflict mentioned above. If xrdp 0.9.14 causes the login issues seen above, then changing the scripts to use xrdp-git instead of xrdp is just subsituting one breakage for another. Will leave this open. |
|
Link to related discussion on xrdp issue: neutrinolabs/xrdp#1684 |
|
We're currently facing the same problem ( |
|
@fbanning same issue, really frustrated for installation new manjaro 20.2.1 Do you have any solution to workaround this issue>? |
Sadly not, sorry. |
|
Okay, I think I've got this to work. I'm using a freshly installed instance of Manjaro KDE. I've modified the instructions from this Manjaro forum post slightly. For anyone else using Manjaro, you have to change 'systemctl restart lightdm' to 'systemctl restart sddm' when starting the live instance. Manjaro has apparently switched from Light DM to SDDM, since the forum post was written. Continue to follow the instructions, but before running ./makepkg.sh edit it to point to xrdp-git and xorgxrdp-git as shown below. As of 1/26/2021 xrdp-git is version 0.91.14.r24 and xorgxrdp-git is version 0.2.13-1. makepkg.sh:XRDPgit clone https://aur.archlinux.org/xrdp-git.git XORGXRDPgit clone https://aur.archlinux.org/xorgxrdp-git.git The build completed successfully, and I then edited .xinitrc as shown in the forum post. When you open Powershell be sure to run it as an administrator or the Set-VM -VMName command will fail. I was then able to restart my VM and the Xrdp login window appeared and everything appears to be working. |
|
Confirmed that @Isildur981 solution work |
|
@Isildur981 cool, let me try |
|
Quick update, I couldn't get enhanced session to work, it'd keep disconnecting so there may be some other problems unless I missed something |
|
It works on my case, just now. makepkg.sh and .xinitrc |
|
Okay, so kde works fine. XFCE doesn't though, it keeps kicking me out. The xinitrc file does look different from the xfce one so maybe it has something to do with that Edit: figured out what's up with xfce: This is the original .xinitrc file with xfce (Manjaro): In addition to removing --exit with session, the problem is with the get_session function. On further testing, it appears that no DE is detected in the case statement ($1="") and so the wildcard is triggered whenever attempting to use enhanced session login. |
|
This repo is being archived, so closing this issue. |
On a clean install of arch, running ./makepkg.sh gives an error:
I can get rid of the error by replacing xrdp with xrdp-git, e.g.
Once I do this, I cannot get enhanced sessions to work properly from the xrdp splash screen.
I can get a DE to load by running startx but it is slow/laggy and doesn't have the enhanced session features.
This seems to be an issue with DBUS. I've tried both gnome and KDE and both fail to load from the xrdp splash screen using either xorg or xnvc.
Here's my ~/.xinitrc
And my ~/.xserverrc
I could get the xrdp splash screen to load gnome using xvnc by changing the line
exec gnome-sessiontoexec dbus-launch gnome-sessionin ~/.xinitrc but this produces a buggy session - for instance the terminal won't start and the shut down button doesn't work.Here are some logs from an attempt to log in from the xrdp splash screen using xvnc (this method used to always work for me up until a few days ago on my usual VM, but using a clean VM as an example here):
$ journalctl -b 0 _UID=1000 --no-pager > bootlog.txt/var/log/xrdp.log/var/log/xrdp-sesman.logThe text was updated successfully, but these errors were encountered: