flathub / com.parsecgaming.parsec Goto Github PK

I can't connect to some people because they have a version 150-81 but this flatpak version is 150-78. Please fix.

I just had to notice that the parsec desktop client reports the following error on startup:

$ flatpak run com.parsecgaming.parsec
[D 2021-01-06 19:27:24] MTY_DeleteFile: 'remove' failed with errno 39
sh: xdg-mime: command not found

[App Failure]
--------------------
Parsec could not create the application.
Please contact us if this problem persists.

This appears to be related to wayland, because the removal of the wayland permission and forcing parsec to use x11 solves the issue. It just results in terrible performance…

Can someone restart the build for parsec flatpack so users can install from the flatpak reference?

I believe flathub related issue was fixed on their end already, and we just need to start the build.

Parsec's immersive mode pass hotkeys like Meta (Windows key), Alt + Tab for switching between windows, etc. This mode is however doesn't work for me. I have GNOME 44.4 on Arch Linux using Wayland. I have set org.gnome.mutter.wayland's property xwayland-allow-grabs to true, appending parsecd to xwayland-grab-access-rules list, and it's still somehow doesn't work.

Furthermore, I also have tried to switch on/off the mode with Ctrl + Shift + I while connecting to a host, but it seems to don't even bother to grab the keys...

Anybody with an idea or working solution?

I have been using the FlatPak install for about 3 weeks now and I was really enjoying it, I had never used the FlatPak version previously; just tried to force it to install. With the latest rounds of OS updates, Parsec fails to launch with the following error:

Error Screenshot

It reads: "Parsec could not create the application. Please contact us if this problem persists."

I searched online and asked in the Parsec Dicsord; this error was unknown to any of them. So I am left with its an error of the FlatPak.

It worked for a while, but it stopped after I upgraded; here is a list of the packages that were upgraded:

alsa-ucm-conf
apport
apport-kde
distro-info-data
libldb2
liblouis-data
liblouis20
libnvidia-cfg1-515
libnvidia-common-515
libnvidia-compute-515
libnvidia-compute-515i386:
libnvidia-decode-515
libnvidia-decode-515i386:
libnvidia-encode-515
libnvidia-encode-515i386:
libnvidia-extra-515
libnvidia-fbc1-515
libnvidia-fbc1-515i386:
libnvidia-gl-515
libnvidia-gl-515i386:
libsmbclient
libwbclient0
linux-firmware
linux-modules-nvidia-515-5.19.0-21-generic
linux-modules-nvidia-515-5.19.0-38-generic
linux-modules-nvidia-515-generic
linux-objects-nvidia-515-5.19.0-38-generic
linux-signatures-nvidia-5.19.0-38-generic
nvidia-compute-utils-515
nvidia-driver-515
nvidia-kernel-common-515
nvidia-kernel-source-515
nvidia-utils-515
python3-apport
python3-ldb
python3-problem-report
python3-samba
samba-common
samba-common-bin
samba-dsdb-modules
samba-libs
smbclient
vim-common
vim-tiny
xserver-xorg-video-nvidia-515
xxd

Here is a more detailed version of the packages that were being upgraded:

updates.txt

This will be blocked in the linter soon. This issue is a heads-up for that.

See flathub-infra/flatpak-builder-lint#178

Hi,
I am trying to run parsec on the steam deck and while I can start it and it finds he computer (Windows) it should connect to, I am getting this error when I press connect and then it crashes:
Flatpak libavcodec58 not found on your system. [-22]

I found this threat:
#23
But I am not sure how to do this on the steam deck/ if it works at all.
Please take a look at this, would really appreciate it!

You can most noticeable see it on the Steam Deck.
Got to Settings -> Gamepad in Parsec and start pressing Buttons.
You will see that some buttons stick as pressed or do not even register as pressed at all.

I suspect this is a General Parsec Incompatibility with the Steam Input System, but I open it here anyway on the off chance that it is a Flatpak Issue.

Lets hope its a Flatpak one, the chances of getting it fixed otherwise are pretty slim.

It would be great if a latest 22.08 runtime was used if possible.

With the latest update from today I got an error when starting the connection to the remote OS (Windows in my case). I'm using Parsec version 150-85c.

Some discussion is here as well: https://www.reddit.com/r/ParsecGaming/comments/z6ixyx/flatpak_libavcodec58_not_found_on_your_system_22

Hi, I'm using Linux Mint 21.1 and trying to run parsec via the flatpak. When I launch it, I get the errors

