Windows to Mint PC RDP Issues

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Windows2LinuxNoob
Level 2
Level 2
Posts: 81
Joined: Mon Mar 23, 2020 11:43 pm

Windows to Mint PC RDP Issues

Post by Windows2LinuxNoob »

Hi, I installed xrdp and xorgxrdp on my Linux Mint PC and I used to be able to to log into this machine from my Windows machine via RDP. I was having issues where the Mint PC was pegging the processors to minimum 80% usage, and could hear fans blaring loud of course. So I tried this:

Code: Select all

echo env SESSION_MANAGER -u DBUS_SESSION_BUS_ADDRESS cinnamon-session>~/.xsession
And this is where everything broke. When I attempt to RDP in the Mint PC, I get to login screen, but after I enter in credentials and ENTER, Windows' RDP session immediately closes... Not entirely sure if this is the issue, but this .xsession file is either empty or has this env var unsetting going on and seems to have no effect. I reinstalled xrdp and xordxrdp - no dice.

I even went back in time via Timeshift and to no avail, this Mint PC system cannot be remoted into anymore no matter what I have tried... Hit a brick wall here...

I didn't change anything in the Windows RDP file used to connect to my Mint PC, so couldn't imagine what would be the issue with this if there is any.

Here's .xsession-errors file:

Code: Select all

dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/chris/.Xauthority
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
dbus-update-activation-environment: setting LANGUAGE=en_US
dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting PWD=/home/chris
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon
dbus-update-activation-environment: setting LOGNAME=chris
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting XAUTHORITY=/home/chris/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/chris
dbus-update-activation-environment: setting GDM_LANG=en_US
dbus-update-activation-environment: setting HOME=/home/chris
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LANG=en_US.UTF-8
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting USER=chris
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting GTK3_MODULES=xapp-gtk3-module
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/chris/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
dbus-update-activation-environment: setting PATH=/home/chris/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting GDMSESSION=cinnamon
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
Cjs-Message: 08:53:15.048: Profiler is disabled. Not setting up signals.
Clutter-Message: 08:53:15.096: Sync method: PRESENTATION TIME
cinnamon-session[3088]: WARNING: t+1.41271s: Failed to start app: Unable to start application: Failed to execute child process “solaar” (No such file or directory)
qt5ct: using qt5ct plugin
Cjs-Message: 08:53:15.244: JS LOG: About to start Cinnamon
Tracker-Message: 08:53:15.276: Set scheduler policy to SCHED_IDLE
Tracker-Message: 08:53:15.276: Setting priority nice level to 19
Cjs-Message: 08:53:15.328: JS LOG: [LookingGlass/info] Cinnamon.AppSystem.get_default() started in 81 ms
Tracker-Message: 08:53:15.345: Set scheduler policy to SCHED_IDLE
Tracker-Message: 08:53:15.345: Setting priority nice level to 19
Cjs-Message: 08:53:15.350: JS LOG: [LookingGlass/info] loading user theme: /usr/share/themes/Linux Mint/cinnamon/cinnamon.css
Cjs-Message: 08:53:15.403: JS LOG: [LookingGlass/info] added icon directory: /usr/share/themes/Linux Mint/cinnamon

(nm-applet:3326): libnotify-WARNING **: 08:53:15.485: Failed to connect to proxy

