Package Details: parsec-bin 150_28-4

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: 46
Popularity: 0.93
First Submitted: 2017-08-10 02:44 (UTC)
Last Updated: 2022-06-13 13:02 (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

ModYokosuka commented on 2022-07-23 05:03 (UTC) (edited on 2022-07-26 01:21 (UTC) by ModYokosuka)

I was getting a segfault when trying to start parsec. This is a recent development that occurred after a recent pacman update. A quick poke around with GDB showed this.

#0  0x00007ffff7df67fd in ?? () from /usr/lib/libc.so.6
#1  0x00007ffff7658f8c in ?? () from /home/me/.parsec/parsecd-150-84.so
#2  0x00007ffff7639a14 in ?? () from /home/me/.parsec/parsecd-150-84.so
#3  0x00007ffff7650bd0 in wx_main () from /home/me/.parsec/parsecd-150-84.so
#4  0x00000000004010fc in main ()

I deleted my /home/me/.parsec directory and parsec now works correctly.

bryiewes commented on 2022-06-08 17:51 (UTC)

Can the maintainer please update the upstream URL to "https://parsec.app"? That is the current URL for this software.

rad4day commented on 2021-11-29 18:43 (UTC)

Sometimes parsecd remains running after closing parsec, and hijacks my clipboard. This leads to long paste times (seconds) and not being able to paste images, as parsec will immediately reassume control of the CLIPBOARD selection.

This only happens sometimes and can be "fixed" by pkill -9 parsecd, but if anyone knows why this happens and how to stop it I would be grateful to be told.

Erin-Allison commented on 2021-11-24 19:36 (UTC)

It may also be worth noting here that for hardware accelerated decode on Nvidia, you appear to need libva-vdpau-driver installed in addition to libva.

OpalJesterOutpst commented on 2021-10-15 17:20 (UTC) (edited on 2021-10-15 17:21 (UTC) by OpalJesterOutpst)

Hey, as @wibru said back in 2018, if you're having issues running Hardware (Hw) decoding on an Intel Processor with integrated graphics make sure you install your distro's libva-intel-driver package. I was running on Manjaro and would get a black screen and immediate crash without it when trying to stream using hardware.

0.zero commented on 2021-10-11 12:31 (UTC)

I was having the same problem as adam900710, today I finally used strace to have a look at what was going on, the last syscall failure before the program terminating itself was

access("/usr/share/X11/locale/iso8859-1/Compose", R_OK) = -1 ENOENT (No such file or directory)

I don't have that locale enabled on my system, only C and en_US.UTF-8. I tried a (probably really bad and NOT RECOMMENDED) "fix" by doing

sudo ln -s /usr/share/X11/locale/en_US.UTF-8 /usr/share/X11/locale/iso8859-1

And sure enough parsecd will now start on my machine.

Note that this could very well be happening because my pacman.conf has NoExtract lines to block unused languages, though I didn't see an iso8859-1 locale directory in parsec-bin's pkg. Hopefully this helps someone.

adam900710 commented on 2021-07-29 02:17 (UTC)

The package just doesn't work, no stderr/stdout when executing the command parsecd.

After a while it begins to spin inside parsecd-150-28.so.

Not sure what's happening here.

r0zbot commented on 2021-07-26 15:53 (UTC)

@harpium For some reason when using parsec detected my touchpad as a gamepad and it was doing the same thing, so disabling some imputs from it on the gamepad settings page fixed it.

harpium commented on 2021-07-25 22:36 (UTC)

UI has some strange behaviour on Manjaro GNOME where random elements keep getting selected. Here's a recording of it: https://imgur.com/a/ib4t1gf

r0zbot commented on 2021-07-13 03:33 (UTC)

@aoleg94 I'm not sure that's enough, as I already had that installed

tadly commented on 2021-07-12 06:49 (UTC)

I'll add the optional pulseaudio-alsa dependency when I'm back home on my PC.
Thanks for letting us know @aoleg94

aoleg94 commented on 2021-07-12 06:21 (UTC)

parsec now uses alsa to output sound, so there is an optional dependency on pulseaudio-alsa for those who use pulseaudio

r0zbot commented on 2021-07-12 03:59 (UTC)

I can't get audio to work after a parsec update with this package, as I get this:

MTY_AudioCreate: 'snd_pcm_open' failed with error -19

It seems to work fine with the flatpak install though.

Hakkou commented on 2021-06-21 15:39 (UTC)

This PKGBUILD might not necessarily work on aarch64 installs. The .deb package is compiled for armhf/armv7h and not all aarch64 systems can run armv7h executables.

ipetrousov commented on 2021-04-05 16:04 (UTC)

Works great on Arch

Linux archlinux 5.10.16-arch1-1 #1 SMP PREEMPT Sat, 13 Feb 2021 20:50:18 +0000 x86_64 GNU/Linux

pgmillon commented on 2021-01-04 13:18 (UTC) (edited on 2021-01-04 13:19 (UTC) by pgmillon)

Seems broken for now:

libva error: /usr/lib/dri/iHD_drv_video.so init failed
Maximum number of clients reachedFloating point exception (core dumped)

D1Ck3n commented on 2020-10-31 00:41 (UTC)

Hi everyone, i try to use this on my Manjaro System but i get after some seconds a frozen screen, like the sound is still there but i got a frozen frame. On the connected Display i see my input on the host (win10) and everything runs smooth but on my Client (Manjaro) the Frame is frozen :(

tadly commented on 2020-10-22 13:14 (UTC)

@gameslayer on what arm system are you trying to run this?
Parsec only really supports RPI afaik and that's what I used as source as you can see in the "Sources" section above

gameslayer commented on 2020-10-22 12:59 (UTC)

For some reason the Arm64 version doesn't work, it wont run but when I try and run the binary from /usr/bin it says failed to execute parsecd

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.

usernamerequired commented on 2020-02-23 09:03 (UTC)

-> Found parsec-linux.deb ==> Validating source_x86_64 files with sha256sums... parsec-linux.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build parsec-bin

i checked the sha256 and the seem to be correct, dont know whats the hiccup here.

Saff commented on 2020-02-02 14:22 (UTC) (edited on 2020-02-02 21:52 (UTC) by Saff)

The sha256 sum doesn't match anymore, pacaur refuses to install it as is.

Edit: Nevermind! Thanks :)

tadly commented on 2020-01-03 11:01 (UTC)

@erkexzcx Forgot to reply yesterday, sorry.
The .deb package can't have changed as otherwise the sha256 sum wouldn't match anymore.
I agree that parsecgaming could do a better job with providing versioned .deb packages but as they don't we have to work with what we've got.

In regards to automatically updating the PKGBUILD, I think that's a bad idea. I'd rather have a final look at what changed rather then automatic the process.
Whenever there's a new version and I miss to update, just flag the package out-of-date and I usually get to it within 1-2 hours (unless I'm in bed)

