Topic: Blank Windows for JRiver on Raspberry Pi with Dietpi (Read 5124 times)

Facel · « **on:** May 07, 2019, 03:02:01 pm »

I am facing a new problem on a Sparky device.

Sparky is a Rasberry PC card , running Dietpi OS.

The MC25 is not running properly as I only have a blank windows .

I was previously running MC24 flawlessly

any help will be appreciated

bob · « **Reply #1 on:** May 07, 2019, 03:11:10 pm »

Quote from: Facel on May 07, 2019, 03:02:01 pm

I am facing a new problem on a Sparky device.

Sparky is a Rasberry PC card , running Dietpi OS.

The MC25 is not running properly as I only have a blank windows .

I was previoulys running MC24 flawlessly

any help will be appreciated

Make sure it's in 24 bit color mode. MC will not run in 16 bit color mode.

Awesome Donkey · « **Reply #2 on:** May 07, 2019, 03:30:43 pm »

https://yabb.jriver.com/interact/index.php/topic,120183.0.html

Follow the part about adding framebuffer_depth=32 and framebuffer_ignore_alpha=1 to your config.txt file.

Facel · « **Reply #3 on:** May 07, 2019, 04:42:23 pm »

Thank to both of you

I will try to implement your advices

Facel · « **Reply #4 on:** May 13, 2019, 12:15:06 pm »

I did verify that the two following lines are effectivly implemented in my DietPi.txt file (this is the equivallent file to config.txt)

framebuffer_depth=32
framebuffer_ignore_alpha=1

but the problem is still there.

Its seems to be linked to the new MC25 version, because when I re-install back MC24 I can run it without any problem.

bob · « **Reply #5 on:** May 13, 2019, 02:35:06 pm »

Perhaps the copying of skins got interrupted.
Try removing the MC25 user directory and re-run it. It will have no library and will be unlicensed at that point, you can restore the library from your MC24 backup.

Code: [Select]

rm -rf ~/.jriver/Media\ Center\ 25

Facel · « **Reply #6 on:** May 14, 2019, 09:13:53 am »

Bob .. I think that your command line should be : rm -rf ~.jriver/"Media Center 25"
I did removed the MC25 directory and I am aked to "restore License" or "Extend Tria" (the trial period has expiredl )

But nothing happen after having entered my Registration codein the restore licence windows !!!

bob · « **Reply #7 on:** May 14, 2019, 09:36:13 am »

Quote from: Facel on May 14, 2019, 09:13:53 am

Bob .. I think that your command line should be : rm -rf ~.jriver/"Media Center 25"
I did removed the MC25 directory and I am aked to "restore License" or "Extend Tria" (the trial period has expiredl )

But nothing happen after having entered my Registration codein the restore licence windows !!!

Yes you are correct.
What exactly do you mean when you say "nothing happens"? Are you back to blank windows or just nothing on the screen?

Facel · « **Reply #8 on:** May 14, 2019, 10:25:54 am »

I have nothing on the screen

Awesome Donkey · « **Reply #9 on:** May 14, 2019, 10:28:20 am »

Chances are MC is running in the background (you can check in the Task Manager). It *should* eventually pop up though.

Facel · « **Reply #10 on:** May 14, 2019, 10:34:07 am »

... when I re-launch MC25, I the"restore Licence windows" appears again !!

I have a HTOP program running on the desktop environnment that is not showing mediacenter25 as running ...unless I run it again ... and in that case I have
the "restore Licence program Windows" waiting for an input

additionnal info: on the desktop I also have a "Chromium Webbrowser" ...when I run it I have a Blank window (but with a blue color !! the previous MC blank windows was White !!)

Facel · « **Reply #11 on:** May 15, 2019, 03:32:09 am »

I have completly uninstalled MC25 .

I have re-installed MC24.

When I run (in console mode) MC24 I have the following error message => MediaCenter: Unable to open the X display device (null)

But when I run it on the desktop I have the windows asking for my Registration code . and then miracle I have my JRiver running properly (almost)

to be more precise when I just open MC the content panel has a blank window (grey color) !
When I select any option in the tree section like :PlayingNow, or Audio , or vdeo, then the content panel is prompting correltly the informations.
The only exception are for : Streaming, - Drives & devices and Services plugin showing a blank windows when they are selected

