Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

libavcodec58 not found on your system. [-22] #23

Closed
rndevfx opened this issue Nov 28, 2022 · 5 comments
Closed

libavcodec58 not found on your system. [-22] #23

rndevfx opened this issue Nov 28, 2022 · 5 comments

Comments

@rndevfx
Copy link

rndevfx commented Nov 28, 2022 •
edited
Loading

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
@rndevfx rndevfx changed the title Flatpak libavcodec58 not found on your system. [-22] libavcodec58 not found on your system. [-22] Nov 28, 2022
@leohearts
Copy link

+1 I'm using Ubuntu Lunar Lobster (development branch), and libavcodec58 has been upgraded to libavcodec59 .
Consider bundling libavcodec58 within ?

@NightHammer1000
Copy link
Contributor

This is down to the SDK Version used I think.
Switching back to 21.08 should fix it.

NightHammer1000 added a commit to NightHammer1000/com.parsecgaming.parsec that referenced this issue Nov 29, 2022
@NightHammer1000
Downgrade Freedesktop SDK to counteract libcacodec58 Issue
f46534f 
flathub#23
@NightHammer1000 NightHammer1000 mentioned this issue Nov 29, 2022
Merged
@rndevfx
Copy link
Author

rndevfx commented Nov 29, 2022

This fixed the issue for me :)

@NightHammer1000
Copy link
Contributor

Even with Flatpak we cant escape dependency hell :3

@DetailsMatterM DetailsMatterM mentioned this issue Nov 29, 2022
Closed
@rndevfx rndevfx closed this as completed Nov 29, 2022
@rndevfx
Copy link
Author

rndevfx commented Nov 29, 2022

Fixed

@burdickjp burdickjp mentioned this issue Oct 9, 2023
Closed
@BentHaase BentHaase mentioned this issue Oct 10, 2023
Closed
@karkusviktor karkusviktor mentioned this issue Mar 15, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@NightHammer1000 @rndevfx @leohearts