More > JRiver Media Center 33 for Linux

[solved with MC34] MC on Arch Linux crash on startup [Partially Solved]

<< < (4/6) > >>

bob:

--- Quote from: npreining on December 29, 2024, 04:39:13 am ---Hmm, very different information going around here. I heard statements that MC works on Wayland on Arch, and at the same time that the chromium plugin does not work with "newer" (or rolling) releases.

If MC/Wayland/Arch works on Gnome, it should not be the problem of the chromium plugin, but something else that is missing? Some shared library that is loaded in a none-standard way?

--- End quote ---
I didn't say that the chromium plugin doesn't work on your particular version of linux, I said that's where it seems to be crashing. There really is no way to test all of the different versions of linux that's why we say the supported distro is debian. Other than that YMMV.

You could look at MC's downloaded chromium plugin which is in ~/.jriver/Media Center 33/Plugins and use ldd on each shared object to see if there are any missing libraries.

npreining:
Thanks for the suggestion, but nothing particularly strange there, all libraries but the ffmpeg ones with -jr affix are found. Those not found are there but not resolved due to ld library path not correctly set I guess:

--- Code: ---$ ldd $(find . -name \*.so\*) 2>/dev/null | grep 'not found'
        libswresample-jr.so.5 => not found
        libavutil-jr.so.59 => not found
        libswscale-jr.so.8 => not found
        libavutil-jr.so.59 => not found
        libavcodec-jr.so.61 => not found
        libavutil-jr.so.59 => not found
        libavutil-jr.so.59 => not found
        libavutil-jr.so.59 => not found

--- End code ---

(the stderr only contains messages about misising exec permissions)

bob:

--- Quote from: npreining on January 03, 2025, 11:55:41 pm ---Thanks for the suggestion, but nothing particularly strange there, all libraries but the ffmpeg ones with -jr affix are found. Those not found are there but not resolved due to ld library path not correctly set I guess:

--- Code: ---$ ldd $(find . -name \*.so\*) 2>/dev/null | grep 'not found'
        libswresample-jr.so.5 => not found
        libavutil-jr.so.59 => not found
        libswscale-jr.so.8 => not found
        libavutil-jr.so.59 => not found
        libavcodec-jr.so.61 => not found
        libavutil-jr.so.59 => not found
        libavutil-jr.so.59 => not found
        libavutil-jr.so.59 => not found

--- End code ---

(the stderr only contains messages about misising exec permissions)

--- End quote ---
Those download automatically into
~/.jriver/Media\ Center\ 33/Plugins/linux_avcodec64
If there aren't there that's an issue.
If they are there you can ldd on them to see if anything in the OS is missing. Any "not founds" that references back to these can safely be ignored (the path isn't set for their self-reference from the shell)

npreining:
Yes, the ffmepg -jr variant libs are there, and all dlls resolve correctly for them:

--- Code: ---[~/.jriver/Media Center 33/Plugins/linux_avcodec64] LD_LIBRARY_PATH=. ldd *

--- End code ---
does not show any unresolved libraries

npreining:
I have now narrowed it down - it is JRiver MC33 on kwin (KDE/Plasma) with Wayland.
Working combinations are:
* KWin / X11
* Gnome / Wayland

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version