To me this behaviour has always been but I did not care considering my use of JRiver.

bob · « **Reply #12 on:** May 16, 2019, 08:48:12 am »

Quote from: Facel on May 15, 2019, 03:32:09 am

...
When I run (in console mode) MC24 I have the following error message => MediaCenter: Unable to open the X display device (null)

This expected behavior simply means that your terminal session doesn't have the DISPLAY variable for X set.

Quote

But when I run it on the desktop I have the windows asking for my Registration code . and then miracle I have my JRiver running properly (almost)

to be more precise when I just open MC the content panel has a blank window (grey color) !
When I select any option in the tree section like :PlayingNow, or Audio , or vdeo, then the content panel is prompting correltly the informations.
The only exception are for : Streaming, - Drives & devices and Services plugin showing a blank windows when they are selected

To me this behaviour has always been but I did not care considering my use of JRiver.

The blank windows are the result of your system not properly supporting the gtk webkit library package libwebkit2gtk-4.0-37
You can see if there are any missing libraries for the internal web browser by doing:
ldd /usr/lib/jriver/Media\ Center\ 24/JRWeb

Facel · « **Reply #13 on:** May 16, 2019, 08:58:20 am »

it seems that nothing is missing ?

Code: [Select]

root@MC-Cuisine:~# ldd /usr/lib/jriver/Media\ Center\ 24/JRWeb
        libcryptlib.so => /usr/lib/jriver/Media Center 24/libcryptlib.so (0xb6c43000)
        libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6c11000)
        librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb6bfb000)
        libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6be8000)
        libX11.so.6 => /usr/lib/arm-linux-gnueabihf/libX11.so.6 (0xb6af4000)
        libuuid.so.1 => /lib/arm-linux-gnueabihf/libuuid.so.1 (0xb6ae0000)
        libXrandr.so.2 => /usr/lib/arm-linux-gnueabihf/libXrandr.so.2 (0xb6ac9000)
        libwebkit2gtk-4.0.so.37 => /usr/lib/arm-linux-gnueabihf/libwebkit2gtk-4.0.so.37 (0xb52b5000)
        libgtk-3.so.0 => /usr/lib/arm-linux-gnueabihf/libgtk-3.so.0 (0xb4daa000)
        libgdk-3.so.0 => /usr/lib/arm-linux-gnueabihf/libgdk-3.so.0 (0xb4cfe000)
        libpangocairo-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libpangocairo-1.0.so.0 (0xb4ce5000)
        libpango-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libpango-1.0.so.0 (0xb4c9e000)
        libatk-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libatk-1.0.so.0 (0xb4c76000)
        libcairo-gobject.so.2 => /usr/lib/arm-linux-gnueabihf/libcairo-gobject.so.2 (0xb4c60000)
        libcairo.so.2 => /usr/lib/arm-linux-gnueabihf/libcairo.so.2 (0xb4ba8000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgdk_pixbuf-2.0.so.0 (0xb4b7e000)
        libsoup-2.4.so.1 => /usr/lib/arm-linux-gnueabihf/libsoup-2.4.so.1 (0xb4adf000)
        libgio-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0 (0xb49d6000)
        libgobject-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0 (0xb498e000)
        libjavascriptcoregtk-4.0.so.18 => /usr/lib/arm-linux-gnueabihf/libjavascriptcoregtk-4.0.so.18 (0xb4102000)
        libglib-2.0.so.0 => /lib/arm-linux-gnueabihf/libglib-2.0.so.0 (0xb4027000)
        libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb3f1b000)
        libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb3ea1000)
        libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb3e78000)
        libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb3d8a000)
        /lib/ld-linux-armhf.so.3 (0xb6f04000)
        libxcb.so.1 => /usr/lib/arm-linux-gnueabihf/libxcb.so.1 (0xb3d62000)
        libXext.so.6 => /usr/lib/arm-linux-gnueabihf/libXext.so.6 (0xb3d47000)
        libXrender.so.1 => /usr/lib/arm-linux-gnueabihf/libXrender.so.1 (0xb3d30000)
        libGLESv2.so.2 => /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 (0xb3d17000)
        libEGL.so.1 => /usr/lib/arm-linux-gnueabihf/libEGL.so.1 (0xb3ce8000)
        libnotify.so.4 => /usr/lib/arm-linux-gnueabihf/libnotify.so.4 (0xb3cd2000)
        libfontconfig.so.1 => /usr/lib/arm-linux-gnueabihf/libfontconfig.so.1 (0xb3c9a000)
        libfreetype.so.6 => /usr/lib/arm-linux-gnueabihf/libfreetype.so.6 (0xb3c1f000)
        libharfbuzz.so.0 => /usr/lib/arm-linux-gnueabihf/libharfbuzz.so.0 (0xb3ba3000)
        libharfbuzz-icu.so.0 => /usr/lib/arm-linux-gnueabihf/libharfbuzz-icu.so.0 (0xb3b91000)
        libgcrypt.so.20 => /lib/arm-linux-gnueabihf/libgcrypt.so.20 (0xb3ae6000)
        libgstapp-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgstapp-1.0.so.0 (0xb3acc000)
        libgstbase-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgstbase-1.0.so.0 (0xb3a75000)
        libgstreamer-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgstreamer-1.0.so.0 (0xb3995000)
        libgstpbutils-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgstpbutils-1.0.so.0 (0xb3960000)
        libgstaudio-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgstaudio-1.0.so.0 (0xb3908000)
        libgsttag-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgsttag-1.0.so.0 (0xb38cd000)
        libgstvideo-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgstvideo-1.0.so.0 (0xb3863000)
        libgstfft-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgstfft-1.0.so.0 (0xb3849000)
        libjpeg.so.62 => /usr/lib/arm-linux-gnueabihf/libjpeg.so.62 (0xb380f000)
        libpng16.so.16 => /usr/lib/arm-linux-gnueabihf/libpng16.so.16 (0xb37df000)
        libwebp.so.6 => /usr/lib/arm-linux-gnueabihf/libwebp.so.6 (0xb3794000)
        libenchant.so.1 => /usr/lib/arm-linux-gnueabihf/libenchant.so.1 (0xb377c000)
        libgmodule-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgmodule-2.0.so.0 (0xb3769000)
        libsecret-1.so.0 => /usr/lib/arm-linux-gnueabihf/libsecret-1.so.0 (0xb3729000)
        libtasn1.so.6 => /usr/lib/arm-linux-gnueabihf/libtasn1.so.6 (0xb370d000)
        libxml2.so.2 => /usr/lib/arm-linux-gnueabihf/libxml2.so.2 (0xb35ef000)
        libxslt.so.1 => /usr/lib/arm-linux-gnueabihf/libxslt.so.1 (0xb35b5000)
        libhyphen.so.0 => /usr/lib/arm-linux-gnueabihf/libhyphen.so.0 (0xb35a1000)
        libsqlite3.so.0 => /usr/lib/arm-linux-gnueabihf/libsqlite3.so.0 (0xb34f4000)
        libXcomposite.so.1 => /usr/lib/arm-linux-gnueabihf/libXcomposite.so.1 (0xb34df000)
        libXdamage.so.1 => /usr/lib/arm-linux-gnueabihf/libXdamage.so.1 (0xb34cc000)
        libicuuc.so.57 => /usr/lib/arm-linux-gnueabihf/libicuuc.so.57 (0xb33a3000)
        libicui18n.so.57 => /usr/lib/arm-linux-gnueabihf/libicui18n.so.57 (0xb31f6000)
        libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb31d4000)
        libwayland-server.so.0 => /usr/lib/arm-linux-gnueabihf/libwayland-server.so.0 (0xb31b9000)
        libwayland-egl.so.1 => /usr/lib/arm-linux-gnueabihf/libwayland-egl.so.1 (0xb31a7000)
        libwayland-client.so.0 => /usr/lib/arm-linux-gnueabihf/libwayland-client.so.0 (0xb318f000)
        libXi.so.6 => /usr/lib/arm-linux-gnueabihf/libXi.so.6 (0xb3175000)
        libXfixes.so.3 => /usr/lib/arm-linux-gnueabihf/libXfixes.so.3 (0xb3161000)
        libatk-bridge-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libatk-bridge-2.0.so.0 (0xb3130000)
        libxkbcommon.so.0 => /usr/lib/arm-linux-gnueabihf/libxkbcommon.so.0 (0xb30f0000)
        libwayland-cursor.so.0 => /usr/lib/arm-linux-gnueabihf/libwayland-cursor.so.0 (0xb30d9000)
        libepoxy.so.0 => /usr/lib/arm-linux-gnueabihf/libepoxy.so.0 (0xb302d000)
        libpangoft2-1.0.so.0 => /usr/lib/arm-linux-gnueabihf/libpangoft2-1.0.so.0 (0xb300e000)
        libXinerama.so.1 => /usr/lib/arm-linux-gnueabihf/libXinerama.so.1 (0xb2ffb000)
        libXcursor.so.1 => /usr/lib/arm-linux-gnueabihf/libXcursor.so.1 (0xb2fe4000)
        libgthread-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgthread-2.0.so.0 (0xb2fd2000)
        libthai.so.0 => /usr/lib/arm-linux-gnueabihf/libthai.so.0 (0xb2fbb000)
        libpixman-1.so.0 => /usr/lib/arm-linux-gnueabihf/libpixman-1.so.0 (0xb2f32000)
        libxcb-shm.so.0 => /usr/lib/arm-linux-gnueabihf/libxcb-shm.so.0 (0xb2f1d000)
        libxcb-render.so.0 => /usr/lib/arm-linux-gnueabihf/libxcb-render.so.0 (0xb2f04000)
        libgssapi_krb5.so.2 => /usr/lib/arm-linux-gnueabihf/libgssapi_krb5.so.2 (0xb2eca000)
        libselinux.so.1 => /lib/arm-linux-gnueabihf/libselinux.so.1 (0xb2ea0000)
        libresolv.so.2 => /lib/arm-linux-gnueabihf/libresolv.so.2 (0xb2e80000)
        libmount.so.1 => /lib/arm-linux-gnueabihf/libmount.so.1 (0xb2e3e000)
        libffi.so.6 => /usr/lib/arm-linux-gnueabihf/libffi.so.6 (0xb2e28000)
        libpcre.so.3 => /lib/arm-linux-gnueabihf/libpcre.so.3 (0xb2dc8000)
        libXau.so.6 => /usr/lib/arm-linux-gnueabihf/libXau.so.6 (0xb2dbd000)
        libXdmcp.so.6 => /usr/lib/arm-linux-gnueabihf/libXdmcp.so.6 (0xb2da9000)
        libdrm.so.2 => /usr/lib/arm-linux-gnueabihf/libdrm.so.2 (0xb2d8d000)
        libglapi.so.0 => /usr/lib/arm-linux-gnueabihf/libglapi.so.0 (0xb2d5a000)
        libX11-xcb.so.1 => /usr/lib/arm-linux-gnueabihf/libX11-xcb.so.1 (0xb2d48000)
        libxcb-dri2.so.0 => /usr/lib/arm-linux-gnueabihf/libxcb-dri2.so.0 (0xb2d34000)
        libxcb-xfixes.so.0 => /usr/lib/arm-linux-gnueabihf/libxcb-xfixes.so.0 (0xb2d1e000)
        libxcb-dri3.so.0 => /usr/lib/arm-linux-gnueabihf/libxcb-dri3.so.0 (0xb2d0b000)
        libxcb-present.so.0 => /usr/lib/arm-linux-gnueabihf/libxcb-present.so.0 (0xb2cf8000)
        libxcb-sync.so.1 => /usr/lib/arm-linux-gnueabihf/libxcb-sync.so.1 (0xb2ce3000)
        libxshmfence.so.1 => /usr/lib/arm-linux-gnueabihf/libxshmfence.so.1 (0xb2cd1000)
        libgbm.so.1 => /usr/lib/arm-linux-gnueabihf/libgbm.so.1 (0xb2cb8000)
        libexpat.so.1 => /lib/arm-linux-gnueabihf/libexpat.so.1 (0xb2c90000)
        libgraphite2.so.3 => /usr/lib/arm-linux-gnueabihf/libgraphite2.so.3 (0xb2c63000)
        libicudata.so.57 => /usr/lib/arm-linux-gnueabihf/libicudata.so.57 (0xb13d6000)
        libgpg-error.so.0 => /lib/arm-linux-gnueabihf/libgpg-error.so.0 (0xb13b9000)
        liborc-0.4.so.0 => /usr/lib/arm-linux-gnueabihf/liborc-0.4.so.0 (0xb135a000)
        liblzma.so.5 => /lib/arm-linux-gnueabihf/liblzma.so.5 (0xb1330000)
        libatspi.so.0 => /usr/lib/arm-linux-gnueabihf/libatspi.so.0 (0xb1301000)
        libdbus-1.so.3 => /lib/arm-linux-gnueabihf/libdbus-1.so.3 (0xb12c0000)
        libdatrie.so.1 => /usr/lib/arm-linux-gnueabihf/libdatrie.so.1 (0xb12aa000)
        libkrb5.so.3 => /usr/lib/arm-linux-gnueabihf/libkrb5.so.3 (0xb1212000)
        libk5crypto.so.3 => /usr/lib/arm-linux-gnueabihf/libk5crypto.so.3 (0xb11dc000)
        libcom_err.so.2 => /lib/arm-linux-gnueabihf/libcom_err.so.2 (0xb11c9000)
        libkrb5support.so.0 => /usr/lib/arm-linux-gnueabihf/libkrb5support.so.0 (0xb11b2000)
        libkeyutils.so.1 => /lib/arm-linux-gnueabihf/libkeyutils.so.1 (0xb119f000)
        libblkid.so.1 => /lib/arm-linux-gnueabihf/libblkid.so.1 (0xb1163000)
        libbsd.so.0 => /lib/arm-linux-gnueabihf/libbsd.so.0 (0xb1140000)
        libsystemd.so.0 => /lib/arm-linux-gnueabihf/libsystemd.so.0 (0xb10e6000)
        liblz4.so.1 => /usr/lib/arm-linux-gnueabihf/liblz4.so.1 (0xb10c8000)

