GithubHelp home page GithubHelp logo

archlinux.chrome-remote-desktop's People

Contributors

felipejunger avatar frealgagu avatar jamesan avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar

Forkers

matt8955 czm1k3 ancientstraits ontelnia casaper gyurmogyuri martincastellano bass-03 dhruvesh2 torettop siliconmeadow ean142023 l3m0n-cao xat0mz anantapodder

archlinux.chrome-remote-desktop's Issues

tput errors during update

When upgrading there are lots of tput errors. See output below.

Note $TERM does have a value set:

echo $TERM
xterm-256color

OS: Manjaro Linux x86_64
Kernel: 5.15.48-1-MANJARO
Shell: bash 5.1.16
DE: GNOME 42.2

Generating chrome-remote-desktop information...

Building chrome-remote-desktop...
==> Making package: chrome-remote-desktop 103.0.5060.46-1 (Mon 27 Jun 2022 08:29:04 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading chrome-remote-desktop-103.0.5060.46.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 18.0M  100 18.0M    0     0  14.6M      0  0:00:01  0:00:01 --:--:-- 14.6M
  -> Found chrome-remote-desktop.service
  -> Found pamrule
  -> Found crd
==> Validating source files with sha256sums...
    chrome-remote-desktop-103.0.5060.46.deb ... Passed
    chrome-remote-desktop.service ... Passed
    pamrule ... Passed
    crd ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting chrome-remote-desktop-103.0.5060.46.deb with bsdtar
==> Starting build()...
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "chrome-remote-desktop"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: chrome-remote-desktop 103.0.5060.46-1 (Mon 27 Jun 2022 08:29:15 BST)
==> Cleaning up...

------------------------------------------------------------------
    SNIP - irrelevant output removed
------------------------------------------------------------------

Upgrading chrome-remote-desktop (101.0.4951.26-1 -> 103.0.5060.46-1)...                                                                 
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Set up CRD by issuing the command:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
crd --setup
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
as a normal user.

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
After that, enable access to CRD in your chrome or chromium browser.

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
To {enable,start} the service, issue the command:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
systemctl --user {enable,start} chrome-remote-desktop
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
This only really makes sense for servers.

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
You can also start the chrome remote desktop server by issuing the command:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
crd --start
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
as a normal user. 
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
This will prompt you to set up your CRD if it hasn't been set up already.

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Go to https://support.google.com/chrome/answer/1649523 for more information.

Failed to download most recent version

Tried to run the script but it failed to download the most recent version

curl: (22) The requested URL returned error: 404

tried to brute force the link on the PKBUILD but go the

ERROR: One or more files did not pass the validity check!

Pls help

Error downloading sources

Hi, I've tried to build this package but failed to download the chrome-remote-desktop_91.0.4472.10_amd64.deb file.
I'va also tried to download the .deb file using wget, but the file does not seem to exist.

Please find below the error messages:

:: (1/1) Parsing SRCINFO: chrome-remote-desktop
==> Making package: chrome-remote-desktop 91.0.4472.10-1 (Tue 20 Jul 2021 04:36:43 PM KST)
==> Retrieving sources...
-> Downloading chrome-remote-desktop-91.0.4472.10.deb...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 1449 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_91.0.4472.10_amd64.deb
Aborting...
error downloading sources: chrome-remote-desktop

Forcing desktop 0 causes crd to crash

I currently want my desktop session to be display 0 [the main screen] so i won't have to deal with firefox already opened errors and come back home with some things i done over crd already there.

however, when modifying the chrome-remote-desktop and forcing it to use display 0 it ends up failing to start up.

is there a way to make crd use the same desktop as the main screen?

crd --setup requires nano

crd --setup currently relies on nano which is neither listed as dependency nor part of base/base-devel. There is no check when starting, so if nano isn't installed it fails to open the appropriate editor windows in between.

Ideas:

  • List nano as (optional?) dependency
  • Check for nano and exit if not accessible before performing any actions in --setup
  • (Honor EDITOR if set to make vim/emacs/notepad.exe-Users happy ;) )

start-host freezes on start

When starting start-host, it came to a complete halt for me. It seems to be because Xvfb struggles to start (or at least is unresponsive) when the DISPLAY variable is set to itself. I had to move where DISPLAY was set in chrome-remote-desktop for it to work, setting it in the environment after Xvfb is started and before it is checked to be alive using xdpyinfo.

dpkg-query

Unfortunately the latest chrome-remote-desktop uses dpkg-query to figure out if xserver-xorg-video-dummy is updated or not. Check the function should_use_xvfb().

Can this be patched instead of manually setting the env variable for it?

AUR failed to build. Download URI 404 outdated. 

Cloning chrome-remote-desktop build files...
Generating chrome-remote-desktop information...
Checking chrome-remote-desktop dependencies...
Resolving dependencies...
Checking inter-conflicts...

Building chrome-remote-desktop...
==> Making package: chrome-remote-desktop 99.0.4844.11-1 (2022 m. balandžio 17 d. 00:42:07)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading chrome-remote-desktop-99.0.4844.11.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0  1449    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_99.0.4844.11_amd64.deb
    Aborting...
Failed to build chrome-remote-desktop

Size file requirement breaks "Resize to fit" functionality

Thanks for packaging this! I came across 1 issue today:

Having to specify a resolution in ~/.config/chrome-remote-desktop/Size forces that size to be used even if the "Resize to fit" option is enabled in the client. I've verified things work fine if I remove the --size parameter from the chrome-remote-desktop command in crd.

Is there a reason to require an explicit size? Looking the source of chrome-remote-desktop, it looks like there are some environment variables (CHROME_REMOTE_DESKTOP_DEFAULT_DESKTOP_SIZES) that would allow something similar if desired.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.