Package Details: plex-desktop 1.109.0.329-1

Git Clone URL: https://aur.archlinux.org/plex-desktop.git (read-only, click to copy)
Package Base: plex-desktop
Description: Plex desktop client for linux
Upstream URL: http://plex.tv
Keywords: media player plex
Licenses: unknown
Submitter: ludvigHz
Maintainer: username227
Last Packager: username227
Votes: 18
Popularity: 0.089534
First Submitted: 2022-05-26 10:36 (UTC)
Last Updated: 2025-05-14 11:47 (UTC)

Required by (0)

Sources (5)

Pinned Comments

mrgrim commented on 2024-10-01 05:16 (UTC) (edited on 2024-10-01 05:20 (UTC) by mrgrim)

The Qt 6.7 problem is an issue where xdg-open inherits the environment of the Plex app causing kde-open to try to load the Qt 6.6 libraries from /opt/plex-desktop/lib due to the LD_LIBRARY_PATH set in Plex.sh.

This can be solved by editing the RUNPATH of the binaries using chrpath then removing the LD_LIBRARY_PATH line from Plex.sh. It turns out The main Plex library has a working RUNPATH but includes a bunch of automation cruft. The transcoding binary does NOT have it set, and QtWebEngineProcess needs no changes. In /opt/plex-desktop/bin run:

chrpath -r '$ORIGIN/../lib' Plex
chrpath -r '$ORIGIN/../lib' Plex\ Transcoder

However, this only exposes additional issues with all of the Qt environment variables set in this script. I couldn't find a super clean way to fix this, but interestingly enough KDE uses a little utility for their AppImage deployments to deal with this exact problem:

https://invent.kde.org/brauch/appimage-exec-wrapper/

Compile it and copy the exec.so file into /opt/plex-desktop/lib then alter Plex.sh like this:

https://gist.github.com/mrgrim/1357da402f8ceccaf8224e145fa6acc3

This could even allow using LD_LIBRARY_PATH and not using chrpath. The choice is yours. Using chrpath seems cleaner but pulls in a dependency.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 Next › Last »

ben2talk commented on 2023-07-30 02:55 (UTC)

Now we should go with plex-HTPC Flatpak I believe.

vagelis commented on 2023-01-28 11:08 (UTC)

@ludvigHz yes I was referring to the snap package. Thanx for the guidance I'll check the plex forum

BIL4X4 commented on 2023-01-27 02:33 (UTC)

I do not have any sound anymore. does anyone else have this issue?

ludvigHz commented on 2023-01-16 14:43 (UTC)

@vagelis I hope you are not referring to the snap package? As that has nothing to do with this AUR package. Issues with official packages should be reported directly to plex (via their forums f.ex.)

If you are referring to this package, then any audio issues you have are dependent on your system configuration and audio setup. Volume control in the plex app works just fine for supported audio interfaces.

vagelis commented on 2023-01-16 14:05 (UTC)

plex-desktop when installed from snap in Arch Linux, volume control is inconsequential, meaning your roll it up and down and does nothing to the volume.

ludvigHz commented on 2022-12-14 16:32 (UTC)

For anyone wondering why this is out of date.

I've been trying to make the latest version of plex-desktop work here. But sadly have an issue with it getting stuck at the first loading screen with no error logs anywhere. If anyone can help out, please do! They have updated FFMPEG, MPV (and maybe QT) and their forks are no longer binary compatible with the arch packages, requiring the use of the forked versions included in the package.

(The same issues are valid for plex-htpc since they're essentially the same app)

Bobyl commented on 2022-11-24 19:51 (UTC)

@ludvigHz thank you for pinpointing the issue, using QT_QPA_PLATFORM=xcb did the trick. Thanks !

ludvigHz commented on 2022-11-24 17:01 (UTC)

Could you try running with QT_QPA_PLATFORM=xcb and see if that changes things? Considering you are on plasma, your environment might be set to use QTs wayland backend by default.

Bobyl commented on 2022-11-24 07:35 (UTC)

@matt17br plex-desktop is a snap image, so there is no real rebuilding to be done here. However, I just tried rebuilding plex-desktop: it doesn’t solve the segfault when using wayland instead of X11.

I just tried on a computer with an Nvidia dGPU: same issue.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 Next › Last »