bob · « **Reply #14 on:** May 16, 2019, 09:29:33 am »

Looks like that's the case but if the browser data isn't showing up there is an issue with your system supporting webkitgtk.
It works on every variant of linux we've tried it on that has the webkitgtk libs.

Facel · « **Reply #15 on:** May 16, 2019, 10:16:03 am »

Thank you bob for your help (as I am not a linux expert)

anyway I am going to re-install everything from scratch because it is not normal that I can't open a chromium webbrowser.

I finally succed to have it running but i prefer to start back from a clean install.

To me it is strange that I can have MC24 running and nothing with MC25 (on the same environnement)

Facel · « **Reply #16 on:** May 17, 2019, 08:05:15 am »

I did re-install everything + MC25 from scratch !!

On the very first run of MC 25 I have got a window asking for the registration code and proposing a 30 day trying period (That is new !)

I have chosen trying ... but no MC windows on the desktop

I can see the JRWeb running (0,7% cpu from time to time)

BryanC · « **Reply #17 on:** May 17, 2019, 08:45:32 am »

Generally, running an obscure OS results in obscure problems. Can you not use Raspbian on your device?

Facel · « **Reply #18 on:** May 17, 2019, 08:58:13 am »

Probably but I had no obscure problem with my obscure OS on MC24 !!!

