Installed jriver mediacenter 33 on my new Zorin 17.3 pro installation last week. It installed fine using jriver procedure and was playing fine. After 2 hours I closed the app and shutdown my system. When I returned the following day, jriver would not start from Dash or Main menu. I tried starting app from Terminal and got "Segmentation fault". I am a relative newbie to Linux and would appreciate any help (as simple as you like) to rectify this problem.
Hi, welcome to Zorin OS!
The big question first would be: how did you install this program? I've also found a few similar instances of this issue over at their own forums, so it may be an issue with how it works under Linux.
For now, try to switch your login session from Wayland to Xorg. To do that, you need to log out of your account, and use the wheel icon on the lower right corner to select "Zorin Desktop" as per this screenshot:
I can't say I've ever heard of this media centre. What I would say is, if like zenzen said, that a lot of users are running into the same issue, it may be a software issue with Linux. Might be worth a post over there as well, or at least checking it out.
I haven't used a media player in a while, but I used to use XBMC (I guess it's called Kodi now). That was quite a feature-rich media centre that is open source, so if you're willing to give another one a shot, that might be worth a look as well.
Hi, thanks for your quick response. I had posted my problem first on jriver forum. They suggested trying to start app from terminal, which I tried to do but received the segmentation error. They also informed me that they don't support Zorin and tried to steer me to a more sane OS (their words). I changed over to Xorg as you suggested but it made no difference...still says Segmentation fault.
May I suggest that you switch to a more sane media player? 
Zorin OS 17.3 is based on Ubuntu 22.04, so it should be similar enough that it should work nonetheless. What I'm still interested is in how did you install it? It seems the only option is through their own repositories but there are several versions to choose from (stable, latest and beta).
EDIT: It looks like is this thread maybe? Another user just added a reply to report that it is working for them:
In any case, try to run this command in the terminal right after you attempt to launch Mediacenter again, and fails:
journalctl -xe
Followed your advice and tried to start jr followed by your terminal command and got the following-
Apr 17 19:51:26 minis com.google.Chrome.desktop[3283]: [2:2:0417/195126.340066:ERROR:a>
lines 2361-2383/2383 (END)
Apr 17 19:51:20 minis systemd[1]: Starting Download data for packages that failed at pa>
░░ Subject: A start job for unit update-notifier-download.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit update-notifier-download.service has begun execution.
░░
░░ The job identifier is 1981.
Apr 17 19:51:20 minis systemd[1]: update-notifier-download.service: Deactivated success>
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit update-notifier-download.service has successfully entered the 'dead' state.
Apr 17 19:51:20 minis systemd[1]: Finished Download data for packages that failed at pa>
░░ Subject: A start job for unit update-notifier-download.service has finished successf>
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit update-notifier-download.service has finished successfully.
░░
░░ The job identifier is 1981.
Zenzen...I used a new simplified procedure by BryanC which downloaded the latest stable version.
Edit by zenzen to add BryanC's response over at the jriver forum:
You likely have a bad file, the Linux MC build is more prone to "choking" on bad files and causing crashes. To start from scratch you will want to remove your library
rm -rf ~/.jriverand then relaunch MC. Enable logging and as you import files you should be able to pinpoint which file(s) is causing the issue.— JRiver 33 installed in Zorin os 17.3 won't re-open after shutting down.
1 Like
I've updated your last reply to add a little formatting to the output (not showing the issue anyway) and to add the reply that you're referring to, in case someone else walks into this thread in the future. For now, I'll label it as the solution since it seems to be an issue with the software itself.