Plexamp Javascript Error

Plex Labs
1

Server Version#:

Version 1.40.1.8227

Player Version#:
Plexamp 4.10.1

OS:
Linux (Arch/EndevaourOS)

Since yesterday when I start plexamp I get this errormessage:

A JavaScript error occurred in the main process

Uncaught Exception:
Error: Cannot send message, stream is closed

at EventEmitter.self. message (/app/bin/plexamp/resources/
app.asar/node_modules/dbus-next/lib/connection.js:139:15)

at MessageBus.send (/app/bin/plexamp/resources/app.asar/
node_modules/dbus-next/lib/bus.js:371:22)

at EventEmitter.<anonymous> (/app/bin/plexamp/resources/
app.asar/node_modules/dbus-next/lib/bus.js:153:14)

at EventEmitter.emit (node:events:517:28)

at /app/bin/plexamp/resources/app.asar/node_modules/dbus-next/
lib/connection.js:116:14

at Socket.<anonymous> (/app/bin/plexamp/resources/app.asar/
node_modules/dbus-next/lib/message.js:63:9)

at Socket.emit (node:events:517:28)

at emitReadable_ (node:internal/streams/readable:601:12)

at processTicksAndRejections (node:internal/process/task_queues:
81:21)

AL

Followed by another error message

A JavaScript error occurred in the main process

Uncaught Exception:
Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:
160:15)
at writeGeneric (nod
at Socket. iteGeneric (node:net:
at Socket._write (node:net:974:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Socket.Writable.write (node:internal/streams/writable:337:10)
at EventEmitter.self. message (/app/bin/plexamp/resources/
app.asar/node_modules/dbus-next/lib/connection.js:141:14)
at MessageBus.send (/app/bin/plexamp/resources/app.asar/
node_modules/dbus-next/lib/bus.js:371:22)
at handleGetProperty (/app/bin/plexamp/resources/app.asar/
node_modules/dbus-next/lib/service/handlers.js:100:7)

internal/stream_base_commons:151:3)
111)

I can acknowledge both errors and the player starts. So far I think only the global hotkeys are not working anymore.

2

Are you using the Flatpak or AppImage?

3

Flatpak Version.
But because of unknown reasons (probably some update, but can not say which one) the error disappeared. So all is good.
/close

4

No changes on the Plexamp side in this timeframe, so must’ve been something underlying in Arch.

Bugs that fix themselves are my favourite kind of bug. Thanks for letting us know!

5

New information has arisen.

The bug has returned and I now have further details regarding when it appears. The mentioned errors appears when plexamp hasnt played anything yet and tries to play a downloaded playlist as the first song. So either when plexamp starts with no last song on deck and I then try to play a downloaded playlist. Or the last song was from said playlist and is still on deck and start plexamp.

This does not happen with all other sources aka library radio, an album, etc.

6

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