Arch Linux User Repository

!!! 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.

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

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.

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.

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.

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

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.

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.

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.

Just gonna mention that I've already sent a mail to parsec mentioning the issue. No answer yet but I'll keep you guys posted if there are any news. @Enelar maybe we should add mesa<=18.0.4 as dependency for the time being just so it's obvious to people not following the aur comment section as much.

I've spoted segfault in deflate -> png -> i965 libraries. I've been trying downgrade everything: i965, libz, libzip, libpng, glibc. No luck.

Confirm mesa 18.0.4 works. https://archive.archlinux.org/packages/m/mesa/mesa-18.0.4-1-x86_64.pkg.tar.xz