The wikis are now using the new authentication system.
If you did not migrate your account yet, visit


Jump to: navigation, search
Please refer to Help:Editing in order to write a quality approved article.

JRiver MediaCenter Setup on Tumbleweed

Download and Install

Either i586 or x86-64 MC should work on TW. If you're upgrading from an existing MC, I recommend backing up the library. At this point, you could also remove the existing MC version if so desired. After the install completes successfully, you can then restore the library backup and restart MC.

The easiest way to get going is to use the "alien" utility to convert the ".deb" to a RPM package. Using this method, you can easily install/remove different MC builds at your convenience and if you have a local folder set up as a repo, MC can be managed easily with the Yast software manager.

  • Find and install alien for your openSUSE version (
  • Download the MC .deb
  • From the .deb location, run sudo alien -r --scripts "<filename>" where <filename> is the downloaded .deb file. This will take a couple of minutes, the resultant RPM will be in the folder from which you ran alien.
  • Install the RPM: sudo zypper in -f "<filename>" where <filename> is the resultant RPM.
  • You might see an error from zypper:

Problem: mediacenter24-24.0.74-2.x86_64 requires, but this requirement cannot be provided not installable providers: syslog-ng-3.19.1-2.1.x86_64[repo-oss]

Solution 1: deinstallation of systemd-logger-239-4.2.x86_64
Solution 2: do not install mediacenter24-24.0.74-2.x86_64
Solution 3: break mediacenter24-24.0.74-2.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c):

  • If so, choose option 3 to continue the install.

You will probably also receive a message indicating that the rpm is not signed, since it was created with alien. Choose (i)gnore to continue the install.

Optionally, if you have a local folder set up as a repo, copy the resultant RPM to that folder and use Yast/Software Management (or run sudo zypper dup) and it should get picked up to install.

CA Certs on Tumbleweed

Suse has moved the ca-certificates.crt to /var/lib/ca-certificates/. Sometimes an update to TW will remove the ca-certificates.crt (symlink) in /etc/ssl/certs/. If you leave the default MC install, the symlinks will work as long as the link remains in /etc/ssl/certs/. Of course, this can be added easy enough after any update to TW that might remove it. In addition, you could change the MC symlink.

  • MC link => /etc/ssl/certs/ca-certificates.crt
  • CA-CERTS => /var/lib/ca-certificates/ca-bundle.pem

Tested Versions

This method has been tested/used on versions 21-26 of Media Center

Font Manager Issues

If you are using a non-standard repo for font enchancments in TW, you most likely will experience segfaults with MC in both 32-bit and x86-64. In short, I believe it to be related to the harfbuzz version mismatching due to the use of newer versions in the freetype2 libs used by the enhancement repos, etc.

Regardless, if you're experience startup segfaults with MC, remove the font enhancement repos, zypper dup, and then try MC again. TW itself could someday roll an incompatible version itself, so just something to look out for. Base Leap repos should be fine.

Note that MC does not directly link against freetype or harfbuzz, but only pango and pango-ft2, so if you can get those compatible with your different font libraries, MC should pick that up.

External links