Package Details: parsec-bin 150_28-3

Git Clone URL: https://aur.archlinux.org/parsec-bin.git (read-only, click to copy)
Package Base: parsec-bin
Description: Remotely connect to a gaming pc for a low latency remote computing experience
Upstream URL: http://parsec.tv
Keywords: parsec remote streaming
Licenses: custom
Provides: parsec
Submitter: sdellysse
Maintainer: tadly
Last Packager: tadly
Votes: 29
Popularity: 1.82
First Submitted: 2017-08-10 02:44
Last Updated: 2020-07-24 08:50

Pinned Comments

tadly commented on 2020-06-10 06:09

!!! Please do NOT flag the package out of date just because a new version has been release. !!!

Parsec self-updates and as long as the package still installs (no sha256 mismatch), there is no reason to update it in the AUR as the .deb actually is an older version.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

tadly commented on 2018-08-17 09:58

Just to make sure, if a systemd service should be added, it should be a user service (installed to /usr/lib/systemd/user/parsecd.service)

test0 commented on 2018-08-16 21:35

Hi, can you add a systemd support for daemon (ex : "sudo systemctl enable/start parsecd" , for "parsec app_daemon=1" command ) ? There is no GUI anymore on Linux, we have choice between CLI or Webpage on any browser, then connecting us with the parsec daemon. :)

E5ten commented on 2018-08-14 20:48

I'm not sure I understand the problem, for me uninstalling parsec and deleting the cache of it etc. and then installing it cleanly works, and after running it and going to https://ui.parsecgaming.com it detects the running daemon. EDIT: Maybe it's possibly related to your AUR helper if you use one, if you do which one do you use?

SuperNegativeP commented on 2018-08-14 01:53

I think I found out what that file too short error is. The file it's talking about is totally empty. I fixed it by unpacking the .deb and coping the file of the same name out of it. I think that something copied over wrong when it was installed...

Other than that it worked perfect!

erkexzcx commented on 2018-08-13 17:31

/home/erikas/.parsec/parsecd-147-9.so: file too short

After fixing PKGBUILD - I ended up with this error. :) Not working or what?

wibru commented on 2018-08-13 14:01

with Intel GPU, the things to do to make it works with the last released version (147-9): install libva-intel-driver (HW acceleration)

in pkgbuild: change the md5sums of package to e4baa31eb9a2f5aaad28148014165626 change version from 147-6 to 147-9

amaura commented on 2018-08-10 13:55

Something fun I noticed while trying to build this package again this morning is the parsecd.so changes its name every update to the version of the update. An extra line to update in the PKGBUILD.

tadly commented on 2018-07-31 07:15

With the new version, there's no integrated UI anymore (it seems) which is now handled via either the web at ui.parsecgaming.com or the cli interface.

@E5ten there is a new .deb with a new md5sum online so you might wanna update to that. Current installs will fail otherwise.
The new included .desktop entry allows to supply arguments which the website will supply when launching the daemon. For this to work "xdg-utils" are required (adding those as optional dependencies might also be good)

And lastly, intel + latest mesa seems to be working fine

kode54 commented on 2018-07-31 02:15

Looks like it got silently upgraded to 147_6. This new version appears to store the cruft of the parsec binary in a .so in /usr/share/parsec/skel, pointed to by a json file, which also includes the SHA-256 hash of the file, so either options=('!strip') may need to be specified, or the file may need to be regenerated. Either way, I can't seem to make it actually do anything.

E5ten commented on 2018-07-11 17:07

I have been collecting data from myself and other people I have asked to test, and it seems that with nvidia drivers parsec will just work, on Intel downgrading mesa to 18.04 fixes things, and amd has not worked in the testing. When I get to my computer I will put up a link to my parsec appimage which has downgraded the specific parts of mesa needed for intel GPUs to work. EDIT: schtufbox, I'm interested to know what you put in your docker image to get it working on AMD.