[D 2023-08-08 16:55:08] log: Parsec release[release19] (150-89b, Service: -1, Loader: 7)
[D 2023-08-08 16:55:08] MTY_DeleteFile: 'remove' failed with errno 39
[D 2023-08-08 16:55:08] MTY_SOLoad: libcrypto.so.3: cannot open shared object file: No such file or directory
[D 2023-08-08 16:55:08] MTY_SOLoad: 'dlopen' failed to find 'libcrypto.so.3'
[I 2023-08-08 16:55:08] unprivileged_user=1 enable_webview=0
[D 2023-08-08 16:55:08] MTY_SOLoad: libjpeg.so.8: cannot open shared object file: No such file or directory
[D 2023-08-08 16:55:08] MTY_SOLoad: 'dlopen' failed to find 'libjpeg.so.8'
[D 2023-08-08 16:55:10] MTY_SOLoad: libjpeg.so.8: cannot open shared object file: No such file or directory
[D 2023-08-08 16:55:10] MTY_SOLoad: 'dlopen' failed to find 'libjpeg.so.8'
[D 2023-08-08 16:55:10] mty_rwlock_writer: 'pthread_rwlock_wrlock' failed with error 35

I do have both of these libraries installed on my system so I'm unsure why dlopen is failing to find them. I tried setting the LD_LIBRARY_PATH environment variable with no change.

Hello

I'm not too familiar with Flatpaks yet, but do I understand correctly that the line "--persist=." in the configuration is essentially the same as --filesystem=home in that it bind mounts the user's actual $HOME/. (which becomes $HOME) into the container of Parsec as-is?

If so, is this absolutely required for the application to function, i.e. would it be possible to limit it to specific subfolders instead, or, barring that, would the application still function, albeit without having things such as the mentioned persistent login?

The unfortunate part of persist is that it cannot be revoked by something like Flatseal or flatpak override, and giving complete access to home is essentially game over if the application is/becomes malicious.

Thanks in advance!

Just thought i'd ask since it's still in flathub but hasn't been updated in like...forever.

Like the title suggested, currently on wayland gnome, there's no way to grab the super key unlike how it works in X11.
Moonlight solves this by using Keyboard shortcuts inhibit protocol from Wayland.
Can it be implemented here?

Hey there,

it seems that vaapi isn't working in this flatpak.
That would be awesome to get working, how would I need to do that?

Thanks!

Info: runtime org.freedesktop.Platform branch 21.08 is end-of-life, with reason:
   org.freedesktop.Platform 21.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
Info: applications using this runtime:
   com.parsecgaming.parsec

this includes org.freedesktop.Platform.VAAPI.Intel, org.freedesktop.Platform.GL.default and org.freedesktop.Platform.ffmpeg-full too

Logging in with valid credentials:

OS is Fedora Silverblue 33

When I go the route of converting the deb and running it in a toolbox container, it works just fine, so it must be related to flatpak.

Console output:

$ flatpak run com.parsecgaming.parsec
sh: xdg-mime: command not found
[D 2020-11-19 19:04:02] uncurl_listen=-50021
[D 2020-11-19 19:04:02] os_readbin=0

Any ideas? Thanks!

After the latest update of Parsec it seems to be unable to use hardware decoding when streaming from my Windows 10 host. I rolled back to commit 9bec7799484d2cc98e408ba6e363223c9d4674e24e3914d18669306b658dc546 and it worked fine again. I'm on Pop!_OS 20.10.

Nothing unusual in the host logs but the client log shows this:
[D 2021-02-20 16:15:59] stun4 = 52.86.26.213:3478
[D 2021-02-20 16:16:00] net = BUD|::ffff:192.168.0.193|21233
[I 2021-02-20 16:16:00] * vaapi_init/WelsCreateDecoder[275] = -1
[D 2021-02-20 16:16:00] decoder = software

I just updated my system and it appears the new version of parsec has new requirements (?)
When I launch it, it appears for a second or two while it fetches available computers, then immediately crashes.

[fake@fedora ~]$ flatpak info com.parsecgaming.parsec 

Parsec - Simple, low-latency game streaming

          ID: com.parsecgaming.parsec
         Ref: app/com.parsecgaming.parsec/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 3.9.8
     License: LicenseRef-proprietary
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 1.5 MB
     Runtime: org.freedesktop.Platform/x86_64/21.08
         Sdk: org.freedesktop.Sdk/x86_64/21.08

      Commit: 2506bb9c6ca80ccc16ece98cf0840f8fa54938ecf74fad836e211613a6bd7151
      Parent: 053d524d3139a3d02fc340cc3d4e244caa915c085c6b76f802fc8a4f04bfc64d
     Subject: Added StartupWMClass to desktop entry (9aa7ab47)
        Date: 2023-04-01 20:44:54 +0000
