Plex Home Theater 1.3.2 Debian build

I have updated my build of Plex Home Theater to the lastest release 1.3.2. All the builds from 1.3.0 onward had connection problems with my server. I have now changed to a different packaging by adapting the one from Plex for Ubuntu to the Debian standard. With this, I can finally use the PHT on my linux box again.

This post is outdated, please see Plex tag for the most recent release!


As before, here is a source package, and a binary build for amd64, ready to be used on Debian/jessie or sid. If you want to give it a try, add the following lines to your sources.list:

deb pht/
deb-src pht/

You can also grab the binary for amd64 directly here: here, you can get the source package with


The release file and changes file are signed with my official Debian key 0x860CDC13.


Email this to someonePrint this pageShare on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInFlattr the author

4 Responses

  1. bitbox says:

    Hi Norbert,

    I’m impatient to be able to test Plex Home Theater on my Debian/Cinnamon laptop. Unfortunately, after adding the two repo lines in my apt sources files (I added an /etc/apt/sources.list.d/plexhometheater.list file containing your repo). I’m stuck with a GPG error when I run apt-get update saying:

    W: GPG error: pht/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6CACA448860CDC13

    I looked around and tried the following to add your key:

    gpg --keyserver --recv-keys 0x09C5B094 && gpg --armor --export 0x09C5B094 | apt-key add -

    Which apparently installed your key (here is the output of a re-run of the previous command)

    gpg: requesting key 09C5B094 from hkp server
    gpg: key 09C5B094: "Norbert Preining " not changed
    gpg: Total number processed: 1
    gpg: unchanged: 1

    But it didn’t help, I still get the damned public key is not available warning when issuing an apt-get update command.

    Could someone please point me in the right direction ?

    • Hi,
      thanks, that was a stupid typo of mine. The key id you used (and what I wrote!, but now it is fixed), was my old 1024bit DSA key, which has been phased out.

      You need to the same gpg… | apt-key incantation with the new key 0x860CDC13

      Sorry for the inconveniences.

      I also tried to get 1.3.5 running, without success, nothing is ever played 🙁

  2. obeone says:

    Hi Norbert,
    Sorry for my english but now when I try to update I have this message:
    W: Erreur de GPG : jessie InRelease : Les signatures suivantes ne sont pas valables : KEYEXPIRED 1486379356
    So I understand I have to update the key but where can I found it ?

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>