Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bob]

Since MC is complied on Debian and the libraries are used are the same on Ubuntu which is derived from Debian, you can add the repo manually without any additional software.
For MC33 this applies to Debian Bullseye (11), Bookworm (12) and Trixie/Testing (13) also for Ubuntu Focal (20), Jammy (22) and Noble (24)

For Debian only, the user may not be added to sudoers on a basic install.
If you get an error with sudo in the commands below, you can do the following in a terminal as the login user so the sudo commands work:

Code: [Select]

su -(you will enter the root password that you used when creating the system)

Code: [Select]

usermod -a -G sudoers youruserloginname(replace youruserloginname with the user name you logged in with)
exit
(to get out of the su -)
Then logout and log back in so that the change to sudoers works.

In a terminal as the login user, install any necessary dependencies:

Code: [Select]

sudo apt update && sudo apt install -y wget apt-transport-https -y gpg -y
Get and install the MediaCenter repo gpg key into a secure keyring:

Code: [Select]

wget -O- http://dist.jriver.com/mediacenter@jriver.com.gpg.key | gpg --dearmor | sudo  tee /usr/share/keyrings/jriver-com-archive-keyring.gpg >/dev/null 2>&1
Create a repo list file
For Focal:

Code: [Select]

echo "deb [signed-by=/usr/share/keyrings/jriver-com-archive-keyring.gpg arch=amd64,i386,armhf,arm64] http://dist.jriver.com/latest/mediacenter/ focal main" | sudo tee /etc/apt/sources.list.d/jriver.list
For Jammy:

Code: [Select]

echo "deb [signed-by=/usr/share/keyrings/jriver-com-archive-keyring.gpg arch=amd64,i386,armhf,arm64] http://dist.jriver.com/latest/mediacenter/ jammy main" | sudo tee /etc/apt/sources.list.d/jriver.list
For Noble:

Code: [Select]

echo "deb [signed-by=/usr/share/keyrings/jriver-com-archive-keyring.gpg arch=amd64,i386,armhf,arm64] http://dist.jriver.com/latest/mediacenter/ noble main" | sudo tee /etc/apt/sources.list.d/jriver.list
For Oracular:

Code: [Select]

sudo curl http://dist.jriver.com/latest/mediacenter/mediacenteroracular.source -o /etc/apt/sources.list.d/mediacenteroracularlatest.source
For Bullseye:

Code: [Select]

echo "deb [signed-by=/usr/share/keyrings/jriver-com-archive-keyring.gpg arch=amd64,i386,armhf,arm64] http://dist.jriver.com/latest/mediacenter/ bullseye main" | sudo tee /etc/apt/sources.list.d/jriver.list
For Bookworm:

Code: [Select]

echo "deb [signed-by=/usr/share/keyrings/jriver-com-archive-keyring.gpg arch=amd64,i386,armhf,arm64] http://dist.jriver.com/latest/mediacenter/ bookworm main" | sudo tee /etc/apt/sources.list.d/jriver.list
For Trixie:

Code: [Select]

echo "deb [signed-by=/usr/share/keyrings/jriver-com-archive-keyring.gpg arch=amd64,i386,armhf,arm64] http://dist.jriver.com/latest/mediacenter/ trixie main" | sudo tee /etc/apt/sources.list.d/jriver.list
Note that you will be getting the same build of MediaCenter in all cases. The only difference is the repo name for your convenience.

To get the stable branch instead you can just replace "latest" in the code above with "stable"

Then to install MediaCenter simply:

Code: [Select]

sudo apt update
sudo apt install mediacenter33

[HTPC Videophile]

Please provide "official" support for widely used rpm based distros like fedora/red-hat/centos  too instead of just debian. One simply cannot change a distro/desktop (which one chooses according to one's professional  needs ) for an entertainment software .

[Awesome Donkey]

JRiver only officially supports Debian (and I guess Ubuntu to an extent due to Ubuntu repos existing), but using it on any other distro is technically 'unsupported'. Third-parties maintain packages and methods of installing Media Center on non-Debian platforms like Arch (via AUR) and Fedora (installJRMC script and repo). And that's probably as good as it's going to get for them.

If you want to install it on Fedora (or CentOS) use the installJRMC script. Otherwise I wouldn't expect JRiver to offer things like RPM files for distros they don't support. I would be very surprised if that ever changed.

[HTPC Videophile]

JRiver only officially supports Debian (and I guess Ubuntu to an extent due to Ubuntu repos existing), but using it on any other distro is technically 'unsupported'. Third-parties maintain packages and methods of installing Media Center on non-Debian platforms like Arch (via AUR) and Fedora (installJRMC script and repo). And that's probably as good as it's going to get for them.

If you want to install it on Fedora (or CentOS) use the installJRMC script. Otherwise I wouldn't expect JRiver to offer things like RPM files for distros they don't support. I would be very surprised if that ever changed.

   After much reluctance, I tried installing JRiver ver 33.15 on  Fedora  40 with Jrmc . Everything went well initially but after the library  building , it gave a Segmentaion fault (core dumped) . As it's confirmed  by other members that there's no scope for official rpm support, i did not bother to report. Simply uninstalled JRiver and did a clean reinstall of  Fedora.

When i say official support, i refer to  JRiver's stake regarding security risk which comes from  unofficial resources. Of course anyone can rebuild rpm from deb but one cannot review third party (or more correctly just a helpful , volunteering member's installation scripts everytime.

[syndromeofadown]

I have been using fedora for a while with MC without issue, but mostly for fairly basic things. I do not like ubuntu, and Debian has given me issues in the past with not supporting new hardware. Soon i plan on moving a server and 4 clients from Windows to fedora. A winter project. When i do this i will be using more featues, and I will have a much larger library. Perhaps I will run into the issues you had, but hopefuly not. I will do a post about it. If I have success maybe you can give fedora another shot. If i do not have success I will probably try Mint as it has worked well in the past. Windows is leaving one way or another.

[Awesome Donkey]

Diagnosing segfaults can be a pain. Usually in those cases I'd make a backup of the hidden .jriver folder (that's in your home directory), delete it and start again and hope it doesn't start happening again.

