Arch Linux User Repository

@frank1x: I get that amdgpu.ids error on my new amd laptop. transcoding works from what I've tried. My error is

/home/runner/actions-runner/_work/plex-conan/plex-conan/.conan/data/libdrm/2.4.120-0/plex/main/build/73ee780ba6ea3ef381da6e7f229c475bfaf477ca/meson-install/share/libdrm/amdgpu.ids: No such file or directory

Another new error in journal I had was not having permission to create /usr/lib/plexmediaserver/.cache/mesa_shader_cache, weird I just made the folders and it went away. It has permissions, it runs as root. Oh well.

I don't use the docker version either. I do use docker stuff tho, but that's not it, as this is an existing install from my other intel laptop. I'll just ignore it.

@frank1x I think that error is benin and can be safely ignored. amdgpus.ids should contain a list of AMD GPU PCI ID numbers in the format VVVV:DDDD where V is the Vendor ID and D is the Device ID. You can probably find the file in the mesa or kernel sources and copy it in place (or just make it an empty file) if you want to supress the error.

I don't understand why I get the following error when transcoding with an AMD card, if it plays without problems, but the error still appears:

mar 24 08:23:58 archlinux plexmediaserver[273701]: /data/jenkins/conan_build/1113263720/conan/.conan/data/libdrm/2.4.115-3/plex/stable/build/73ee780ba6ea3ef381da6e7f229c475bfaf477ca/meson-install/share/libdrm/amdgpu.ids: No such file or directory
mar 24 08:23:59 archlinux plexmediaserver[273701]: /data/jenkins/conan_build/1113263720/conan/.conan/data/libdrm/2.4.115-3/plex/stable/build/73ee780ba6ea3ef381da6e7f229c475bfaf477ca/meson-install/share/libdrm/amdgpu.ids: No such file or directory
mar 24 08:23:59 archlinux plexmediaserver[325043]: /data/jenkins/conan_build/1113263720/conan/.conan/data/libdrm/2.4.115-3/plex/stable/build/73ee780ba6ea3ef381da6e7f229c475bfaf477ca/meson-install/share/libdrm/amdgpu.ids: No such file or directory

I don't use docker, just the installation of "yay -S plex-media-server" But that route seems to be from docker, I don't know.

@NoIdea, a good way to know you're doing something wrong in Linux is to run something as root or to set permissions to 777. The top of the plexmediaserver.service file explains the right way to do this. You should have a setup with a user per service, shared group and running w/ umask 002. Your existing folders should be 775 and folders 664.

# Be sure to use `systemctl edit plexmediaserver` to modify this service with an override.conf because
# direct changes will be overwritten by package updates.
#
# A user per service w/ shared group setup would have an override like:
# [Service]
# Group=sharedgroupname
# UMask=002

For those having trouble with seeing mounted drives due to user permissions this is how i fixed it

Made a new directory, below is my example, you can try a new directory in /mnt but i just wanted it separate personally

sudo mkdir /storage/NAS

change the mount point of the drive to /storage/NAS

Then i made permissions read/write for the whole folder, it is just media files so i was ok with these broad permissions. If you used a directory in /mnt be careful not to set anything else in mnt as 777

sudo chown -R 777 /storage

plex saw the folder fine and is able to delete from the filesystem as well, if you dont want to delete from inside plex you can chown 775 instead of 777

@jmarmstrong1207, negative, this is a configuration problem not a bug.

If it were possible to fix via PKGBUILD, it would be impossible to cover all possible configurations, so you have to use a configuration that will work within the restrictions created by your system. Otherwise, if your software didn't respect your configuration, your software could just do whatever it wanted, which would not be very safe. Unfortunately, the issue in this case is your disk configuration not Plex itself.

edit: alternatively, you can modify your local service file or add a .conf file that sets the user to be your user instead of 'plex' but I would generally advise against running background services connected to the internet under your user as it potentially exposes you to exploits via that service.

@techwiz I wonder, wouldn't it be better if PKGBUILD was modified so this permission problem didn't need to be manually fixed by the end user? e.g. Having the Plex server be run as the user instead of the 'plex' user. External drives are pretty common for a plex server setup.

@jmarmstrong1207, sounds like a permissions problem. KDE is probably mounting as your user while Plex is running as 'plex' user. Snapd I think might run the app under your user like it would if you launched it manually from cli.

I'd suggest manually mounting the drive and adding a line to /etc/fstab so you can just do 'sudo mount -a' when you plug it in to auto-mount using fstab rules.

Hey, I have an issue where the server cannot detect external drives mounted at /run/media/$USER/ by KDE. The Snap version of plexmediaserver sees them perfectly fine though. Do you know what the issue could be?

Please remove the out-of-date tag on this project. The provided package is the version mentioned in the out-of-date request.