Package Details: parsec-bin 150_97c-1

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.app
Keywords: parsec remote streaming
Licenses: custom
Provides: parsec
Submitter: sdellysse
Maintainer: tadly
Last Packager: tadly
Votes: 53
Popularity: 0.065392
First Submitted: 2017-08-10 02:44 (UTC)
Last Updated: 2025-01-30 13:37 (UTC)

Required by (0)

Sources (1)

Pinned Comments

tadly commented on 2020-06-10 06:09 (UTC) (edited on 2020-06-10 06:10 (UTC) by tadly)

!!! 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 .. 7 8 9 10 11 12 13 Next › Last »

Anntoin commented on 2018-03-04 18:36 (UTC)

@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 (UTC)

@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 (UTC) (edited on 2018-02-26 20:04 (UTC) by jbmorgado)

It doesn't work, fails complaining it can't find libsndio.so.6.1

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

Bousty commented on 2018-02-23 21:23 (UTC) (edited on 2018-02-23 23:48 (UTC) by Bousty)

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:192.168.0.40:22620

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

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

[1] 1931 segmentation fault (core dumped) parsec

https://pastebin.com/7KWVNp9Y

ekkelett commented on 2018-02-02 22:02 (UTC) (edited on 2018-02-02 22:03 (UTC) by ekkelett)

@Saladien, you can also just # ln -s /usr/lib/libsndio.so.7 /usr/lib/libsndio.so.6.1 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 (UTC)

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 (UTC)

@MakiXx

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

makidoll commented on 2018-01-24 17:36 (UTC)

I installed all the dependencies including sndio and pulseaudio-module-sndio but everytime I open up the program I get:

libsndio.so.6.1: 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.

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 Next › Last »