INTERACT FORUM

More => Old Versions => JRiver Media Center 31 for Linux => Topic started by: MRiver on May 16, 2023, 07:05:07 am

Title: libxdmcp >= 1.2.162 request
Post by: MRiver on May 16, 2023, 07:05:07 am
The required package version is listed as libxdmcp6: 1:1.2.162, so is this a build error?
If this requirement is correct, it will not install on all Linux. This is 1.1.3 in my environment. I am waiting for a fix. Thanks for your daily hard work.
Title: Re: libxdmcp >= 1.2.162 request
Post by: Awesome Donkey on May 16, 2023, 07:12:51 am
It's a bug. You can workaround it right now using the installJRMC script with the --compat --install local --mcversion 31.0.11 switches, otherwise have to wait for a fixed build to be posted.

I reported it here earlier: https://yabb.jriver.com/interact/index.php/topic,135990.0.html
Title: Re: libxdmcp >= 1.2.162 request
Post by: bob on May 16, 2023, 12:33:25 pm
Fixed in 31.0.12
Title: Re: libxdmcp >= 1.2.162 request
Post by: MRiver on May 16, 2023, 11:31:26 pm
Thanks for the fix, I think the BUG is fixed, but I can't install it. The reason is that the required version of licxcb is 1.14. I am trying with Fedora, but RHL-based Linux uses licxcb 1.13. This is also true for Fedora39 which has not been released yet.

Could you please revert to the first list of requirements, 1.12? Or please bundle 1.14, it is impossible for the average user to build and install 1.14 from source code, except for engineers.
Title: Re: libxdmcp >= 1.2.162 request
Post by: Awesome Donkey on May 17, 2023, 03:08:26 am
Yes, for Fedora you still need to do the workaround. Bryan posted about it here: https://yabb.jriver.com/interact/index.php/topic,135999.msg942158.html#msg942158
Title: Re: libxdmcp >= 1.2.162 request
Post by: MRiver on May 17, 2023, 12:16:42 pm
It worked with the COMPACT option. Thanks.
Title: Re: libxdmcp >= 1.2.162 request
Post by: drmimosa on May 18, 2023, 08:52:52 am
Has anyone considered building or maintaining a Flatpak version of mediacenter?

It might mitigate some of the depency issues like this one, and allow installation on immutable Linux systems.

https://docs.flatpak.org/en/latest/first-build.html

Not sure how much this would limit access to system resources etc.
Title: Re: libxdmcp >= 1.2.162 request
Post by: Awesome Donkey on May 18, 2023, 08:57:36 am
I'd be highly interested in a Flatpak version of Media Center. It'd allow me to install MC on my Steam Deck and use it, without needing to enable write access in SteamOS to install it that way (which would then be removed during any SteamOS updates). :D

Regarding limitations, considering RetroArch is available and works as a Flatpak, Snap and AppImage and it'd likely require way more permissions than MC would, I don't see any reason why MC wouldn't, IMO.
Title: Re: libxdmcp >= 1.2.162 request
Post by: bob on May 18, 2023, 03:02:51 pm
When I looked at this before it didn't seem doable.
MC's requirements for system libraries and access to things at system level didn't look compatible.
Title: Re: libxdmcp >= 1.2.162 request
Post by: danrien on June 08, 2023, 08:25:02 am
When I looked at this before it didn't seem doable.
MC's requirements for system libraries and access to things at system level didn't look compatible.

I would happily take a crack at it, but would probably not be up to maintaining it if it works... my little project blue (https://play.google.com/store/apps/details?id=com.lasthopesoftware.bluewater) is enough of a maintenance burden  ;D.
Title: Re: libxdmcp >= 1.2.162 request
Post by: Awesome Donkey on June 08, 2023, 08:28:39 am
As a proof-of-concept it might be worth it to see if it even works as a Flatpak. I would happily test it on my Steam Deck too. :P
Title: Re: libxdmcp >= 1.2.162 request
Post by: danrien on June 25, 2023, 09:28:36 am
The flatpak approach is quite intimidating, so I instead spent my weekend going down the AppImage route, however I do seem to be hitting a wall with accessing/copying skins to the home directory... all of this stuff is promised to work, but it seems as though some path patching doesn't work as hoped. Here's an strace call, where the relative path patching seems to work, until it doesn't, on `openat`:

Code: [Select]
access("/tmp/.mount_mediacUs0sGQ/usr/lib/jriver/Media Center 30/Skins/Standard View/", F_OK) = 0
stat("/tmp/.mount_mediacUs0sGQ/usr/lib/jriver/Media Center 30/Skins/Standard View/", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
openat(AT_FDCWD, "/usr/lib/jriver/Media Center 30/Skins/Standard View", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)

The good news is that if I copy the skins over myself before running the AppImage, then Media Center seems to launch just fine! But there seems to be other read/write issues that then happen after that, so I wouldn't encourage using this in its current state, as it can wipe out your library.

I've also tried this with MC31 with the same results  :(.

My work so far is shared on github: https://github.com/davidvedvick/mediacenter.appimage, it uses appimage-builder (https://appimage-builder.readthedocs.io/en/latest/index.html) to build the image from an apt source.