More > JRiver Media Center 25 for Linux

MC25 segfaults after a few seconds in Ubuntu Bionic container

<< < (2/2)

BryanC:

--- Quote from: max096 on December 24, 2019, 05:00:52 pm ---My experience with that has been pretty hit and miss.

--- End quote ---

So far I've missed far more than I've hit. I've lost a solid two weeks trying to deal with podman issues across my entire workflow. The biggest problem is that you never know what won't work ahead of time (I'm on my third bugzilla report atm) because they refuse to acknowledge the fact that podman is not a drop-in replacement. If at the very least they published a list of compatible base images it would save a lot of time. They really screwed up by forcing cgroups v2 into F31. It's such an obvious power play to move users away from Docker, but they forgot to ship an alternative that actually works to offset the broken compatibility. And for some reason they are set on sticking with libpod 1.6.2 in F31 (probably because they know that updating podman within a release cycle is extremely risky based on the major changes they have had to make in the interim to restore basic functionality). I've had podman crash my entire system numerous times, which has not happened since F18 despite being the "safe" rootless container implementation. For the first time in nearly a decade I feel like the stereotypical RHEL beta tester.

And since I was always taught to end on a positive, Toolbox is a pretty nice tool for users (considering it is optional).

max096:
GDB also wasnīt very helpful. Iīm sitting at the same segfault (probably? hopefully?) that you are.


--- Code: ---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.

--- End code ---

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).

Navigation

[0] Message Index

[*] Previous page