Package Details: parsec-bin 139_8-2

Git Clone URL: (read-only)
Package Base: parsec-bin
Description: Remotely connect to a gaming pc for a low latency remote computing experience
Upstream URL:
Keywords: parsec remote streaming
Conflicts: parsec
Provides: parsec
Submitter: sdellysse
Maintainer: sdellysse
Last Packager: sdellysse
Votes: 7
Popularity: 0.581789
First Submitted: 2017-08-10 02:44
Last Updated: 2017-12-09 17:21

Latest Comments

schtufbox commented on 2018-05-20 21:14

Gave up getting this working reliably, so I created a docker image instead with HW acceleration for AMD and intel, mainly for my own use but just in case anyone else needs:

Anntoin commented on 2018-03-04 18:36

@sdellysse There should also be a dependency on gtk2

Regarding sndio, this version of the aur package worked for me sndio-1:1.3.0-2-x86_64.pkg.tar.xz (git checkout d4be5063; makepkg)

For expat this version did the trick expat-git-2.2.4.r0.gfc577ad-1-x86_64.pkg.tar.xz (cd src/libexpat; git checkout R_2_2_4; cd ../..; makepkg -e)

FYI for missing libs don't use symlinks. From the wiki:

do not "fix" the problem simply by symlinking. Libraries receive soname bumps when they are not backwards compatible

jbmorgado commented on 2018-02-26 20:07

@benjy_parsec None of the instructions you have in your page actually works.

The one about manual installing the libraries doesn't explain how to actually install the parsec binaries and the one about docker doesn't work (the docker image fails with a segfault).

Could you please look into it? Right now Parsec seems unusable in anything but Ubuntu when it comes to Linux.

jbmorgado commented on 2018-02-26 20:04

It doesn't work, fails complaining it can't find

Tried to use the workaround bellow ln -s /usr/lib/ /usr/lib/ but the error remains exactly the same.

Bousty commented on 2018-02-23 21:23

I have an error, when i try to connect, parsec crash with a segmentation fault:

[2018-02-23 22:22:17 D] CLI.net0 = BUD:

[2018-02-23 22:22:17 D] CLI.net1 = BUD:

[2018-02-23 22:22:17 D] CLI.net2 = BUD:

[1] 1931 segmentation fault (core dumped) parsec

ekkelett commented on 2018-02-02 22:02

@Saladien, you can also just # ln -s /usr/lib/ /usr/lib/ to get around that. Seems like it's not too incompatible.

@benjy_parsec, thanks for your comment. Is parsec actually reliant on sndio? I got it somewhat to work, but couldn't get audio through sndio, whereas without sndio actually enabled with pulseaudio, I still got audio. parsec just seemed to need libsndio -- does it do something with it that isn't actually in regards to outputting audio? If so, pulseaudio-module-sndio hardly seems necessary.

Saladien commented on 2018-01-29 03:36

Thank you for looking into that issue. Spend a few hours today searching for a solution but i dont know how all this stuff works.

sdellysse commented on 2018-01-24 19:18


It looks like at some point sndio got updated, the file on disk is I don't have the time at this moment to investigate futher, but I'll do more when I can.

MakiXx commented on 2018-01-24 17:36

I installed all the dependencies including sndio and pulseaudio-module-sndio but everytime I open up the program I get: cannot open shared object file: No such file or directory

Not really sure what I'm doing wrong here. I have sndio-1:1.4.0-1 installed.

benjy_parsec commented on 2017-12-17 14:52

Hi, I'm the co-founder of Parsec. A user reached out to me and pointed this package out. We have instructions for running Parsec on Arch on our support page - We haven't started officially supporting Arch yet, but in the future we hope to. We are a very small team, so we have to focus on just a couple operating systems for the time being. Sorry about that.

Thanks everyone!

All comments