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.

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) "

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

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

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.

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.

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.

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 :)

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

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.

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

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