erkexzcx commented on 2020-01-02 17:35 (UTC)

Not sure what changed (seems it's upstream change), but /usr/share/applications/parsec.desktop got changed from Terminal=true to Terminal=false which is great since we have native desktop app (no longer need to use browser).

But wondering why I had to perform trizen -S parsec-bin manually to update this package and there is no update for such little change in https://parsecgaming.com/changelog/ ? Also parsec versioning control is such a mess....

So, @tadly - if you could make me a maintainer, I could set up script to auto update this PKGBUILD according to provided content-length attribute from the server:

curl -sI https://builds.parsecgaming.com/package/parsec-linux.deb | grep -i Content-Length | awk '{print $2}'

tadly commented on 2019-12-13 08:10 (UTC)

@Thulinma I remember this being an issue with another package I maintain.
Thanks for the heads-up, should be fixed now :)

Thulinma commented on 2019-12-13 07:27 (UTC)

Hey there! Thanks for keeping this package up to date. Unfortunately the software does hash checks on some of its files, meaning Arch's stripping of binaries changes the hash and can very easily result in a corrupt install. To prevent issues, please add:

options=('!strip')

To the PKGBUILD and it should no longer happen. :-)

tadly commented on 2019-12-09 15:56 (UTC)

@erkexzcx thanks. This would have been a big issue actually. Hope this iteration fixes it (Don't have a arm device available to test)

erkexzcx commented on 2019-12-09 15:49 (UTC)

Not a big issue, but sources on AUR website for arm architectures looks slightly misleading... :D

https://builds.parsecgaming.com/package/parsec-linux.deb (x86_64)
https://builds.parsecgaming.com/package/parsec-rpi.deb (arm)
https://builds.parsecgaming.com/package/parsec-rpi.deb[@] (armv6h)
https://builds.parsecgaming.com/package/parsec-rpi.deb[@] (armv7h)
https://builds.parsecgaming.com/package/parsec-rpi.deb[@] (aarch64)

tadly commented on 2019-12-09 15:21 (UTC)

thanks @E5ten

Everyone else. You might have to explicitly re-install the package due to the version number being in a different format now.

E5ten commented on 2019-12-09 14:58 (UTC)

@tadly I don't use parsec anymore, disowning so you can take over.

tadly commented on 2019-12-06 11:54 (UTC)

@erkexzcx Hm. didn't get a notification for your comment... Anyways. This works on x86_64. ARM I can't test but I would expect it to work.

pkgname=parsec-bin
pkgver=150.10
pkgrel=1
pkgdesc="Remotely connect to a gaming pc for a low latency remote computing experience"
url=http://parsec.tv
arch=('x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')
provides=('parsec')
conflicts=('parsec')
depends=('gcc-libs' 'libglvnd' 'libxext' 'libxcb')
optdepends=('libva: For hardware accelerated decoding')

source_x86_64=("https://builds.parsecgaming.com/package/parsec-linux.deb")
sha256sums_x86_64=('4f465a0aab40abb09017362e67edb875098506dd802ead84ee6535459f6641f3')

source_arm=("https://builds.parsecgaming.com/package/parsec-rpi.deb")
sha256sums_arm=('3b72d1d761f53977fd4be07c7ba049838f3b24f63009b3ed196ca997fa7ea06f')

source_armv6h=($source_arm[@])
sha256sums_armv6h=($sha256sums_armv6h[@])

source_armv7h=($source_arm[@])
sha256sums_armv7h=($sha256sums_armv6h[@])

source_aarch64=($source_arm[@])
sha256sums_aarch64=($sha256sums_armv6h[@])

package() {
    tar xf "${srcdir}/data.tar.xz" -C "${pkgdir}"
    chmod 755 "${pkgdir}/usr/"
}

erkexzcx commented on 2019-12-04 09:44 (UTC)

@tadly - nice one. Just letting you know that your PKGBUILD source code will not work since ARM and x86_64 download URLs are different.

tadly commented on 2019-12-04 08:54 (UTC) (edited on 2019-12-04 09:13 (UTC) by tadly)

@E5ten there you go. Or disown the package and let me maintain it if you don't have the time or desire to do so.

pkgname=parsec-bin
pkgver=150.10
pkgrel=1
pkgdesc="Remotely connect to a gaming pc for a low latency remote computing experience"
url=http://parsec.tv
arch=('x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')
provides=('parsec')
conflicts=('parsec')
depends=('gcc-libs' 'libglvnd' 'libxext' 'libxcb')
optdepends=('libva: For hardware accelerated decoding')
source=("https://s3.amazonaws.com/parsec-build/package/parsec-linux.deb")
sha256sums=('4f465a0aab40abb09017362e67edb875098506dd802ead84ee6535459f6641f3')

package() {
    tar xf "${srcdir}/data.tar.xz" -C "${pkgdir}"
    chmod 755 "${pkgdir}/usr/"
}

erkexzcx commented on 2019-12-04 08:33 (UTC)

Parsec for raspbian supports rpi 0 as well, so it means it should support all ARM devices starting from armv5 (arm). You should provide the same arm binary for the following arm architectures (it's called backwards compatibility. even if it's indeed armv5 binary):

arm
armv6h
armv7h
aarch64

As I said - installation steps should be identical. Need example on how to add additional arm architectures? See for example https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nordvpn-bin

erkexzcx commented on 2019-12-04 08:29 (UTC) (edited on 2019-12-04 08:29 (UTC) by erkexzcx)

Few things to notice:

  1. Out of date (someone marked it yesterday)

  2. They finally have GUI app for Linux. Great, but it seems to be launching from terminal when I open from start menu.

  3. You are missing arm (armv6 or even armv7) architecture (for raspbian). Would be great if you could provide it as well. Should be identical installation.

erkexzcx commented on 2019-02-27 09:16 (UTC)

FYI: https://wiki.archlinux.org/index.php/Gaming#Remote_gaming

erkexzcx commented on 2019-02-24 23:04 (UTC) (edited on 2019-02-25 02:43 (UTC) by erkexzcx)

!!!!! How to fix -7000 error !!!!!

Edit "~/.parsec/config.txt" and add "client_vsync = 0".

rolimans commented on 2019-01-09 15:16 (UTC)

@tadly But what you've said had nothing to do with the problem, and you said unpolitely. Let's end the discussion here...

tadly commented on 2019-01-09 14:35 (UTC)

You are very welcome.
At least I got you to dig for information that was already available instead of making others do it for you :)