[fake@fedora ~]$ flatpak run com.parsecgaming.parsec 
[D 2023-08-11 16:25:47] log: Parsec release[release7] (150-89b, Service: -1, Loader: 7)
[D 2023-08-11 16:25:47] MTY_DeleteFile: 'remove' failed with errno 39
[D 2023-08-11 16:25:48] MTY_SOLoad: libcrypto.so.3: cannot open shared object file: No such file or directory
[I 2023-08-11 16:25:48] unprivileged_user=1 enable_webview=0
[D 2023-08-11 16:25:48] MTY_SOLoad: libjpeg.so.8: cannot open shared object file: No such file or directory
[D 2023-08-11 16:25:48] MTY_SOLoad: 'dlopen' failed to find 'libjpeg.so.8'
[D 2023-08-11 16:25:50] MTY_SOLoad: libjpeg.so.8: cannot open shared object file: No such file or directory
[D 2023-08-11 16:25:50] MTY_SOLoad: 'dlopen' failed to find 'libjpeg.so.8'
[D 2023-08-11 16:25:50] mty_rwlock_writer: 'pthread_rwlock_wrlock' failed with error 35
[fake@fedora ~]$ 

Picture taken right before it crashes:

I've tested this on two different systems (a laptop with an i7-8550U running Fedora 35 and an Intel NUC with i5 10210U with Pop OS 21.10).

On the laptop, running it through software rendering, I get ~15ms decode time, and it's very variable. If I enable the wayland socket, it switches to hardware decoding, and I get ~30ms decode time.

On the NUC, I can reproduce this, and I can also install the Parsec provided DEB. Here, same happens as on the laptop while running the flatpak, but when running the DEB directly, i get about 5-7ms decode time.

This is all for a 1080p60 stream from a LAN connected Windows host.

Is there a reason the flatpak version is so much slower with software rendering, and can that be fixed some way ?

I run on a custom app_channel and with other manual config changes.

When I give the parsec access to my ~/.parsec folder, it doesn't use the config.
When I give it access to ~, it spews an entire config directory across the root of my home folder, rather than in the subfolder it should be using.

I got error about libbfd when I install parsec.

$ flatpak install --reinstall com.parsecgaming.parsec -v
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/pluser/.local/share/flatpak
Looking for matches…
...(snip)...
F: extracting extra data to /home/pluser/.local/share/flatpak/app/com.parsecgaming.parsec/x86_64/stable/.9bec7799484d2cc98e408ba6e363223c9d4674e24e3914d18669306b658dc546-6NRAX0/files/extra
F: Opening user flatpak installation at path /home/pluser/.local/share/flatpak
F: Disallowing ipc access
F: Disallowing network access
F: Running /app/bin/apply_extra 
ar: error while loading shared libraries: libbfd-2.32.so: cannot open shared object file: No such file or directory
tar: data.tar.xz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
mv: cannot stat 'usr/*': No such file or directory
F: running triggers from /usr/share/flatpak/triggers
F: running trigger gtk-icon-cache.trigger
F: Running 'bwrap --unshare-ipc --unshare-net --unshare-pid --ro-bind / / --proc /proc --dev /dev --bind /home/pluser/.local/share/flatpak /home/pluser/.local/share/flatpak /usr/share/flatpak/triggers/gtk-icon-cache.trigger /home/pluser/.local/share/flatpak'
F: running trigger mime-database.trigger
F: Running 'bwrap --unshare-ipc --unshare-net --unshare-pid --ro-bind / / --proc /proc --dev /dev --bind /home/pluser/.local/share/flatpak /home/pluser/.local/share/flatpak /usr/share/flatpak/triggers/mime-database.trigger /home/pluser/.local/share/flatpak'
F: running trigger desktop-database.trigger
F: Running 'bwrap --unshare-ipc --unshare-net --unshare-pid --ro-bind / / --proc /proc --dev /dev --bind /home/pluser/.local/share/flatpak /home/pluser/.local/share/flatpak /usr/share/flatpak/triggers/desktop-database.trigger /home/pluser/.local/share/flatpak'
F: Pruning repo
F: Pruned 61646/0 objects, size 0 bytes
Installation complete.   

And I can't launch parsec.

