Print

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

[anonymous]

My music systems that were working on Debian 12 that I updated to Trixie are working fine, but on my main system I did a fresh install of Trixie and mediacenter appears to have no internet access, though everything else works fine. Using X11 Gnome in all cases, went through new installs fixing libwebkit2gtk-4.0-37 issue, but no luck. On another new install tried installJRMC, but only a blank screen is shown. Ran debug in all cases and no output. Perhaps the industry switch to Wayland is resulting in not-up-to-snuff X11 compatibility?

Tried installJRMC on my laptop with endeavouros and it worked fine. Did try other linux distros too, though I know they're unsupported and got the same not-good result.

Suggestions?

Looking forward to when JRiver to switches to Wayland.

[anonymous]

Forgot to mention I tried opening the ports and even disabled the firewall and still the same result - blank page

[Awesome Donkey]

Try to enable logging and reproduce the issue and post the log here. Maybe a dependency is missing/changed in Trixie?

Looking forward to when JRiver to switches to Wayland.

I don't think this is happening anytime soon. For one, Xfce (Bob's desktop environment of choice) would have to support Wayland and that's still years away from happening. Media Center does run on Wayland through XWayland, though there may be issues here and there like small dialog boxes.

[mwillems]

Try to enable logging and reproduce the issue and post the log here.

I don't think this is happening anytime soon. For one, Xfce would have to support Wayland and that's still years away from happening. Media Center does run on Wayland through XWayland, though there may be issues here and there like small dialog boxes.

So folks have been experiencing some some intermittent connectivity problems with JRiver's servers due to a server switch since yesterday:  https://yabb.jriver.com/interact/index.php/topic,140860.msg977728.html#new

This might be complicating new installs that need to download components.  If everything but web access is working I'd bet that's the issue. My understanding is that it should resolve in a day or so.

See also: https://yabb.jriver.com/interact/index.php/topic,140942.msg977729.html

[Awesome Donkey]

If that's the case, try setting Debian to use Google DNS as the system DNS and see if that clears it up.

[anonymous]

Thank you for the quick replies!

Just tried to enable logging on my eight or ninth OS install and it works. It appears the JRiver server was was much more down than up yesterday, but that prohibited me from setting up my JRemote which was all I cared about. So, a suggestion going forward would be to eliminate the requirement to speak with a JRiver server to enable JRemote via an access key.

On another topic, is Xfce on Debian the testing/building environment? Thought Gnome, so just checking since I want to use whatever you do.

Thanks again for the quick reply.

[bob]

Thank you for the quick replies!

Just tried to enable logging on my eight or ninth OS install and it works. It appears the JRiver server was was much more down than up yesterday, but that prohibited me from setting up my JRemote which was all I cared about. So, a suggestion going forward would be to eliminate the requirement to speak with a JRiver server to enable JRemote via an access key.

On another topic, is Xfce on Debian the testing/building environment? Thought Gnome, so just checking since I want to use whatever you do.

Thanks again for the quick reply.

XFCE

[mwillems]

Just tried to enable logging on my eight or ninth OS install and it works. It appears the JRiver server was was much more down than up yesterday, but that prohibited me from setting up my JRemote which was all I cared about. So, a suggestion going forward would be to eliminate the requirement to speak with a JRiver server to enable JRemote via an access key.

So just FYI the whole point of the access key is that it pings JRiver's servers so the servers can automagically supply the IP address of the local jriver instance to the client (both internal and external IP address).  The access key allows JRiver's servers to perform IP matchmaking between JRemote or other clients and local JRiver instances so they can find each other successfully.  For that reason, the access key requires JRiver's servers to work at all; it's an internet enabled service that JRiver provides to make it easier to use remotes or otherwise connect JRiver instances.

If you want to avoid pinging JRiver's servers you can assign your server a static IP address (in your router), and then you can manually enter that IP address into JRemote. Then you'll have no trouble when JRiver's servers are unavailable.  It's more trouble to setup on the user's end, but it can let you keep using remotes when JRiver's servers are temporarily unreachable.  For example, I use a manual IP setup and had no JRemote or Gizmo trouble yesterday even when JRiver's website was inaccessible to me.

[JimH]

The Access Key routine running on your computer checks the IP addresses on your machine periodically and updates our servers.  The main reason to do this is that addresses can change.  If you reboot your router, it will probably change, for instance.  The Access Key will reflect this within a few minutes.