rolimans commented on 2019-01-09 14:18 (UTC) (edited on 2019-01-09 14:19 (UTC) by rolimans)

After digging around the internet I found that after installing the package "libvdpau-va-gl" to make the program work, I had to then unninstall the package "libva-vdpau-driver" that was causing conflicts. Only after that things worked fine.

PS. Thanks @tadly for the useless advice.

rolimans commented on 2019-01-09 13:53 (UTC) (edited on 2019-01-09 13:53 (UTC) by rolimans)

@tadly but there is no client connected, as a matter of fact searching on the web fo this problem I found it is a problem with libva.

tadly commented on 2019-01-09 07:13 (UTC) (edited on 2019-01-09 07:14 (UTC) by tadly)

@eduardo_amarall did you ever bother reading the error message? I don't get how people can be this lazy sometimes sigh

Edit: To be slightly less of an ass I'll give you a hint.
"Maximum number of clients reached". What could that mean... hm...

rolimans commented on 2019-01-08 16:14 (UTC)

No matter if I try the daemon or the CLI version it always gives me " [2019-01-08 11:07:53 D] CMD.daemon_join [2019-01-08 11:07:53 D] CMD.app_cfg_get [2019-01-08 11:07:53 D] CMD.app_get_binary_info [2019-01-08 11:07:53 D] CMD.app_whitelist_get [2019-01-08 11:07:53 D] CMD.app_get_runtime_info [2019-01-08 11:07:53 D] CMD.app_server_get_clients [2019-01-08 11:07:53 D] CMD.app_approve_get_pending [2019-01-08 11:08:11 D] CMD.app_cfg_get [2019-01-08 11:08:12 D] CMD.app_get_binary_info [2019-01-08 11:08:12 D] CMD.app_get_binary_info [2019-01-08 11:08:18 D] CLI.server_id = 2611006 [2019-01-08 11:08:18 D] CMD.app_client [2019-01-08 11:08:19 D] CLI.net = BUD|::ffff:35.237.204.248|8000 [2019-01-08 11:08:19 D] CLI.client_x = 1920 [2019-01-08 11:08:19 D] CLI.client_y = 1080 [2019-01-08 11:08:19 D] CLI.renderer = opengl Maximum number of clients reachedFloating point exception (core dumped) "