(nm-applet:3326): nm-applet-WARNING **: 08:53:15.487: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.Notifications” on object at path /org/freedesktop/Notifications
[31;01merror: Unable to lock /home/chris/.hplip/hp-systray.lock. Is hp-systray already running?[0m
kdeconnect.core: Daemon starting
kdeconnect.core: LanLinkProvider started
kdeconnect.core: Daemon started
kdeconnect.core: Could not query capabilities from notifications server
kdeconnect.core: Broadcasting identity packet
Cjs-Message: 08:53:15.757: JS LOG: [LookingGlass/info] loaded at Sun Jun 20 2021 08:53:15 GMT-0400 (Eastern Daylight Time)
Cjs-Message: 08:53:15.757: JS LOG: Cinnamon started at Sun Jun 20 2021 08:53:15 GMT-0400 (Eastern Daylight Time)
Cjs-Message: 08:53:15.773: JS LOG: [LookingGlass/info] ExtensionSystem started in 1 ms
Cjs-Message: 08:53:15.774: JS LOG: [LookingGlass/info] DeskletManager started in 2 ms
Cjs-Message: 08:53:15.774: JS LOG: [LookingGlass/info] SearchProviderManager started in 1 ms
openGL version 3.1 detected (GL3 Cogl Driver)
** Message: 08:53:15.880: nemo-desktop: session is cinnamon, establishing proxy
Cjs-Message: 08:53:15.908: JS LOG: [LookingGlass/info] Loaded applet show-desktop@cinnamon.org in 62 ms
Cjs-Message: 08:53:15.914: JS LOG: [LookingGlass/info] Role locked: tray
Cjs-Message: 08:53:15.917: JS LOG: [LookingGlass/info] Loaded applet systray@cinnamon.org in 9 ms
St-Message: 08:53:15.920: cogl npot texture sizes SUPPORTED
Cjs-Message: 08:53:15.931: JS LOG: [LookingGlass/info] Role locked: notifications
Cjs-Message: 08:53:15.948: JS LOG: [LookingGlass/info] Loaded applet notifications@cinnamon.org in 30 ms

(tracker-miner-fs:3339): Tracker-CRITICAL **: 08:53:15.965: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Files': D-Bus service name:'org.freedesktop.Tracker1.Miner.Files' is already taken, perhaps the application is already running?
Cjs-Message: 08:53:15.966: JS LOG: [LookingGlass/info] Loaded applet removable-drives@cinnamon.org in 18 ms
Cjs-Message: 08:53:15.995: JS LOG: [LookingGlass/info] Loaded applet printers@cinnamon.org in 29 ms
Cjs-Message: 08:53:16.046: JS LOG: [LookingGlass/info] Loaded applet keyboard@cinnamon.org in 51 ms
Cjs-Message: 08:53:16.053: JS LOG: [LookingGlass/info] Loaded applet xapp-status@cinnamon.org in 7 ms
Cjs-Message: 08:53:16.112: JS LOG: [LookingGlass/info] Loaded applet calendar@cinnamon.org in 59 ms
Cjs-Message: 08:53:16.123: JS LOG: [LookingGlass/info] Role locked: panellauncher
Cjs-Message: 08:53:16.148: JS LOG: [LookingGlass/info] Loaded applet grouped-window-list@cinnamon.org in 36 ms
Cjs-Message: 08:53:16.187: JS LOG: [LookingGlass/info] Loaded applet power@cinnamon.org in 39 ms
Cjs-Message: 08:53:16.189: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: nm-applet (:1.147/org/x/StatusIcon/Icon)
Cjs-Message: 08:53:16.193: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: redshift-gtk (:1.157/org/x/StatusIcon/Icon)

** (csd-power:3189): CRITICAL **: 08:53:16.387: abs_to_percentage: assertion 'max > min' failed
Cjs-Message: 08:53:16.418: JS LOG: [LookingGlass/info] Loaded applet sound@cinnamon.org in 230 ms
Cjs-Message: 08:53:16.455: JS LOG: [LookingGlass/info] Hiding XAppStatusIcon (we have an applet): nm-applet (:1.147/org/x/StatusIcon/Icon)
Cjs-Message: 08:53:16.468: JS LOG: [LookingGlass/info] Loaded applet network@cinnamon.org in 50 ms
Cjs-Message: 08:53:16.665: JS LOG: [LookingGlass/info] Loaded applet menu@cinnamon.org in 197 ms
Cjs-Message: 08:53:16.666: JS LOG: [LookingGlass/info] AppletManager started in 908 ms
Cjs-Message: 08:53:16.670: JS LOG: [LookingGlass/info] Cinnamon took 1426 ms to start
Cjs-Message: 08:53:16.707: JS LOG: Unknown network device type, is 14
cinnamon-session[3088]: WARNING: t+6.76471s: Detected that screensaver has appeared on the bus
Cjs-Message: 08:53:35.667: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: mintUpdate.py (:1.174/org/x/StatusIcon/Icon)
WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support Legacyheader, cannot determine support level
Cjs-Message: 08:54:04.474: JS LOG: [LookingGlass/info] Adding XAppStatusIcon: mintreport (:1.178/org/x/StatusIcon/Icon)
As well, if anyone has insight as to why I am getting poor performance issues in the Mint remote session, would be much appreciative too. Both PCs (Windows RDP'ing into Mint) are hard-wired to the LAN FWIW... Please let me know what I can do to help troubleshoot. Thank you in advance.
Last edited by SMG on Sat Dec 17, 2022 12:37 pm, edited 1 time in total.
Reason: Locking old topic.
shockedquartz
Level 2
Level 2
Posts: 69
Joined: Tue Dec 17, 2019 3:31 pm

Re: Windows to Mint PC RDP Issues

Post by shockedquartz »

Only speaking for 19.3 Cinnamon. I found all the remote desktop solutions to be total hacks and a pain in the butt.
xrdp permission issues. sessions, crashing. Not even starting.
Circumventing using RDP all together, I found x2go works pretty good but it's a bit heavy on CPU and I turn off the service when I don't use it.

In the end, I settled with using Vino, the default remote access solution for Ubuntu. It's not natively supported on Mint (that I know of) and I had to install some extras like dconf editor to get it working and without any encryption, only plain-text passwords. But I use it only via a VPN so I wasn't so worried about that. Latency is a mess. I disable my 2nd monitor using ARandR to keep the bandwidth down. Vino runs in the user session. Meaning it's off when you log out and have to do a hack with lightdm to kick it on remotely with ssh.

Just my opinion, Linux has always been miles behind native Windows Remote Desktop for remote GUI access. Sound, copy/paste, drag/drop, shared printer, scalable to different bandwidths, etc.
My Linux client is Remmina via a PPA which I use alot for work.

Using my android phone with VNC Viewer over LTE and VPN to my Mint PC with Vino. It's manageable but slow as hell.
Windows2LinuxNoob
Level 2
Level 2
Posts: 81
Joined: Mon Mar 23, 2020 11:43 pm

Re: Windows to Mint PC RDP Issues

Post by Windows2LinuxNoob »

I completed the following:

Code: Select all

$ sudo apt update
$ sudo apt purge xrdp xorgxrdp
...then reinstalled these along with xfce4. I modified the .xsessions file to use this front-end which is fine with me. In the file .xsession:

Code: Select all

$ echo xfce4-session>~/.xsession
I simply want to remote into it and control it with something a little more than SSH as I program other devices with this Mint machine. With this 2D environment, it seems to treat my machine better too - fans aren't screaming like they were before (processors not taxed as hard apparently). I'm not an RDP expert so can't say why as to when I have my "regular" Mint desktop RDP'ed over to my Windows machine, works real hard... I might speculate that the processor is doing all the graphical processing - has something to do with it???

Strange because at one point in time, I was able to remote into the Mint machine and get the "regular" desktop - albeit with the issues described previously - but now it has that "Login-close instantly" behavior occurring, so I can't even get back to square one here...

EDIT:
OK, I fixed this piece I had incorrect:

Code: Select all

echo env SESSION_MANAGER -u DBUS_SESSION_BUS_ADDRESS cinnamon-session>~/.xsession
to

Code: Select all

echo env SESSION_MANAGER -u DBUS_SESSION_BUS_ADDRESS -u cinnamon-session>~/.xsession
Would help if I unset the second env. variable... So this gets me back to square one before I went the xfce route.

I wouldn't mind sticking with xfce if it was used only for remote sessions, but I was having issues opening up Thunar (or Nautilus) as root and Eclipse (which yes, I installed this as root). When I run my Mint PC using Cinnamon, I would go to the filesystem root, open the file manager there are root user, then navigate inside the root's home folder where Eclipse is located. If I can get around this, not too concerned with a fancy desktop, but again, want something more than a basic shell as I want to eventually write my code in this remote machine. Looks like I need an education on why I cannot open a program as root when I RDP into the system...

I think I'm going to stay away from the xrdp-xorgxrdp combination. Will be looking into other means to remote into this Mint machine where I can use this machine as if I were using it locally. Maybe I am not setting up something, maybe the capabilities aren't there... Not too sure what I'm dealing with since this is new at the moment.
User avatar
AndyMH
Level 21
Level 21
Posts: 13582
Joined: Fri Mar 04, 2016 5:23 pm
Location: Wiltshire

Re: Windows to Mint PC RDP Issues

Post by AndyMH »

I use nomachine to remote into my PCs, both linux and win. Works 'out of the box'.
Thinkcentre M720Q - LM21.3 cinnamon, 4 x T430 - LM21.3 cinnamon, Homebrew desktop i5-8400+GTX1080 Cinnamon 19.0
Windows2LinuxNoob
Level 2
Level 2
Posts: 81
Joined: Mon Mar 23, 2020 11:43 pm

Re: Windows to Mint PC RDP Issues

Post by Windows2LinuxNoob »

I will give nomachine a look. Uses different protocol than RDP but that’s fine. So going to spend some time learning about the suggested tool and hopefully better results. Thank you @AndyMH!
loloimeusp
Level 1
Level 1
Posts: 2
Joined: Thu Jul 22, 2021 11:16 am
Contact:

Re: Windows to Mint PC RDP Issues

Post by loloimeusp »

Well, RDP is not the best option out there to access a Linux machine... The best solution that I've found for now is ThinLinc (cendio.com)... In terms of better picture quality, better responsivness (even on lower bandwidth/high latency connections), works with sound, low on resources on both host and client and can even provide 3D hardware acceleration from host if combined with VirtualGL... The only "problem" is that it's free only for up to 5 simultaneous connected users and commercial for 5+ simultaneous connections. The server application is Linux only (64bit or 32bit), but has client application for Windows, Mac and Linux (64bit, 32bit and arm). Here's a sample video that I did for comparison - https://youtu.be/xBs0M8-XTJo

Its based on TigerVNC (they're one of TigerVNCs maintainers)... TigerVNC also works great for me by the way, but ThinLinc gets more quality and its much easy to install and configure.
jlarysz
Level 1
Level 1
Posts: 2
Joined: Tue Sep 21, 2021 10:21 am

Re: Windows to Mint PC RDC Issues

Post by jlarysz »

I am running Linux Mint 20.2 on an Intel box, and Windows 10 with Remote Desktop Connection (RDC) from a desktop computer.

I found that I could not run an xrdp session from the Windows machine to the Linux mint using a user id that was already logged in on the Linux box. I had to create a new user in Linux, and then the Windows Remote Desktop Connection session worked just fine.

I think that the reference to X session 0 in the discussion above referred arose from an attempt to log in through RDC using an ID that was already logged in on the Linux box and was occupying X session 0.
Echogolf
Level 1
Level 1
Posts: 1
Joined: Sat Dec 17, 2022 12:17 pm

Re: Windows to Mint PC RDP Issues

Post by Echogolf »

This same issue afflicts at least Raspberry Pis running PiOS Bullseye (Debian11). It seems less of an issue of trying to login with the same account at the console and via RDP at the same time rather the level of account you are using. If you make a new user that is not in the groups that your admin user account is in, then the RDP session works correctly. In fact if you then upgrade the permissions on your test user to be the same as you admin by adding it to all of the same groups as your admin user, the issue arises again for this test account too. I have verified this on both my Pi400 running PiOS Bullseye and my Mint 20.3 laptop.

To fix my Pi400 I implemented this fix https://github.com/neutrinolabs/xrdp/is ... -979322159. I have just implemented the same fix on my Mint 20.3 laptop and that works for me too. :D
Locked

Return to “Networking”