I have installed the package chrome-remote-desktop, but every time I try and use Chrome Remote Desktop the website still says that I need to install a .deb package.
Normally I would confirm that Chrome Remote Desktop is installed correctly by running the crd command, but that does not appear to have been installed.
How do i get this working? I have never had these issues on other Linux distributions, and our support team needs CRD so they can support my machine. Does this just not work with Fedora?
Where did you get chrome-remote-desktop from? That package was built from chromium in Fedora, but it was disabled circa v108 and never made it into F38. It looks like it’s broken due to changes on Google’s end. You now need to use an official build, but Google doesn’t make an RPM version. I hate to suggest using alien, but it’s either that or manually replicating the AUR pkgbuild.
Is an alternative remote desktop system out of the question?
Also, I’ve only used chrome remote desktop in the other direction so I was surprised to discover that the linux version doesn’t support mirroring‽ Less surprisingly, it doesn’t support Wayland, but that kind of cancels out with the other issue.
======================================================================================================================================================================================================
Package Architecture Version Repository Size
======================================================================================================================================================================================================
Installing:
chrome-remote-desktop x86_64 118.0.5993.9-2 @commandline 18 M
Transaction Summary
======================================================================================================================================================================================================
Install 1 Package
Total size: 18 M
Installed size: 49 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction test error:
file /lib from install of chrome-remote-desktop-118.0.5993.9-2.x86_64 conflicts with file from package filesystem-3.18-3.fc38.x86_64
file /usr/lib from install of chrome-remote-desktop-118.0.5993.9-2.x86_64 conflicts with file from package filesystem-3.18-3.fc38.x86_64
What remote desktop solutions can you recommend for KDE? krfb/VNC is slow, unreliable and does not survive hibernate/sleep. Everything else is commercial, as far as I can tell.
I really don’t understand why this isn’t being addressed. It seems pretty clear that while Google have made upstream changes the changes aren’t insurmountable because Arch and the baby Archs support it flawlessly.
I understand the theory, but I see a couple of issues:
The command sudo dnf install chrome-remote-desktop works on a clean install of Fedora 38. It comes from the Updates repo. If it is known not to work, then why publish it at all?
How did it work in the past? It seems pretty clear that at some point it did work, and therefore there was a work-around for the closed source binaries.
Let’s assume it doesn’t work. What do I use instead? Is there an alternative Open Source option that takes care of dialling home and NAT traversal? KRFB is unusable.
It does something, but it doesn’t install chrome-remote-desktop. Instead it installs chromium-common, which Provides and Obsoletes chrome-remote-desktop. This was apparently an attempt to make sure chrome-remote-desktop was removed on upgrades after being disabled. Unfortunately, the version on the Obsoletes wasn’t updated when it was disabled for the last time, so I’m not sure this is working as intended.
Chrome Remote Desktop recently had to switch to a different signaling service. Unfortunately, the new service doesn’t support third-party API access, so it will only work with official builds, and a third-party build using the Fedora API keys would not be expected to work at this time. I don’t know if we’ll be able to relax this restriction in the future, but for now the only solution would be to use the official host binary.