tadly commented on 2019-01-07 07:13 (UTC) (edited on 2019-01-07 07:13 (UTC) by tadly)

@thisischrys check your ~/.parsec folder.
As of writing this, you should have parsecd-149-2.so. If you don't then start parsec as app-daemon (I still suspect this is the only way of updating the binary but I'm not sure).

To do this run /usr/bin/parsecd app_daemon=1.

If you already have the latest binary and it still doesn't work, you have to be more specific on the issue you're having.

thisischrys commented on 2019-01-06 23:52 (UTC)

Any got this working again? I tried a clean install, still no go.

salsadoom commented on 2018-12-01 19:43 (UTC)

Yeah the daemon just doesn't seem to work, the webpage insists the daemon isn't running but from what I can tell it is working just fine. It seems to be communicating with the webpage, but it refuses to let me host. I don't see any errors of any kind on my end so... who knows.

Modelmat commented on 2018-10-21 04:33 (UTC)

The systemd service doesn't work for me, I have to add the line Environment=TERM=xterm-256colors to the script for it to work.

E5ten commented on 2018-10-17 11:37 (UTC) (edited on 2018-10-17 11:38 (UTC) by E5ten)

It doesn't seem that linux got that update, as the most recent deb from their website is still 147-9 sadly. EDIT: Nevermind, it's just that we received the update through that autoupdating, there is no new deb.