[guycarmin]

I would love an official repo for Fedora as well...

[Awesome Donkey]

I would love an official repo for Fedora as well...

There isn't one, but there is a third-party one maintained by the installJRMC author that's added and used when using the installJRMC script. That's as good as it's going to get though.

[Awesome Donkey]

Bob, I forgot to mention this when Ubuntu 24.10 came out, but as of right now trying to add the jriver.list file will cause APT to error out and fail. This is because in Ubuntu 24.10 they've changed it where instead of the jriver.list file you need to now use a jriver.source file with the following contents...

Code: [Select]

Types: deb
URIs: http://dist.jriver.com/latest/mediacenter/
Signed-By: /usr/share/keyrings/jriver-com-archive-keyring.gpg
Suites: noble
Components: main

Otherwise if you try to use the jriver.list file you'll get this exact error from APT you won't be able to continue...

Code: [Select]

Error: The repository 'http://dist.jriver.com/latest/mediacenter oracular Release' does not have a Release file.

[bob]

Bob, I forgot to mention this when Ubuntu 24.10 came out, but as of right now trying to add the jriver.list file will cause APT to error out and fail. This is because in Ubuntu 24.10 they've changed it where instead of the jriver.list file you need to now use a jriver.source file with the following contents...

Code: [Select]

Types: deb
URIs: http://dist.jriver.com/latest/mediacenter/
Signed-By: /usr/share/keyrings/jriver-com-archive-keyring.gpg
Suites: noble
Components: main

Otherwise if you try to use the jriver.list file you'll get this exact error from APT you won't be able to continue...

Code: [Select]

Error: The repository 'http://dist.jriver.com/latest/mediacenter oracular Release' does not have a Release file.

So this started with 24.10 (oracular)?
I'll probably update the repo and make a new entry above.

[Awesome Donkey]

Yes, it did.

Seems they fully converted to the deb822 format with 24.10. I had issues with other apps that used .list files like Chrome and Edge and I had to manually fix those by replacing them with .sources as well when I upgraded.

https://repolib.readthedocs.io/en/latest/deb822-format.html
https://manpages.ubuntu.com/manpages/xenial/en/man5/sources.list.5.html#deb822-style%20format

[bob]

Yes, it did.

Seems they fully converted to the deb822 format with 24.10. I had issues with other apps that used .list files like Chrome and Edge and I had to manually fix those by replacing them with .sources as well when I upgraded.

https://repolib.readthedocs.io/en/latest/deb822-format.html
https://manpages.ubuntu.com/manpages/xenial/en/man5/sources.list.5.html#deb822-style%20format

Ok, so the new one should be ready to go and I added an entry above. I don't have that version to test so maybe someone else can and let us know.

[Awesome Donkey]

http://dist.jriver.com/latest/mediacenter/mediacenteroracular.source gives a 404 not found error.

[bob]

http://dist.jriver.com/latest/mediacenter/mediacenteroracular.source gives a 404 not found error.

I just click on the link above and it's fine for me.

[Awesome Donkey]

Just checked it again and it's giving a 404 again.

[bob]

Just checked it again and it's giving a 404 again.

Interesting, not for met.
#MC
Types: deb
URIs: http://dist.jriver.com/latest/mediacenter/
Signed-By: /usr/share/keyrings/jriver-com-archive-keyring.gpg
Suites: oracular
Components: main

[BryanC]

It was down for me earlier but it's working now.

[Awesome Donkey]

Still down/404 for me, hmm.

[bob]

Still down/404 for me, hmm.

What happens if you do a traceroute?

[bob]

It wasn't doing https. I noticed all of the existing configuration files use http. It's a legacy thing. I wonder if your browser or whatever was converting to https?? At any rate I made that work as well.

[Awesome Donkey]

Yes, all web browsers pretty much are in the process of always forcing HTTPS. Works good now, thanks!

[jcd201406]

Hi All,

