Print

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

[npreining]

OS: Arch Linux
Package from AUR
Version of MC: 33.0.49
Windowing system: Wayland

I cannot start the mediacenter, it crashes right on start with a segfault. Running under gdb does not give any useful information, unfortunately:

Code: [Select]

Thread 1 "mediacenter33" received signal SIGSEGV, Segmentation fault.
0x00005555561d34a9 in ?? ()
(gdb) bt
#0  0x00005555561d34a9 in ? ()
#1  0x0000555556d3c218 in ? ()
#2  0x00005555563ffadf in ? ()
#3  0x0000555556d3c218 in ? ()
#4  0x0000555556d480b2 in ? ()
#5  0x0000555555fa69ee in ? ()
#6  0x0000555556d4e4e6 in ? ()
#7  0x0000555556d4e605 in ? ()
#8  0x0000555556d26a35 in ? ()
#9  0x0000555556d753ba in ? ()
#10 0x0000555556d2745f in ? ()
#11 0x0000555556d25291 in ? ()
#12 0x0000555556df9fa3 in ? ()
#13 0x0000555556e1372a in ? ()
#14 0x0000555556d28f7b in ? ()
#15 0x0000555555fa4270 in ? ()
#16 0x0000555555d6e70a in ? ()
#17 0x0000555555d70544 in ? ()
#18 0x0000555555d387b7 in ? ()
#19 0x0000555556e298da in ? ()
#20 0x0000555556e2935d in ? ()
#21 0x00007ffff7434e08 in __libc_start_call_main (main=main@entry=0x555555d2f030, argc=argc@entry=1, argv=argv@entry=0x7fffffffd568)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#22 0x00007ffff7434ecc in __libc_start_main_impl
    (main=0x555555d2f030, argc=1, argv=0x7fffffffd568, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd558) at ../csu/libc-start.c:360
#23 0x0000555555d3640a in ? ()(gdb)


Any suggestion how to proceed? Thanks

[Awesome Donkey]

You might try on Debian and see if it happens there too, since Debian is the only Linux distro JRiver officially supports.

[npreining]

Thanks for the suggestion, but my guess it is with Wayland and XWayland.
On my desktop system, which also runs Arch but with X11/Xorg, it works without any problem.
Unfortunately, due to the stripped debugging symbols, there is not really a hint what needs to be changed.

[npreining]

After a cleaning of the whole ~/.jriver directory and reentering my license number, now mediacenter spits out a few error messages:

Code: [Select]

[1225/212940.098111:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
FFF9F9F9 Start bcolor F9F9F9 nColor
[1225/212940.214044:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[1225/212940.224531:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[1225/212940.331448:WARNING:policy_logger.cc(151)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(88) Could not create policy manager as CBCM is not enabled.
[1225/212940.466943:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[1225/212940.497980:WARNING:angle_platform_impl.cc(49)] RendererVk.cpp:1962 (initialize): ANGLE VMA version: 2003000
[1225/212940.551477:WARNING:sandbox_linux.cc(400)] InitializeSandbox() called with multiple threads in process gpu-process.
Segmentation fault (core dumped)

Does that ring a bell with someone?

[npreining]

Just for confirmation, same laptop, but running X11 and not Wayland, mediacenter starts witihout a problem!

[Awesome Donkey]

Media Center only supports X11 and doesn't support Wayland, so you'd need XWayland if using it there, though that may not make the segfault go away (there may be other factors). I can say however that MC33 works fine in both my GNOME and KDE Plasma Arch Linux VMs that uses X11.

[npreining]

Yup, so it seems. XWayland seems to work with most apps, but not with MC. With X11 all is working fine.

[Awesome Donkey]

MC33 does work fine for me with XWayland in Ubuntu 24.10, so I guess the mileage may vary.

[mwillems]

So I run Mediacenter on Arch Linux with Gnome on Wayland with no issues at all (for many years), so the problem is likely something idiosyncratic to your system.  In fact I'm running 33.0.49 on Wayland right now as I type this, so I can confirm there is no general or universal issue with mediacenter and Wayland/XWayland on Arch. 

One thing to know is that every Wayland compositor is completely different (i.e. it's not like X11 where all window managers share the same underlying implementation), so it doesn't always make sense to talk about Wayland in the abstract: the specific window manager or desktop environment can make a big difference for wayland compatability.  What wayland compositor (i.e. desktop environment or window manager) are you using?  If you're using Gnome or KDE then it's almost certainly something about your setup or configuration as there are several folks here (including me) successfully running Mediacenter on those Wayland compositors on Arch.  If it's something more exotic like Sway, then there might be a compatibility issue for further investigation there.

[bob]

The errors you see in terminal are coming from the browser code. (the embedded chromium plugin).
Seems like some incompatibility with that and your Wayland server.

[Awesome Donkey]

Does it depend on any dependency to be installed in order to work? Maybe the Arch Linux PKGBUILD on the AUR hasn't been updated for some unmet dependency? It does list webkit2gtk at least.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jriver-media-center