tadly commented on 2018-10-17 08:47 (UTC)

So, parsec is doing weird stuff where it self-updates without any notice (only through a running daemon I think, not sure though).
That IMO sucks bigtime but can't be helped.

Now... From what I can tell, the whole /usr/share/parsec directory can be omitted as the appdata.json and parsecd-<version>.so exist in ~/.parsec/.
Those are the ones getting self-updated.

Finally, 148-1 is the most recent version so a bump is in order :)

Enelar commented on 2018-09-25 17:44 (UTC)

I've got -6, -6023, -17001 issues with no luck

kachunkachunk commented on 2018-09-19 00:28 (UTC) (edited on 2018-09-22 19:55 (UTC) by kachunkachunk)

Edit: Had a redundant response that tadly and test0 already shared from 08/16 and 08/17, so here's a better comment and content. Someone more versed could suggest a better service file, though.

1) Create a systemd service file in /usr/lib/systemd/user/parsecd.service - working content example: https://pastebin.com/raw/4MJS3nx2 (updated 09/22 with a network-online dependency).

2) Reload systemd with sudo systemctl daemon-reload (you may need to do systemctl --user daemon-reload as well, if you're making changes/updates).

3) Enable the newly-created user service: systemctl --user enable parsecd.service

4) Start the user service: systemctl --user start parsecd.service

5) Confirm your daemon can communicate with the parsecgaming.com interface.

ky7pxrp2 commented on 2018-08-18 01:50 (UTC) (edited on 2018-08-18 12:06 (UTC) by ky7pxrp2)

Can connect but only receiving audio--no video. i7-8550U/UHD 620 with libva-intel-driver installed. Any suggestions?

log: https://pastebin.com/9zFuFBb8

tadly commented on 2018-08-17 09:58 (UTC)

Just to make sure, if a systemd service should be added, it should be a user service (installed to /usr/lib/systemd/user/parsecd.service)

test0 commented on 2018-08-16 21:35 (UTC)

Hi, can you add a systemd support for daemon (ex : "sudo systemctl enable/start parsecd" , for "parsec app_daemon=1" command ) ? There is no GUI anymore on Linux, we have choice between CLI or Webpage on any browser, then connecting us with the parsec daemon. :)

E5ten commented on 2018-08-14 20:48 (UTC) (edited on 2018-08-14 20:49 (UTC) by E5ten)

I'm not sure I understand the problem, for me uninstalling parsec and deleting the cache of it etc. and then installing it cleanly works, and after running it and going to https://ui.parsecgaming.com it detects the running daemon. EDIT: Maybe it's possibly related to your AUR helper if you use one, if you do which one do you use?

SuperNegativeP commented on 2018-08-14 01:53 (UTC) (edited on 2018-08-14 01:54 (UTC) by SuperNegativeP)

I think I found out what that file too short error is. The file it's talking about is totally empty. I fixed it by unpacking the .deb and coping the file of the same name out of it. I think that something copied over wrong when it was installed...

Other than that it worked perfect!

erkexzcx commented on 2018-08-13 17:31 (UTC) (edited on 2018-08-13 17:31 (UTC) by erkexzcx)

/home/erikas/.parsec/parsecd-147-9.so: file too short

After fixing PKGBUILD - I ended up with this error. :) Not working or what?

wibru commented on 2018-08-13 14:01 (UTC)

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

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.

tadly commented on 2018-06-19 12:24 (UTC)

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.

Enelar commented on 2018-06-19 12:17 (UTC)

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

tadly commented on 2018-06-17 18:22 (UTC)

@salmongin thanks for that. I can confirm that mesa 18.0.4 works. Also the latest expat works and indeed sndio isn't required anymore :)

salmongin commented on 2018-06-17 18:04 (UTC)

I'm also getting a segfault, I'm running on a Core i7 8th generation with Intel graphics. For a different reason, I downgraded mesa to version 18.0.4-1 and parsec now works. When I upgrade back to 18.1.1-1, it stops working and segfaults once connecting.

I've got an Nvidia chip in my notebook as well and tried to set up bumblebee and primusrun. primusrun segfaulted as well and people said that downgrading mesa to 18.0.4 fixed the issue for them.

tadly commented on 2018-06-17 16:13 (UTC)

