| 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: | 0.67 |
| First Submitted: | 2017-08-10 02:44 (UTC) |
| Last Updated: | 2025-03-27 22:29 (UTC) |
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.
@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.
@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...
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 :)
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.