Server Version#:latest
Player Version#:1.53.1
Plex-desktop snap crashes on startup.
snap run plex-desktop
libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (Operation not permitted)
[31674:31729:0907/130431.556362:ERROR:address_tracker_linux.cc(195)] Could not create NETLINK socket: Operation not permitted (1)
[31674:31727:0907/130431.557961:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.nMGlDf failed: Permission denied (13)
[31674:31674:0907/130431.629069:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.SKG45f failed: Permission denied (13)
[31674:31739:0907/130431.631667:ERROR:zygote_host_impl_linux.cc(263)] Failed to adjust OOM score of renderer with pid 31742: Permission denied (13)
[31740:31752:0907/130431.639467:ERROR:address_tracker_linux.cc(195)] Could not create NETLINK socket: Operation not permitted (1)
Cannot load libcuda.so.1
[31674:31727:0907/130431.759294:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.Xc3oCd failed: Permission denied (13)
[31742:31742:0907/130431.759334:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759405:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.759485:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.dwKw7e failed: Permission denied (13)
[31742:31742:0907/130431.759496:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759516:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.759569:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.bnglUf failed: Permission denied (13)
[31742:31742:0907/130431.759579:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759597:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.759649:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.U6mbig failed: Permission denied (13)
[31742:31742:0907/130431.759658:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759676:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.759727:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.CxsHug failed: Permission denied (13)
[31742:31742:0907/130431.759736:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759755:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.759805:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.U6U8Jf failed: Permission denied (13)
[31742:31742:0907/130431.759814:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759832:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.759883:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.mSaKmg failed: Permission denied (13)
[31742:31742:0907/130431.759892:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759910:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.759961:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.oJA9me failed: Permission denied (13)
[31742:31742:0907/130431.759970:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.759987:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.760037:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.ZArWSe failed: Permission denied (13)
[31742:31742:0907/130431.760048:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.760065:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31727:0907/130431.760116:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.8iE2ng failed: Permission denied (13)
[31742:31742:0907/130431.760124:ERROR:broker_posix.cc(46)] Received unexpected number of handles
[31742:31742:0907/130431.760142:ERROR:command_buffer_proxy_impl.cc(102)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed
[31674:31729:0907/130431.768148:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.zGGTtd failed: Permission denied (13)
[31674:31729:0907/130431.768168:FATAL:data_pipe.cc(14)] Failed to create data pipe due to MOJO_RESULT_RESOURCE_EXHAUSTED.
Trace/breakpoint trap (core dumped)
I wonder why https://plex.app/ lists broken Snap on the downloads page without even showing functional Flatpak as an option?
I don’t really care what to use as long as it works. I realize it may be hard to maintain a native package for all OSes so taking a shortcut with something like flatpak makes sense.
I care about what to use because using various different package managers leads to confusion and clutter let alone duplication. Native packages are available for PMS, why not for Plexamp? It seems to me the solution is not to use your favorite package manager of the day but to work to reduce the number of package managers to 1. However, that would require the cats of Linux to herd and we all know that’s next to impossible.
To me it would make a hell of a lot more sense for package managers to be gates of installation for the various flavors of Linux whose input may be standardized but whose output - the actual placement and configuration of the installed package - would be indistinguishable from had the user installed the package with the native package installer.
I agree completely, but package managers like Flatpak, that provide all dependencies, are an easy shortcut for closed source apps like Plex that can’t rely on users to roll packages for their favorite OS or package manager.
Yes, if the package was rolled for your OS and sometimes only for specific version of your OS. There are a bunch of OSes that can use RPMs for example, but they often don’t specify libraries that one OS will have installed by default. Different OS might also provide a different version of the package that will satisfy dependency without it actually working.
Flatpak solves that by providing ALL dependencies. I thought Snap does the same, but apparently not. Plex is the only app I use either of these for so I don’t know much about them.
My point was that a big part of a package manager’s job is to manage the dependencies of the software being installed. Errors in specifying the proper dependencies notwithstanding.
Also, if a package manager has resolved all dependencies but the application fails to work then IMHO it’s the package manager (or probably better stated, the package maintainer) who has failed. I’d say the same thing for any package manager/maintainer who has failed to resolve ALL dependencies.
When upgrading to Ubuntu 22.04, firefox was only available via snap. I suspect they’ll be more coming but whether they will be snap, flatpack, or whatever and I contend that this will only serve to complicate and confuse matters.
Remember universal package systems? Although AppImage, the earliest universal package system, was first released in 2004, the concept did not capture much attention until a decade later, when Canonical released Snappy and Red Hat released Flatpak. Each was presented as the next generation of package managers, usable by any distribution, and as a means to reduce the number of rival technologies. Yet in 2020, both Snappy and Flatpak have receded into the background, and the deb and RPM package management systems continue to dominate Linux, leaving the question of why Snappy and Flatpak did not fulfill their promises.
Two quick searches on DistroWatch reveal that, out of the 273 active distros listed, 39 support Flatpak, and 35 support Snap packages. At first, those may sound like respectable numbers, until you realize that a much more arcane deviation from the norm, like distros that do not ship systemd, can boast 99 distros. Moreover, those figures consist mainly of major distros that support Flatpak and Snap – often both – but still depend primarily on traditional package managers.
You could similarly ask the Linux community to settle on a single distro. Given that there are already several installation methods available with a single distro, it seems standardizing on a distro is an easier prospect
The reason why HTPC/Desktop are not distributed as native packages but PMS is comes down to the difference between having a UI and not. A UI-based app has considerably more tight dependencies on libraries and the like installed and in particular tight dependencies on versions. So while PMS can be built once and packaged multiple times for a myriad of Linux distros (especially since we use musl), the same is not true of a UI app and would require building it in multiple configurations. So snap/flatpak allowed us to support much more distros that we were willing to target in build configurations.
With things like this, one wonders why we’ve yet to see Linux on the desktop really take off.
As per the flatpak link being missing from the downloads page, that needs to be corrected.
P.S. We will not be making an AppImage due to legal constraints.
Using Linux (most SUSE) as daily driver for over 20 years for work and play. Hardly ever see issues like these.
Don’t blame you for taking the shortcut, but to be fair a ton of other apps with similar complexities, do build and distribute OS specific packages. For example VLC and OBS. Linux varieties are only part of the problem here.
I actually think that something like Plex belongs perfectly in the browser, but I understand that it comes with a ton of limitations you have no control over.
I was speaking to how a lot of software isn’t available on Linux. The differences among distros add a significant burden on developers and many will just not see it being worth the extra work.
You are free to use the browser version but you will lose the MPV playback engine which is vastly superior to the media stack in any browser.
Aside from audio apps like DAWS and the like, I don’t see “a lot of software isn’t available on Linux”. What isn’t available on Linux for you?
What is this MPV playback engine I’m losing? I don’t see any difference between playing a video in Plex using a web browser and playing the same video on my Vizio (save the difference in the size of the screen).