Regarding libva, I agree. I also tested that. In regards to expat and sndio, the link I posted yesterday suggests otherwise though. But as long as we don't find the cause for the current segfault (which we can agree on isn't due to libva, expat or sndio) that doesn't matter to much. Can I help you in any way? I'm also in the parsec discord channel where you could ping me for better ways of communication.

E5ten commented on 2018-06-17 16:03 (UTC) (edited on 2018-06-17 16:03 (UTC) by E5ten)

Parsec no longer depends on expat or sndio, the cause of the segfault is still unknown. EDIT: It can't be because of libva, it happens in software mode too.

tadly commented on 2018-06-16 14:09 (UTC)

I just spent another hour double-checking all dependencies as of https://support.parsecgaming.com/hc/en-us/articles/115002699032-Linux-Ubuntu-16-04-and-17-10 and I just can't get it to work...

Enelar commented on 2018-06-16 13:18 (UTC)

I've just tried downgrade to 1.8.3 and it wont help. Either with libva 2.3 and 1.8 it doesnt work. Segfault.

It began after latest update

tadly commented on 2018-06-16 08:14 (UTC)

Anyone else still segfaulting? Someone from parsec was saying that it's most likely due to libva (because they migrated to libva2) but that's default to arch so...<br> @E5ten shouldn't expat<=2.2.4 and pulseaudio-module-sndio still be a dependency?

Enelar commented on 2018-06-12 20:30 (UTC)

https://hub.docker.com/r/kajmaj87/parsec-intel/ https://hub.docker.com/r/schtufbox/parsec_amd/

Enelar commented on 2018-06-12 20:27 (UTC)

same to me, but i've got segfaults after update

SolarAquarion commented on 2018-06-03 10:26 (UTC)

So you only need expat.so.1.6.6?

schtufbox commented on 2018-05-26 18:28 (UTC)

As an aside, used this on another PC, and it ran and connected fine, without downgrading expat. Tried again on my daily machine, no joy, still segfaults. Main difference is, main PC has an AMD video card, pc that works was using intel GMA 4500

schtufbox commented on 2018-05-20 21:14 (UTC)

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: https://hub.docker.com/r/schtufbox/parsec_amd/

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.

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

benjy_parsec commented on 2017-12-17 14:52 (UTC)

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 - https://support.parsecgaming.com/hc/en-us/articles/115003477771. 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!

z0id commented on 2017-12-13 13:35 (UTC)

I did install expat-2.2.4 and it still segfaults on connect, with both hw and sw decoding. Parsec guys would not help as they only support Ubuntu. Any ideas?

sdellysse commented on 2017-12-09 19:24 (UTC) (edited on 2017-12-09 19:24 (UTC) by sdellysse)

Need an old version of expat for parsec to not segfault on connect. Download expat-2.2.4 from here: https://archive.archlinux.org/packages/e/expat/expat-2.2.4-1-x86_64.pkg.tar.xz and pacman -U it

add expat to the IgnorePkg line in /etc/pacman.conf and uncomment the line

You do not need to install any VA-API packages. This build includes the specific libraries parsec needs.

on first run, parsec will fail to start. This creates the configuration directories. On second run, parsec will start fine.

Credit: https://gist.github.com/aoleg94/ee1bcf82d68ddbc6073cd77b39a1fc8b#file-pkgbuild-L39

iamtheoneorg commented on 2017-12-02 02:10 (UTC)

i think you can edit PKGBUILD with depends=('glibc' 'sndio') md5sums=('438177b6f9d81f7eb1f093d920193295')

dmnc commented on 2017-11-23 20:31 (UTC)

@z0id do you have pulseaudio-module-sndio?

exploser commented on 2017-11-23 16:20 (UTC)

I can connect w/o problems using software decoding. Hardware doesn't work at all for me though.

z0id commented on 2017-11-16 16:43 (UTC)

Did anyone manage to connect to the server without getting a segfault? It must be a library thing, as it works on Ubuntu.

dmnc commented on 2017-11-16 09:24 (UTC)

Failed to verify parsec integrity (bad checksum of parsec-linux.deb).

w4tsn commented on 2017-08-06 14:49 (UTC)

Currently fails the md5sum check. Please update. Also this package is missing the pulseaudio-module-sndio dependency. See https://faq.parsec.tv/articles/10121-linux-ubuntu-1604.