GDB also wasnīt very helpful. Iīm sitting at the same segfault (probably? hopefully?) that you are.
root@a5fd92bdfc33:/# gdb mediacenter25
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from mediacenter25...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/mediacenter25
warning: Error disabling address space randomization: Operation not permitted
During startup program terminated with signal SIGSEGV, Segmentation fault.
(gdb) bt
No stack.
Not very helpful. No stack. Dies on startup. I was very sceptical of this giving me anything but jibberish anyways (given that jriver isnīt exactly open source, probably no one could read whatever it outputs). But it does not even do jibberish.
I also just installed nautilus into the otherwise identical JRiver image and started that instead of JRiver.
And no one behold there was nautilus. Exact same image. JRiver still installed actually, just started nautilus instead.
I think we are just not getting JRiver to run in podman for the time being.
And trying to build it with buildah instead I did not even get this far. It told me it cannot find sh every script it ran (after building 'successfully' when running the result with podman).