$ flatpak run com.parsecgaming.parsec
cp: cannot stat '/app/extra/share/parsec/skel/appdata.json': No such file or directory
/app/bin/parsec: line 3: [: /home/pluser/parsecd-150-28.so: binary operator expected
/app/bin/parsec: line 4: /app/extra/bin/parsecd: No such file or directory

I was able to solve the problem by using the following patch, but I am not sure if this solution is good for everyone.

diff --git a/com.parsecgaming.parsec.yml b/com.parsecgaming.parsec.yml
index 5e26871..d8fb473 100644
--- a/com.parsecgaming.parsec.yml
+++ b/com.parsecgaming.parsec.yml
@@ -61,7 +61,7 @@ modules:
       - type: "script"
         dest-filename: "apply_extra"
         commands:
-          - "ar x parsec-linux.deb"
+          - "LD_LIBRARY_PATH='/app/lib' ar x parsec-linux.deb"
           - "tar xf data.tar.xz"
           - "mv usr/* ."
           - "rm -rf usr debian-binary control.tar.gz data.tar.xz parsec-linux.deb"

When running on AMD w/ Wayland (KWin compositor) I'm getting this:

[D 2021-12-18 19:35:28] stun4         = 52.86.26.213:3478
[D 2021-12-18 19:35:29] net           = BUD|::ffff:192.168.7.27|21740
[E 2021-12-18 19:35:29] Vaapi unable to open Wayland display.
[D 2021-12-18 19:35:29] decoder       = software
[D 2021-12-18 19:35:37] Decoder failure, queued_frames=38

The problematic thing seems to be this "Vaapi unable to open Wayland display" line.

Parsec stopped launching after a recent update.

$ flatpak run com.parsecgaming.parsec 
[D 2023-12-11 10:36:30] log: Parsec release[release] (150-91a, Service: -1, Loader: 12)
[D 2023-12-11 10:36:30] MTY_SOLoad: libcrypto.so.3: cannot open shared object file: No such file or directory
[D 2023-12-11 10:36:30] MTY_SOLoad: 'dlopen' failed to find 'libcrypto.so.3'
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: radeonsi
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: radeonsi
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[I 2023-12-11 10:36:30] unprivileged_user=1 enable_webview=0
[D 2023-12-11 10:36:30] mty_gl_ctx_create: 'glXCreateContext' failed
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  89
  Current serial number in output stream:  90
~ $ Gtk-Message: 10:36:30.287: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:36:30.288: Failed to load module "canberra-gtk-module"

Hi, I recently installed the flatpak version of parsec into my fedora system using Wayland. I have read that parsec is onyl compatible with X11, in my case everything works, audio, video, keyboard and mouse but the xbox controller. I have enabled all the settings in flatseal just to test but no luck.

What happens is that in the gamepad section before connecting to a host, it detects the controller, but some triggers or button are not detected. Any idea?

I know is not the controller problem because I can use it on steam for streaming to another device, even tho i get no sound (that's another problem for another day)

Hi there. Great software so far, I'm a fan. :-)

However, using it on Linux (Kubuntu 23.04) via Flatpak (com.parsecgaming.parsec stable) yields the above error message as of late. It did work fine not too long ago though. Naturally, one tries to install libavcodec58 to resolve the issue but since libavcodec59 is the current release, installing the older one either is impossible, fails or mixes up the rest of the system without solving anything.

I did try the .deb package too, getting rid of the Flatpak release, but this, as you may have guessed, hangs on the same issue:

dpkg: dependency problems prevent configuration of parsec:
parsec depends on libavcodec58; however:
Package libavcodec58 is not installed.

So us crazy Linux people may need a way to have Parsec running with the libavcodec59 package to eventually be able to use your great streaming solution again.

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Edit:
My older Linux Mint machine, which still uses libavcodec58, does work as expected, so the recent update of the libavcodec package/library may have caused this. Means it's not exactly Parsec's problem but I would expect the Flatpak installation to be able to bring everything needed to eventually run on any system. Wrong thinking?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In short:
The dependency on libavcodec58 (as opposed to the current libavcodec59 release) seems to be the issue.

Workarounds:

• None -

Wishes:
Sure, if you'd asked me for extra wishes, a proper Parsec release which allows streaming from Linux would also be appreciated. :-)

Parsec flatpak does not start and reports the following error.

makaba@PC192:~> flatpak run --socket=wayland com.parsecgaming.parsec /home/makaba/parsecd-150-28.so: cannot enable executable stack as shared object requires: Permission denied

OS is openSUSE MicroOS