More > JRiver Media Center 33 for Linux

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

<< < (2/6) > >>

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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page