Just upgraded debian from 'bookworm' to 'trixie' and after modifying jriver.list for 'trixie', I got a proposal message to transform jriver.list to jriver.sources with 'apt modernize-sources'.

It gives jriver.sources :

Types: deb
URIs: http://dist.jriver.com/latest/mediacenter/
Suites: trixie
Components: main
Signed-By: /etc/apt/trusted.gpg.d/jriver.asc

Got no answer for the URI, so I reverted back to .list and working fine now.

[antenna]

JRiver only officially supports Debian ...

Thank-you.  It is good to see that stated (officially?).

In some respects, my opinion is that Linux may be its own worst enemy with so many different distributions.  But that's a topic for a different thread ...

OK, now that JRiver only officially supports Debian (which, imo, is likely the most stable of the distributions, but again, likely a different thread), can someone please supply the other needs for such official support?

Which window managers has JRiver tested for using the Debian distribution?

One reason I ask is that I am currently using the Linux Mint version, LMDE6, which is based upon Debian and uses the Cinnamon window manager.

But after some routine OS/package update, Media Center suddenly stopped working.

So, I have the following requests:

1) please state a Linux distribution (Debian?) and window manager (Mate, Cinnamon, ?) that JRiver uses to test Media Center for proper operations.

2) Once (1) is achieved, please provide an official package for that distribution/window manager.  The current shell scripts, which seem to pull in things from wherever have issues when I run them.[1]

I have just been burned using Media Center on Linux Mint LMDE6 (with Cinnamon).

So, as I look for a replacement for LMDE6, please help me by providing the answers to the above questions.

thx.

1-

# sh ./installJRMC.sh --install local --compat -d
./installJRMC.sh: 19: shopt: not found
./installJRMC.sh: 21: declare: not found
./installJRMC.sh: 22: declare: not found
./installJRMC.sh: 23: declare: not found
./installJRMC.sh: 24: declare: not found
./installJRMC.sh: 25: declare: not found
./installJRMC.sh: 26: declare: not found
./installJRMC.sh: 28: declare: not found
./installJRMC.sh: 149: Syntax error: "(" unexpected (expecting "then")

.

[antenna]

... and, if I may add....

My reason for wanting a more reliable Linux version of Media Center centers upon the current PC I am using for Media Center inthe entertainment center here.  It is an old Windows 10 PC running Windows.

But, over the years, it has just worked.

Well, except for one occurrence ...

https://yabb.jriver.com/interact/index.php/topic,139707.msg968793.html#msg968793


To which I eventually replied ...

Yeah, the PC I use as a MC client in my entertainment center is not recent.  I plan to replace it next year to install a Win11-based replacement.

The current crop of Intel video chips seem to be quite good enough for my needs going forward.

Indeed, the current MC PC has an Intel video chip, but Intel stopped providing drivers for Win10.  So when I moved it from Win7 to Win10 that's when I switched to NVidia.  I had to get an old NVidia card for the old bus in the PC.

All this is to say the following...

The workaround you provided in a prior comment works quite well for me.

So... if I am the only person who noticed this issue, don't waste time trying to resolve the issue I had been seeing.

I'm good here.
[

 
So, I'm looking for a replacement of that old Win10 PC.

My experience with Media Center on Linux has not been a good one so far.

So, I may be stuck with Win11 ...   


 

[Awesome Donkey]

Bob/Jim/JRiver has said for years that only Debian is officially supported. In fact you'll see with every MC for Linux release topic here on the forums has for Debian in the title. That said I'd say that Ubuntu is either unofficially supported or semi-supported, as Bob added several Ubuntu repositories. Anything outside of Debian (and perhaps Ubuntu if it counts too) would be a sort of deal where if you have issues with installing or running, you may be on your own unless there's a third-party maintaining a package or something.

Linux Mint Debian Edition (LMDE) would be a bit on the fringe I'm afraid, so it may or may not work. If it doesn't work, you'll likely be on your own there. And I don't believe it's even tested with the installJRMC script either.

Speaking of, BryanC is the developer of the installJRMC script (and also maintains a third-party MC repository for Fedora), and generally the installJRMC script would be my recommended method of installing Media Center on any Linux distro be it Debian, Ubuntu, Fedora, Mint, OpenSUSE, etc. But LMDE may be an exception for that, probably better to use a more sane or "tried and true" distro like Debian or Ubuntu.

[bob]

MC is built on Debian (bullseye currently) with the XFCE desktop. That's the most lightweight and stable distribution as far as we are concerned.
The reason for building on this particular combination is that it still contains every library we need but is forward compatible with all versions of ubuntu which is totally based on debian and most of the older TLS distros that are still being supported.

Also the libraries are generic enough to work on non-debian distributions in general. The certificates.crt for SSL can be in different places in non-debian distributions so we handle that with a local copy that can be used if necessary.
If there are particular libraries we need, we add custom builds of them in the package.

Things to watch for are the noveau X server. That doesn't play at all with MC so alert for NVidia users.
Also wayland seems to cause issues we can't track down yet. We are using pretty basic X calls but the translation layer in wayland is less than perfect.