Plex Media Server for armhf (arm64) Debian / Ubuntu: Beta Packages

@bahia I do not have character encoding issues since 1.1.4. My 1.2.2 Raspberry Pi installation does not have any problems. Maybe it’s an issue in the Samsung TV app (I do not use it)? Do you use the old community client or the official new Samsung client?

I don’t know. I use the app I could install in Smart Hub. I believe, I can’t install something new, because it is an older TV (from 2010 or so). But the strange thing is: It worked without any problem. I didn’t change the TV neither the app in the TV. And suddenly I encountered this issue. I found other users here in the forum with the same problem, but they’ve got no answer… :frowning:

Here is 1.2.3.

Here is the DVR Beta Three.

I chose package version 1.2.100, so public 1.2.x updates won’t remove the DVR Beta and public 1.3.x updates will install automatically nonetheless. Disclaimer: I did not test this version, as I do not own any supported DVR device.

@bahia, I have Samsung 2013 with Orca’s smart tv app and have not been having the character issue since 1.1.4. Do still have the problem with your setup? What Pi do you have? Can you post a picture of the problem? Just wondering if your problem is the same as we had.

Here is a photo. Not very good, but it may work… You see:
»& #246;« is »ö«,
»& #252;« is »ü«,
»& #223;« is »ß«
»& #8222;« is somethig else (don’t know what).

This issue was not before PLEX 1.x

@bahia Your client is faulty. The screenshot proofs that the Plex Media Server performs the correct XML encoding. The client is responsible for replacing the numeric character references with real characters.

This is strange. The client was not faulty before PLEX arrived at version 1.x
The question is now: How can the client change when the server software changes? Or this: If the server software changes and a problem appears, is this the client’s fault?

@bahia Related.

Here is 1.2.4.

@uglymagoo Thanks for the hint. This means, the problem is known and real, but there is no hope. In the meantime I had an Amazon Fire-Stick with the new PLEX-App. There the encoding is OK, but the App is not good at all. So I’ll learn to take it as is…

@uglymagoo any chance you can add the 1.2.6 version here? I am too new at linux to add the auto update to the repository (I tried and I must have done something wrong since it did not work)

@espinooo said:
@uglymagoo any chance you can add the 1.2.6 version here? I am too new at linux to add the auto update to the repository (I tried and I must have done something wrong since it did not work)

Auto-update (i.e. downgrade) from DVR Beta 3 to 1.2.x is intentionally disabled. If you want to move from the DVR Beta to the stable 1.2.x releases, just uninstall plexmediaserver-installer and install again from my repo.

@uglymagoo I just wanted to let you know that linuxserver’s docker container is using your installer package, which works really well.

I also wanted to let you know that linuxserver’s x86 docker container has a really cool updater script for plexpass, which I believe your installer package could benefit from in terms of getting the plexpass releases without breaking any plex rules.

It retrieves the token from the plex preferences.xml, uses that to login to the plex downloads page, and then gets the latest plexpass release. It doesn’t break the rules, because the user has to be a plexpass subscriber for it to work.

Here’s the script:https://github.com/linuxserver/docker-plex/blob/master/root/etc/cont-init.d/50-plex-update
It also allows for pulling a specific version.

The one thing that wouldn’t work out of the box is that your installer runs before plex is even installed, so there would be no preferences.xml (the token gets created after login) but perhaps your installer can come with a command that triggers the “update”, that way it can be put into a cron or a startup script (our docker container would run it during container start)

Just an idea. . .

Here is 1.3.0.

Hi there @uglymagoo , is there something wrong with the dev2day.de (I’m getting unable to resolve host) or the deb files (the 1.3.0 have 3K is that correct? And I’m receiving an structure error when I tried to dpkg -i : structure needs cleaning)

@fernandoavc said:
Hi there @uglymagoo , is there something wrong with the dev2day.de (I’m getting unable to resolve host)
dev2day.de is fine, I just checked
( or the deb files (the 1.3.0 have 3K is that correct?
Correct.
And I’m receiving an structure error when I tried to dpkg -i : structure needs cleaning)
Filesystem error as far as I know. It’s not the package, it’s your system :slight_smile:

@uglymagoo said:

@fernandoavc said:
Hi there @uglymagoo , is there something wrong with the dev2day.de (I’m getting unable to resolve host)
dev2day.de is fine, I just checked
( or the deb files (the 1.3.0 have 3K is that correct?
Correct.
And I’m receiving an structure error when I tried to dpkg -i : structure needs cleaning)
Filesystem error as far as I know. It’s not the package, it’s your system :slight_smile:

Hey @uglymagoo you’re perfectly right, the file worked out and my system is behaving strangely… Not sure what the problem is (if it’s my raspberry pi or the Plex itself) but something is wrong with my system not your package. Thanks for the awesome work!!!

Here is 1.3.1.

Here is DVR Beta 4.