Description of problem: chrome-remote-desktop fails to start with the following error: $ /usr/lib64/chrome-remote-desktop/chrome-remote-desktop -s 1366x765 --start --foreground 2018-01-26 21:31:30,825:ERROR:Could not execute /usr/lib64/chrome-remote-desktop/user-session: No such file or directory Version-Release number of selected component (if applicable): chrome-remote-desktop-63.0.3239.108-1.fc27.x86_64 How reproducible: 1. run chrome-remote-desktop using the command above 2. it fails with an error about user-session Actual results: 2018-01-26 21:31:30,825:ERROR:Could not execute /usr/lib64/chrome-remote-desktop/user-session: No such file or directory Expected results: chrome-remote-desktop should start a desktop session and start accepting connections. Additional info: I tried symlinking user-session: sudo ln -s /etc/opt/chrome/native-messaging-hosts/user-session /usr/lib64/chrome-remote-desktop/user-session That led to a similar error about remoting_user_session. I tried symlinking that: sudo ln -s /etc/opt/chrome/native-messaging-hosts/remoting_user_session /usr/lib64/chrome-remote-desktop/remoting_user_session That led to an error about libbase.so: /usr/lib64/chrome-remote-desktop/remoting_user_session: error while loading shared libraries: libbase.so: cannot open shared object file: No such file or directory /usr/lib64/chrome-remote-desktop/libbase.so already existed, so I not sure what to do next.
Workaround: on Fedora 28, with chrome-remote-desktop-65.0.3325.181-1.fc28.x86_64, it works for me after making user-session setuid root: $ sudo chmod +s /usr/lib64/chrome-remote-desktop/user-session
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This has been fixed for a while now, actually.