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: TheCyberArcher
Last Packager: TheCyberArcher
Votes: 55
Popularity: 1.08
First Submitted: 2017-08-10 02:44 (UTC)
Last Updated: 2025-03-27 22:29 (UTC)

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 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »

retrop7 commented on 2020-10-04 15:30 (UTC)

Also seeing crashing with hardware acceleration "floating point exception (core dumped)" parsecd.

alchemistake commented on 2020-08-27 18:02 (UTC)

I'm trying to use hardware accelaration but it crashes the whole software. What can I do?

tadly commented on 2020-07-10 08:50 (UTC)

@sauyon Fair point. Something I could have thought of myself. Updated and pushed

sauyon commented on 2020-07-10 08:43 (UTC)

For those having the sha256sum issue, try to find the "parsec-linux.deb" file on your system and remove it from the caches.

FWIW I like adding the version number to the name of the downloaded file, since it gets around this issue and it makes it a bit easier to tell when building manually too.

kajmaj87 commented on 2020-06-25 16:40 (UTC) (edited on 2020-06-25 16:40 (UTC) by kajmaj87)

Is the downgrading to mesa<=18.0.4 still the only solution to avoid the libsndio.so.6.1: cannot open shared object file: No such file or directory error?

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.

kerenua commented on 2020-03-07 00:56 (UTC)

what worked for me in locating the file was find . -name "parsec*"

the fd command gave me no output for some reason.

Daegalus commented on 2020-02-25 19:11 (UTC)

For those having the sha256sum issue, try to find the "parsec-linux.deb" file on your system and remove it from the caches.

For me, pamac was caching the deb file, because pacman -Sc did not help. I used the tool fd to find it.

>>> fd parsec-linux.deb /
/var/tmp/pamac-build-yulian/parsec-bin/parsec-linux.deb

After I removed the parsec-linux.deb file from that tmp folder for pamac, it all worked swimmingly. It might be in a different place for your preferred package tool, or distro.

entrix commented on 2020-02-23 11:20 (UTC) (edited on 2020-02-23 11:20 (UTC) by entrix)

@usernamerequired If you are using yay (or an other AUR helper) it might be possible that it doesn't download the new parsec-linux.deb file.

If you git clone it in a totaly new folder/thing it works fine, because parsec-linux.deb doesn't already exist so it downloads the newer version.

This is only my assumption, but for the moment, I upgrade parsec-bin manually.

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