Plexamp v3.4.4 AppImage crash

Plex Labs
1

Server Version#: 1.22.1.4228
Player Version#: v3.4.4
OS: Fedora 33

The v3.4.4 AppImage won’t start, it crashes trying to find a dev electron file. Here is the stacktrace:

Error: Error: ENOENT: no such file or directory, open '/dev-app-update.yml'
    at A.B [as _captureStackTrace] (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:339676)
    at ret (eval at _ (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:378030), <anonymous>:6:21)
    at /tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:74517
    at Generator.next (<anonymous>)
    at Generator.u (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:2143)
    at f._promiseFulfilled (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:263584)
    at /tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:265611
    at e.AppImageUpdater.loadUpdateConfig (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:74552)
    at e.Lazy.<anonymous> (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:69795)
    at e.Lazy.get value [as value] (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:2:181102)
    at /tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:72332
    at Generator.next (<anonymous>)
    at Generator.u (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:2143)
    at f._promiseFulfilled (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:263584)
    at A._settlePromise (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:213679)
    at A._settlePromise0 (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:214277)
    at A._settlePromises (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:215629)
    at f (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:217222)
    at h (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:217161)
    at a._drainQueues (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:218681)
    at Immediate.drainQueues (/tmp/.mount_Plexam9cCndQ/resources/app.asar/main.js:1:216903)
    at processImmediate (internal/timers.js:439:21)
2

Update on this issue:

It seems that this happens because I’m a developer, and I have NODE_ENV=development set globally. If I launch the AppImage like this: NODE_ENV=production ./Plexamp-3.4.3.AppImage, I don’t have that crash anymore. However, there seems to be another issue, this time with glibc.

Here is the new stacktrace:

Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
Started Media Service: false
Linux: Registering MPRIS service.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
(node:39505) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:39505) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information

I’m on the latest Fedora so I have a recent glibc, that seems to cause a problem with Chromium/Electron according to this GitHub issue for RStudio: syscall 0230 error on (arch)linux · Issue #6379 · rstudio/rstudio · GitHub

3

Update #2:

I have managed to make it run on my system, using the Flatpak version, here: Flathub—An app store and build service for Linux

Although I still have to manually set the NODE_ENV variable to production, or else the app doesn’t start because of the crash ENOENT: no such file or directory, open '/dev-app-update.yml'.

So, to make it work, I run: NODE_ENV=production flatpak run com.plexamp.Plexamp.

I hope this may help other users with the same problem!

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.