Print

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

[Jodel]

I’m currently running Linux Mint 19 Tara:
Kernel: 4.15.0-38-generic x86_64 bits: 64 Desktop: Cinnamon 3.8.9

I recently updated JRiver to build 24.0.61.  I cannot ‘see’ any of my drives in the browse window when I select ‘Drives & Devices’, instead I get a message ‘Web page viewing is not yet supported on this platform’

I also use the same version of JRiver on the same PC booting to Windows 7 and it operates with no problems.

Has anyone else encountered this issue and is there any guidance as to how it may be resolved?  Any help would be much appreciated.

[Awesome Donkey]

What kind of drives are they? Internal drives? NAS shares? Something else? Also are they mounted in Linux Mint? If so, how are they mounted?

[Jodel]

Hi - these are all internal hard disks.  JRiver can't see any of them, including the boot drive. I've tried mounting them prior to starting JRiver, but it does not appear to make any difference.  I can navigate to any of the drives via the file manager, select a file and then choose to open it with JRiver.

My music drives / directories are successfully monitored by JRiver too, as I can browse albums etc. via the 'Audio' tab in the tree view.  It updates the contents quite happily as recent albums are captured and displayed, it is just that there is nothing to see in the 'Drives and Devices' tab.  Strange one!

[bob]

The explorer tab for drives and devices is only implemented on windows.
When CD ripping gets linux support the drives will show up there.

The browser should work on your 24.0.61 build. What happens when you click on the "Streaming" item in the tree?

[Jodel]

Hi Bob,

Thanks for your reply.

Unfortunately, neither 'Streaming' or 'Drives & Devices' seem to be working as I get the same ‘Web page viewing is not yet supported on this platform’ message when I try to open these items.

What seems really odd is that I can see all of the files listed under the 'Audio' item in the tree view, as all the sub-menus are working fine under that item.

[bob]

Hi Bob,

Thanks for your reply.

Unfortunately, neither 'Streaming' or 'Drives & Devices' seem to be working as I get the same ‘Web page viewing is not yet supported on this platform’ message when I try to open these items.

What seems really odd is that I can see all of the files listed under the 'Audio' item in the tree view, as all the sub-menus are working fine under that item.

Those particular pages use a browser view.
The 64 bit version DL's chromium for it's view the first time it's run. It's a pretty large DL.
I haven't tried your particular distro. Perhaps someone else can comment on that.
MC 64 bit is build on Debian Jessie for maximum compatibility.

[Jodel]

Thanks Bob,

I didn't notice if JR had downloaded Chromium when it first started - I'm not certain it did, so I loaded it up manually to see if that made any difference - no joy.

If I try starting JR from the terminal window the application starts, but I noticed the following error messages are generated in terminal:

"ERROR: ld.so: object 'libcef.so' from LD_PRELOAD cannot be preloaded (file too short): ignored."
"JRWeb: error while loading shared libraries: /home/ldm/.jriver/Media Center 24/Plugins/linux_chromium64/libcef.so: file too short"
"ipc server no longer running"

I'm no Linux or JR expert, so not sure what the above is telling me other than
a) some components are missing from the Chromium download or
b) JR is not finding them

Chrome can be started and works fine as a browser.  Any further ideas gratefully received.

[bob]

Sounds like the original DL didn't work.
Clear out the respective directory and try again.
Be patient when first starting up, it can take minutes depending on your DL speed...

Code: [Select]

rm  -rf ~/.jriver/Media\ Center\ 24/Plugins/linux_chromium64

[Jodel]

Progress and some success!

I tried what you suggested and removed the directory.  On loading JRiver again, the DL completed (I have a 35Mbs connection so it is quite quick) and this time, the 'Streaming' item is available and working from the tree view.

The 'Drives & Devices' still does not operate,  but now displays a message 'Loading'.

The terminal window shows a further error message:

"[1113/084943.272718:ERROR:gpu_process_transport_factory.cc(1027)] Lost UI shared context."

I'll see what I can find about this message, but it does seem like a resolution is close.

[Hendrik]

The "Lost UI shared context" message can be ignored, its of no consequence.

The "Drives & Devices" web page is known to be broken right now, and there is a fix in the next version for that. However, its really only an informational page and not something to interact with.
That window is not supposed to show you any drives or devices, if they are detected they would show up in the tree itself. But as Bob said above, this functionality is not available on Linux yet.

[Kott]

Sounds like the original DL didn't work.
Clear out the respective directory and try again.
Be patient when first starting up, it can take minutes depending on your DL speed...

Code: [Select]

rm  -rf ~/.jriver/Media\ Center\ 24/Plugins/linux_chromium64

Hi
I've tried this method because Radio Paradise doesn't work for me. I deleted this subfolder (without backup or renaming, of course) and Chromium engine was not downloaded after restart.
When started in terminal, the similar error appears:

JRWeb: error while loading shared libraries: libcef.so: cannot open shared object file: No such file or directory
ipc server no longer running

[bob]

Hi
I've tried this method because Radio Paradise doesn't work for me. I deleted this subfolder (without backup or renaming, of course) and Chromium engine was not downloaded after restart.
When started in terminal, the similar error appears:

JRWeb: error while loading shared libraries: libcef.so: cannot open shared object file: No such file or directory
ipc server no longer running

What distro and platform are you running on?
Chromium is only used for X64.

[Kott]

What distro and platform are you running on?
Chromium is only used for X64.

sorry didn't mention it

openSUSE Tumbleweed x86_64
embedded browser engine worked before (as chromium folder was present in ~/.jriver), but I don't remember which version downloaded it, tried 24.0.55 with same result above

[bob]

sorry didn't mention it

openSUSE Tumbleweed x86_64
embedded browser engine worked before (as chromium folder was present in ~/.jriver), but I don't remember which version downloaded it, tried 24.0.55 with same result above

If MC had successfully downloaded the current chromium plugin it would be in ~/.jriver/Media\ Center\ 24/Plugins/linux_chromium64
I'm guessing that it's because you aren't on debian and the DL of the chromium plugin is using https now and your certificate store isn't compatible.

You can try fixing the certificate store. MC is looking for it in the default debian location which is /etc/ssl/certs/ca-certificates.crt

Try looking around the forum for that string and you should find the references.

[Kott]

You can try fixing the certificate store. MC is looking for it in the default debian location which is /etc/ssl/certs/ca-certificates.crt
Try looking around the forum for that string and you should find the references.

It helped. Many thanks.