net-misc/chrome-remote-desktop (CRD) has some user tweakage and a hard dependency on x11-libs/gksu in order to setup the system up properly for remote access. The first thing is that the user needs to "mkdir ~/.config/chrome-remote-desktop" as itself (not as root). CRD looks for this folder and won't create it for some reason. A tweak in the ebuild would help here. The second thing is that Chrome app requires x11-libs/gksu to use gksudo for adding the user to the 'chrome-remote-desktop' group. It specifically calls gksudo. A dependency can be added for the time being, and I'll be sending an upstream bug to Google to support KDE.
not exactly true. gksu is used only when an existing GUI env is detected (i.e. $DISPLAY is set). if you ssh in it works fine. the usage is largely frivolous even then ... i'll just patch it out so it always uses sudo.
hmm, it only shows up when using --add-user ... i would contend that crd shouldn't even have this flag in the first place. user management should be the user's problem.
should be all set now in the tree; thanks for the report! Commit message: Avoid using gksu and always use sudo http://sources.gentoo.org/net-misc/chrome-remote-desktop/chrome-remote-desktop-41.0.2272.41-r1.ebuild?rev=1.1 http://sources.gentoo.org/net-misc/chrome-remote-desktop/files/chrome-remote-desktop-41.0.2272.41-always-sudo.patch?rev=1.1
