Chrome "Remote Desktop" feature

[Clarity]

Has anyone using a PUP gotten Chrome Remote Desktop to

1. Install?

2. Remotely access another "Chrome" computer?

If so, which Chrome did you install and onto which PUP?

On couple of PUPs, Chrome Remote Desktop installation "stops" on the following screen.

RemoteDesktop Install failure.jpg (24.7 KiB) Viewed 1795 times

Thanks in advance for any help

[mikewalsh]

@Clarity :-

Heh. Sounds ve-e-ery familiar.....

I've tried installing the thing several times over the last 18 months or so. Stops at exactly the same point for me, too.

I believe it's to do with the "xdg-open" stuff, which utterly fails to function in Puppy. I've looked into it a few times, but numerous web searches yield nothing of any use whatsoever. It seems to be automatically assumed that if you're running a "proper" Linux distro (i.e., a full mainstream 'install'), then it will simply function without issue. So therefore, nobody has bothered to detail any "fixes" for it...because a 'sensible' Linux user won't HAVE any problems with it.

Huh??!?

(After all, if you're daft enough to run Linux as the 'root' user, then you deserve all the problems you get, y'know? So the thinking goes... )

Mike.

[bigpup]

Found this info.
Maybe it will help.
https://www.helpwire.app/blog/chrome-re ... top-linux/

[williams2]

"xdg-open" stuff, which utterly fails to function in Puppy

Some Pups, like BionicPup64, have code that breaks xdg-open.

Puppy uses Rox-Filer to open files but in some Pups,
you can edit /usr/local/bin/roxfiler and change this:

exec /usr/local/apps/ROX-Filer/AppRun "${@#*file://}"

to this:

exec /usr/local/apps/ROX-Filer/AppRun "$@"

xdg-open should now work better.

The torrent line in /usr/local/bin/xdg-open does nothing, unless you move it in to the case statement, like this:

Code: Select all

#!/bin/sh
#this script created by Jemimah. see: http://murga-linux.com/puppy/viewtopic.php?t=63400&start=150
#110115 xdg-open used to be a symlink to defaulthandler.

case "$1" in
        '') exit
                ;;
        file://*) exec /usr/local/apps/ROX-Filer/AppRun -U "$1"
                ;;
        magnet:*) exec transmission "$1"
                ;;
        *://*) exec rox -U "$1"
                ;;
        *@*.*) exec rox -U "mailto:${1}"
                ;;
        *) exec rox "$1"
                ;;
esac

It can be problematic if an installer (or any software expects to use sudo

AFAIK, this (roxfiler) is fixed in FossaPup64.

[ozsouth]

@Clarity - I have used C-R-D with ScPup64-20.06. I used a .pet I made a year ago & the browser plugin to connect then.
Old .pet no longer works. (Chrome = constant change). I've made a new .pet including parts of the current .deb.
Connects via ScPup64-21.04, but as for security etc - I don't know. On both PCs, need to install .pet, then open latest chrome & install c-r-d plugin, run it & go to remotedesktop.google.com/support. USE AT OWN RISK.

.pet is here: https://www.mediafire.com/file/vbky1xr ... 2.pet/file

I apologise if ads at mediafire links are inappropriate.

EDIT: Mouse lag is quite noticeable. (most edits to post were typos).

[Clarity]

Thank you very much, @ozsouth. I will try today your PET and report. I am currently running Slacko64 v8.2.2.

Currently, reviewing @bigpup's CRD link, after deb manually installed, I get the following in a test within the terminal

Code: Select all

~$ mkdir ~/.config/chrome-remote-desktop                                                                                                                                           
~$ /etc/init.d/chrome-remote-desktop stop
/etc/init.d/chrome-remote-desktop: line 22: /lib/lsb/init-functions: No such file or directory

~$ pwd  
/root
~$ touch .chrome-remote-desktop-session

~$ /etc/init.d/chrome-remote-desktop start
/etc/init.d/chrome-remote-desktop: line 22: /lib/lsb/init-functions: No such file or directory

These messages are gotten in a terminal on @norgo's Slacko64 v8.2.2. Seems something expected in distro is missing for the CRD to work.

CRD also fails when attempts to have the extension load in Chrome on @666philb's and @01micko's PUPs.