remote desktop to blendos
i enabled remote desktop to blendos but i can't get it to work. i have tried several protocols and apps.
i tried to find any documentation or youtubes, or googles telling me what to do.
can't figure it out so i came here. should i give up on the internal 'settings' remote desktop and use something else?
33 Replies
How are you trying to enable remote desktop?
If its a setting within the "System Settings", what Desktop Environment are you using?
In the case of it being a setting in your DE's settings program, I'd recommend checking their documentation to see if it needs additional packages to enable specific functionality
the default one, i believe that is GNOME
is there a way to check from terminal?
systemctl status |grep -i gnome
│ ├─gnome-remote-desktop.service
│ │ └─2621 /usr/lib/gnome-remote-desktop-daemon
information I'm reading online points to Gnome Remote Desktop needing atleast one extra package to enable specific functionality
Though the only two options for protocol appear to be either VNC, via LibVNCServer, or RDP, via FreeRDP
OH. It appears the default is RDP. Have you already tried connecting using RDP?
RDP means normal windows RDP right?
cause yes i have tried doesn't seem to work
Same protocol, yeah.
Did you try to sign into RDP using your username AND password?
yes, i just tried from a win10 machine rather than my mac .. it says 'an authentication error has occured. the token supplied to the function is invalid.' not sure how to suplly a token
Sounds like Windows is just being Windows, if anything. Are you able to try remmina from a different linux machine?
just to make sure its not "Just Windows Things (TM)"
ill have to boot up a vm or something i don't have any other/more GUI based linux
VMs usually don't have access to your local network without more tinkering
Unless you're using Hyper-V or TrueNAS, I still have yet to learn how to properly expose the local network to anything under KVM...
shouldn't be an issue, just won't happen any time soon. i am going away for a week. andi have to re-image a work. machine then pass its nvme through to my unraid, via vm. and not break the tpm, bitlocker, secureboot, or UUID. as it was losing the machine cert and not having the vpn work.
i appreciate the info. and help you have provided but ill have to give up for now it would seem. cheers
wanted to let you know that it works. the main issue is that everytime i reboot my blendos it randomizes the password
any chance you know how to have that stay set
?
that shouldn't happen
i have confirmed it definitely does. am i doing something wrong? it seems to have an independent username and password field. maybe making it the same as my user was a mistake.
after reboot the password field randomizes. is there a way to stop that? or set it from the commandline as i am always able to ssh into the machine.
this is for RDP
not your main system
correct. how do i set it and have it remain set and not change on reboot or how can i change it from commandline?
You can try asking Google
Seems like a great security feature
sure if you were crazy enough to expose RDP to the internet this would be a very good idea i suppose but really you shouldn't do that regardless. the problem i am having with blendos is that the only things you can really find on google and youtube is about its distrobox like features.
excuse me for asking but have I done something wrong, i thought i was in the extact right place to ask for help. discord>blendOS>support>'remote desktop to blendos' <-my thread.
yeah this is where the support is
it's so new that the guides and whatnot have not been built up yet
I haven't messed around with xrdp on Linux
but
xrdp should be the RDP backend so you could look into thatthanks i had heard of xrdp but i wasn't sure that blendos was using that, because when i did a quick search of the services i didn't find it. but i will take a closer look.
so it seems to be gnome-remote-desktop not xrdp. still haven't quite figured out the rest.
sudo ss -pan |grep 3389
tcp LISTEN 0 10 *:3389 : users:(("gnome-remote-de",pid=2120,fd=16)) tcp ESTAB 0 97021 [::ffff:192.168.1.x]:3389 [::ffff:192.168.1.x]:59503 users:(("gnome-remote-de",pid=2120,fd=18))
[ ~]$ systemctl list-units |grep -i gnome-remote-de
run-user-1000-gnome\x2dremote\x2ddesktop-cliprdr\x2db5OLLl.mount loaded active mounted /run/user/1000/gnome-remote-desktop/cliprdr-b5OLLl okay i figure it out ... now i just need to figure out how to run a command at startup on this system, i dont' see a crontab /usr/bin/grdctl rdp set-credentials <username> <password> so i was going to edit the 'service' but strangly i can't figure out the actual service name you can see from my previous that when listing all service status it doesn't have the usual
[ ~]$ systemctl list-units |grep -i gnome-remote-de
run-user-1000-gnome\x2dremote\x2ddesktop-cliprdr\x2db5OLLl.mount loaded active mounted /run/user/1000/gnome-remote-desktop/cliprdr-b5OLLl okay i figure it out ... now i just need to figure out how to run a command at startup on this system, i dont' see a crontab /usr/bin/grdctl rdp set-credentials <username> <password> so i was going to edit the 'service' but strangly i can't figure out the actual service name you can see from my previous that when listing all service status it doesn't have the usual
nameofservice.service
so i believe the service is
/usr/lib/systemd/user/gnome-remote-desktop.service
but instead being called by the system from /usr/lib/systemd/system its in the systemd/user/ and isntead of being
WantedBy=multi-user.target
it is
WantedBy=gnome-session.target
is there a way to temporarily override the 'overlay' not allowing me to edit anything in the /usr directory?
okay i am used to servers so i didn't realize this is the proper way to show the status of this service but i still don't know how to edit it to set my creds to remain static.. could be that i am autologging into the machine on reboot but that was only because the service being a user gnome-session.target doesn't start until you login.
systemctl --user status gnome-remote-desktop
● gnome-remote-desktop.service - GNOME Remote Desktop
Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enabled; preset: enabled)
Active: active (running) since Sat 2023-11-18 11:22:17 EST; 1 day 9h ago
Main PID: 2120 (gnome-remote-de)
Tasks: 25 (limit: 38344)
Memory: 229.9M
CPU: 2h 49min 15.346s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remote-desktop.service
└─2120 /usr/lib/gnome-remote-desktop-daemon@225droid, you've gained the level
1systemctl --user disable gnome-remote-desktop
sudo cp /home/<user>/.config/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable gnome-remote-desktop
sudo vi /etc/systemd/system/gnome-remote-desktop.service
Change
WantedBy=gnome-session.target
To
WantedBy=multi-user.target
sudo systemctl enable gnome-remote-desktop
Created symlink /etc/systemd/system/multi-user.target.wants/gnome-remote-desktop.service → /etc/systemd/system/gnome-remote-desktop.service.
forget all that, i thought i was getting somewhere but i can't set the password im getting this error probably cause the gnome sesssion isn't properly active or something after a reboot
/usr/bin/grdctl rdp set-credentials <username> <password>
Failed to lookup legacy VNC password schema: Cannot autolaunch D-Bus without X11 $DISPLAY
Cannot autolaunch D-Bus without X11 $DISPLAY
the dbust status even thought its enabled and running ... ends with
dbus-daemon[1362]: [session uid=1000 pid=1362] Failed to activate service 'org.gnome.Shell.Screencast': timed out (service_start_timeout=120000ms)
and the remote desktop status with
gnome-remote-de[1420]: RDP server started
gnome-remote-de[1420]: [RDP] Credentials are not set, denying client
i am stuck again. giving up for tonight.
Use rustdesk. I could not get my wife’s Win10 laptop to RDP to her Win11 desktop. Rustdesk worked straight up. Add Tailscale to securely access anywhere in the world.
If it’s on the AUR it’s tricker to get in the host
Unless they have an appimage or flatpak
i ended up trashing my blend install somehow, (i did and update from the console and it messed it up), rather than try to fix it, i split out another partition and called it system, and reinstalled there. then copied over my home folder from my user partition. to get back most of my settings and what not. the very strange thing is . remote desktop is no longer behaving poorly. the password is working without randomizing and all in all its mostly reliable.
except one thing, i can't headless reboot, then use remote desktop. i have autologin turned on but that doesn't seem to help. the gnome-remote-desktop.service is running.
when i tail the log like so , i get this error.
journalctl -f -n 100
...
gnome-remote-de[3022]: [RDP] Credentials are not set, denying client
i found the following and it worked once for me but i am unsure what i did that made it stop working.
https://gist.github.com/Pieter81/78a3a087f142d712951f8352bb9ab2ba
once i get things working consistently i will report back.
Gist
configures then activates gnome-remote-desktop from the command line
configures then activates gnome-remote-desktop from the command line - reset_gnome_VNC_password.sh
tried this one too with some edits of course.
https://gist.github.com/greyltc/7085bff8f2e728b60077b81329019828
Gist
configures then activates gnome-remote-desktop from the command line
configures then activates gnome-remote-desktop from the command line - launch-GRD.sh
i think i am possibly screwed on this due to the read-only file system.
BlendOS Mutifier
- To use
mutifier, run sudo system install gum beforehand.
- mutify-cli requires no extra dependencies and is used as such:
mutify-cli <mount-point> [other-mount-point], ex. mutify-cli /usr/@225droid
you can experiment
thank you that helped. and again i got it to work once, then i rebooted to see if this time i could consistently replicate my success. so far no go.
i will try again tomorrow. cause some how i have it so messed up right now that i can't even reboot remotely. ha!
still having trouble scripting it but when i enter all the lines manually via ssh i get the credentials set properly, so i know the gnome-keyring-daemon is working the way i want.
for example, i can lookup my credentials using
secret-tool lookup xdg:schema org.gnome.RemoteDesktop.RdpCredentials
{'username': <'REDACTED.actual.username'>, 'password': <'REDACTED.actual.password'>}
certs are all working as well
this is the error i get when i try to connect via RDP
pipewire[1957]: pw.link: (47.0.0 -> 65.0.0) negotiating -> error (no more input formats) (configure-configure)
you can try something that isn't RDP
try using xvnc
I GOT IT i am now able to reboot, SSH into the box, then run a script and then RDP in.. WOOT!
i cleaned up the mess of a script and redacted it of course. it assumes you already have the tls setup and what not. I think you can just enable everything in the GUI/Settings. if anyone wants a hand with this let me know.
basically just reboot. SSH in, and run the script. depending on how fast your computer is you might need to wait for the system to finish rebooting like a minute or so, then RDP will work!