No I can't use Raspbian because I am using a set (Sparky Board + USBrige board) in order to get a clean USB audio signal.

By the way I succeed to have chromium running properly .. ((with the help of linux expert on internet)
I can hope to have mC25 running properly

bob · « **Reply #19 on:** May 17, 2019, 09:32:27 am »

Quote from: Facel on May 17, 2019, 08:58:13 am

Probably but I had no obscure problem with my obscure OS on MC24 !!!

No I can't use Raspbian because I am using a set (Sparky Board + USBrige board) in order to get a clean USB audio signal.

By the way I succeed to have chromium running properly .. ((with the help of linux expert on internet)
I can hope to have mC25 running properly

I can't imagine why there would be any difference between MC24 and MC25 on your device with regards to windowing.
If you run MC24 does the browser window show up now? (start page, streaming, etc...)

Facel · « **Reply #20 on:** May 17, 2019, 10:59:11 am »

I did not try MC24 on my new "complete install from srcratch"

on ma previous config, even after having chromium running properly, I could not get the browser window showing up on MC24.

My princiapl problem with MC25 is not having any MC Windows.

Awesome Donkey · « **Reply #21 on:** May 17, 2019, 11:34:11 am »

Quote from: BryanC on May 17, 2019, 08:45:32 am

Generally, running an obscure OS results in obscure problems.

I have to agree with this. There's a reason running MC on non-Debian (or Raspbian in this case) OSes is considered unsupported configurations.

You might try Raspbian, it'll more than likely work there if you follow this tutorial: https://yabb.jriver.com/interact/index.php/topic,120183.0.html

Facel · « **Reply #22 on:** May 24, 2019, 03:52:18 am »

Back again..

I have installed MC24 on my new "complete install from srcratch"=> I have the MC 24 windows prompting !! with blank windows remaining on the very first launch and for Streaming, Drives & Devices and Services & Plug ing

The blank windows inside MC24 program are prompting : "Loading ..."

Still no windows at all for MC25 running

Facel · « **Reply #23 on:** May 27, 2019, 10:03:46 am »

Maybe the problem is coming from Bitdeph, because I have founded this info in the release section of
version 6.22 of the Dietpi OS.

- RPi | DietPi does not set or change "framebuffer_depth" in config.txt any more which defaults to 16 which works in every known case.
It will be re-added as fast as we find a case where another value is required.

I am running v 6.24.1 (the very last version) => what is strange is that MC24 main windows is correctly prompting (in 16 bit ) and MC25 not ?

bob · « **Reply #24 on:** May 28, 2019, 11:27:22 am »

Quote from: Facel on May 27, 2019, 10:03:46 am

Maybe the problem is coming from Bitdeph, because I have founded this info in the release section of
version 6.22 of the Dietpi OS.

- RPi | DietPi does not set or change "framebuffer_depth" in config.txt any more which defaults to 16 which works in every known case.
It will be re-added as fast as we find a case where another value is required.

I am running v 6.24.1 (the very last version) => what is strange is that MC24 main windows is correctly prompting (in 16 bit ) and MC25 not ?

I can't understand why MC24 would work but I can tell you for CERTAIN MC requires a 24 bit framebuffer.

Facel · « **Reply #25 on:** May 29, 2019, 02:58:18 am »

After some investigations ...I do not think that the problem is related to a wrong framebuffer depth.

The framebuffer_depth has been set to 16 only in the Dietpi OS for RPI board. In my case I am using a Spaky board and
so this modification does not apply for me.

The fact MC24 is running confirm that my framebuffer_depth is ok for JRiver.

When I launch MC25 (in the LXDE environnment), there is a brief flash on the screen (as if the MC Windows start to open and immedialtly close itself)

The JRWeb / Engine GTKWebkit is effectivly running but mediacenter25 is not running (info from Htop)

Is there a way to get some log files somewhere ?

Facel · « **Reply #26 on:** May 29, 2019, 08:23:30 am »

Sorry for this auto-reply

After some (long) addtionnal research other people had the same problem as I have on some RPI devices:
https://github.com/MichaIng/DietPi/issues/1080 with MC24 version.

Could it be a possible JRIver Bug ??

JimH · « **Reply #27 on:** May 29, 2019, 09:14:39 am »

I don't think it's clear whose bug it may be, but we're not going to chase it in any case. If you choose an OS we don't support, it's up to you to make it work.

Raspbian would be a lot less trouble.

Facel · « **Reply #28 on:** May 29, 2019, 10:13:00 am »

Quote from: JimH on May 29, 2019, 09:14:39 am

Raspbian would be a lot less trouble.

Maybe or Maybe not

I did not choose the OS, I have chosen a product : USBridge (from Allo) known to be an excellent audio renderer
with a very clean USB output ... running a different OS (Dietpi) than Raspbian ...

I agree that it is not clear whose bug is it .. nevertheless any help will be appreciated

JimH · « **Reply #29 on:** May 29, 2019, 10:21:38 am »

Have you asked Allo about using Raspbian?

Facel · « **Reply #30 on:** May 29, 2019, 10:55:04 am »

not yet but I will

Dietpi is derived from Debian Jessie ... they should release a "stretch" version soon ...

INTERACT FORUM

Author Topic: Blank Windows for JRiver on Raspberry Pi with Dietpi (Read 5124 times)