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
Search Criteria
Package Details: parsec-bin 150_97c-1
Package Actions
| 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: | DXC-0 |
| Last Packager: | DXC-0 |
| Votes: | 54 |
| Popularity: | 0.22 |
| First Submitted: | 2017-08-10 02:44 (UTC) |
| Last Updated: | 2025-05-25 17:39 (UTC) |
Dependencies (9)
- ffmpeg4.4
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- libglvnd (libglvnd-gitAUR)
- libxcb (libxcb-gitAUR)
- libxext (libxext-gitAUR)
- libxi (libxi-gitAUR)
- openssl-1.1
- pipewire-alsa (pipewire-full-alsa-gitAUR, pipewire-alsa-gitAUR)
- libva (libva-gitAUR, libva-headlessAUR, intel-media-stack-binAUR, intel-media-stack-legacy-binAUR) (optional) – For hardware accelerated decoding
Required by (0)
Sources (1)
wibru commented on 2018-08-13 14:01 (UTC)
amaura commented on 2018-08-10 13:55 (UTC)
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 (UTC)
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 (UTC)
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 (UTC) (edited on 2018-07-11 17:08 (UTC) by E5ten)
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.
schtufbox commented on 2018-07-02 18:23 (UTC)
Also, with regards to the docker image for AMD that I made, I'm not updating it anymore, so eventually it will break, sorry. No longer have an AMD card to test with.
schtufbox commented on 2018-07-02 18:21 (UTC)
Hmm. I just removed the mesa dependancy from the PKGBUILD and installed and it ran fine. Upgrading over the previous version. Nvidia gtx 1050 video card
E5ten commented on 2018-07-02 13:54 (UTC)
If they don't conflict and one of you adds a mesa-18.0.4 package I will replace mesa with it as a dep.
tadly commented on 2018-06-19 13:21 (UTC) (edited on 2018-06-19 13:22 (UTC) by tadly)
I noticed this "we dont care" mentality as well. Regarding a separat mesa package in the aur, it would make more sense to call it mesa-18.0.4 to represent exactly what it is. Do 18.0.4 and 18.1* interfere with each other? Would be nice to have them installed alongside each other.
Enelar commented on 2018-06-19 13:10 (UTC)
Well, i've been chatting with their support. Long story short 'we dont care, ubuntu only'.
Yes, dependency is mandatory, otherwise it would break after each update. Also im thinking about parsec-dependencies or parsec-mesa aur, that would unpack right version.
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.