Package Details: plex-desktop 1.105.1.257-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
Licenses: unknown
Submitter: ludvigHz
Maintainer: huyz (username227)
Last Packager: username227
Votes: 17
Popularity: 0.029449
First Submitted: 2022-05-26 10:36 (UTC)
Last Updated: 2024-11-25 13:35 (UTC)

Required by (0)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

electronarchy commented on 2024-07-16 19:18 (UTC) (edited on 2024-07-16 19:55 (UTC) by electronarchy)

@username227, yes, that was the first thing i checked. it was already installed. reinstalling didn't fix. i also was initially on kde-unstable and arch testing repos, and i rolled back to the standard repos and cleared yay's cache and rebuilt this AUR package. still no dice. and kde-open seems to work fine otherwise (kde-open archlinux.org works as expected)

edit: for the time-being i have found a workaround-- install xfce4, switch to xfce session, sign in to plex, logout, uninstall xfce4 ;)

username227 commented on 2024-07-16 19:10 (UTC)

@electronarchy,

Please try installing the package qt6-base from extra and let me know if it then works. If it works to solve the problem, I will add this to the depends. Thanks.

electronarchy commented on 2024-07-16 19:02 (UTC) (edited on 2024-07-16 19:02 (UTC) by electronarchy)

i can't sign into my account. when i click the "Sign in" button i get this error and 11 others just like it with different required-by's:

kde-open: /opt/plex-desktop/lib/libQt6Core.so.6: versionQt_6.7' not found (required by kde-open)`

SprobbyBlongo commented on 2024-07-03 20:30 (UTC)

@username227

Thats really odd. Im also amd/nvidia on plasma 6.1. I am using the latest drivers from nvidia. I wonder if its maybe one of my other kernel paramaters, ill have to do some experimenting.

username227 commented on 2024-07-03 20:27 (UTC)

@SprobbyBlongo

I have amd/nvidia. for nvidia i'm using proprietary and nvidia-drm.modeset-1. amd is integrated. I use optimus manager to switch which doesn't work on wayland, but does switch out globally, and it appears to work on wayland with on both GPUs.

SprobbyBlongo commented on 2024-07-03 20:18 (UTC)

@username227

Interesting. I am using an Nvidia GPU with proprietary drivers and the following kernel parameters:

nvidia-drm.modeset=1 nvidia-drm.fbdev=1 nvidia.NVreg_EnableGpuFirmware=0

Are you using amd or intel graphics?

username227 commented on 2024-07-02 18:32 (UTC)

@SprobbyBlongo,

I cannot replicate. Just successfully ran on Wayland and even successfully played a show.

SprobbyBlongo commented on 2024-07-02 16:41 (UTC) (edited on 2024-07-02 16:42 (UTC) by SprobbyBlongo)

This works fine in an X11 session but not with wayland. Not sure if this is just a me thing but when I open it in terminal this output just goes on forever:

qt.scenegraph.general: Using QRhi with backend OpenGL Graphics API debug/validation layers: 0 QRhi profiling and debug markers: 0 Shader/pipeline cache collection: 0 qt.scenegraph.general: Using QRhi with backend OpenGL Graphics API debug/validation layers: 0 QRhi profiling and debug markers: 0 Shader/pipeline cache collection: 0 [46627:46672:0702/094221.271969:ERROR:gl_context_egl.cc(277)] eglCreateContext failed with error EGL_BAD_CONTEXT [46627:46672:0702/094221.271980:ERROR:gpu_channel_manager.cc(771)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. [46627:46672:0702/094221.271983:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context [46627:46672:0702/094221.271988:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub

username227 commented on 2024-06-24 18:32 (UTC) (edited on 2024-06-24 18:33 (UTC) by username227)

@samuel-emrys - I just pushed an update to fix the error. The update to ffmpeg7 broke plex. ffmpeg6.1 is now an AUR package and is required to run this. ffmpeg6.1 and ffmpeg packages can coexist, so this should be fixed now.

username227 commented on 2024-06-23 03:27 (UTC)

@samuel-emrys - I just spent the past hour trying to figure out what the problem is, as it was working fine two days ago but now I can confirm your error. I believe the problem was the recent update from ffmpeg6.1 to ffmpeg7.0. However, I cannot downgrade to test because i'll end up in a dependency nightmare. Hopefully @huyz can push a fix for this.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »