Server Version#: 1.41.4.9463
Player Version#: 4.143.0
I’m attempting to upgrade my system from LinuxMint 21.3 to 22. During the pre-check, it tells me that the Plex “repository is not explicitly supported for this version of LinuxMint”, lists this repository https://downloads.plex.tv/repo/deb/ public main, and tells me to disable the repository before proceeding.
Is the current version of Plex explicitly not supported under LM22? When I first installed Plex, I did so via download of the deb package and installing via apt.
From prior discussions, I recognize that LinuxMint is frowned upon for use with Plex but I’ve been using it for several years and prior versions of LinuxMint without issue and would like to keep doing so. I’m technically competent with Linux and just want to confirm that going forward would not somehow eliminate ability to receive support.
There’s difference in meaning between “not explicitly supported” and “explicitly not supported.” The former means that there’s no stated support for it. The latter means that it’s specifically called out as not being supported. PMS on Linux Mint would be an example of the former.
Plex Media Server explicitly supports Debian, Ubuntu, Fedora, CentOS, and SUSE, with appropriate minimum versions. Linux Mint is not listed, so it’s not explicitly supported. (Note that I’m referring to the native packaging here.)
Experience on these forums suggests that should you run into issues (problems with transcoding, stability or performance problems, etc.) you’ll likely be asked to reproduce the issue in a supported environment, i.e. on one fo the platforms listed above. That’s if the problem isn’t easily resolved.
@pshanew I do understand the difference. However, I do not recall encountering this with any previous upgrade experience so it made me want to get some clarification on this and understand why I would be seeing this with this particular upgrade.
Sorry, only now saw this response. I was successfully updated the system to LinuxMint 22 and Plex Server v 1.41.5.9522 appears to be working without issue.
NOTE: For the LM upgrade to proceed, I just had to comment out the apt entry for checking the plex repository. The upgrade completed successfully, I uncommented the apt entry for the plex repository, and all seems fine. For those who might be using LM, I’ll report back if anything undesired occurs.
Ah, good to know; thank you. In my case, I’ve not had any negative experiences with it but I’m running the server only for my own local use (in-house). So, that may be a consideration.
I’ll plan to do some load testing. I have several systems where I can install the client and see at what point I experience “weird, inexplicable, random failures”.
Would these be mostly drops in the video? For what else would you suggest I check?
I was once helping a user with a NAS mount and a local HDD mount.
We’d setup the NAS mounts and they were working.
We then added the USB HDD to mount using the blkid (UUID string)
The drive would not mount via /etc/fstab but would mount manually.
Rebooted the machine.
Upon logging in, we discovered the drive mounted as it should but the NAS mount didn’t mount.
We had to manually kick the NAS to mount which it did without error
Rebooted again and both mounted.
A few days later, the user let me know that the NAS wasn’t mounting again.
This is the kind of flakiness I see
A friend of mine was using Mint as his desktop. Great UI but in the middle of the day, it would often reboot without warning. Journal / system logs showed no reboot commands so something had triggered the ‘back door’ reboot.
Both that user and my friend switched to Debian, then Ubuntu. Haven’t had a problem since.
Wow, crazy. I’ve never experienced anything like that. I have experienced a couple minor issues but in every instance I recall, I found the solution on the Ubuntu forum – meaning they weren’t LM specific but the underlying Ubuntu distro.
In any case, I’ll do some load testing by spinning up some additional systems and see what I find.
