Complete failure here. Plexamp eventually finds (local and healthy) server. Authenticate, must restart Plexamp. Now shows some recently played stuff from my server, nice. Click any, screen goes dark chocolate. No visuals, no audio. No window resize, no move, nothing.
Complete no-joy.
Must kill application. Same as before upon restart, reboot, whatever. Plex web player is fine.
How can I diagnose this? Suggestions welcome.
I’m trying to help another user that’s having issues on Debian Stretch. It didn’t work for him, but try running the AppImage with the --disable-gpu flag.
My continued thanks for your suggestions. --no-sandbox made no difference, but there are errors shown on the console. Maybe someone can make sense of these?
$ ./Plexamp-3.0.0.appimage --no-sandbox
xdg-mime: application argument missing
Try 'xdg-mime --help' for more information.
Couldn't install shortcut for MediaPlayPause.
Couldn't install shortcut for MediaPreviousTrack.
Couldn't install shortcut for MediaNextTrack.
Started Media Service: false
Linux: Registering MPRIS service.
[31223:0418/082315.586909:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
(node:31231) 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:31231) 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
Checking for update
(node:31231) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:31231) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Update for version 3.0.0 is not available (latest version: 3.0.0, downgrade is disallowed).
checkForUpdatesAndNotify called, downloadPromise is null
System info shows OpenGL as version “4.6 (Compatibility Profile) Mesa 20.0.4” with amdgpu kernel module.
So, I wanted to check if the issue is on my system, as I’m considering make a fresh install to the lastest version of fedora.
I booted on a live Fedora 32 and I have exactly the same behavior.
So, as mentioned with the previous version, the appimage is not really portable. You need to have the same libs that the linux version it was developed on …
A work around seems to provide those libs to the app manually:
But find those will be hit and miss job and shouldn’t be users job, particularly for a feature offered only for premium users.
@kvern many thanks for the effort you have put into investigating and sharing your findings; much appreciated.
I couldn’t find compat-openssl for OpenSuse tumbleweed and didn’t want to risk breaking SSL, which I depend upon for other things.
But this morning brought an update to libpangox-1_0-0 and Plexamp (now 3.0.2), so I was hopeful but at no avail. Still fails with the same UI symptom (grey UI, nothing happens) but it seems as if the console output is more promising.
Still shows “[7723:0501/085616.459713:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command”, which I thought you had diagnosed as the SSL issue…?
Is it possible to wipe all trace from previous Plexamp attempts from the computer and try again from scratch with the latest?
FTR I still have the same grey-window problem on Debian 9, plexamp 3.0.2
I have tried all the suggestions in this thread (and others), including the SSL version bypass. All of these decrease the warnings on stdout but none of them fix the grey-screen issue.
Main problem is there appears to be no other logging? Is this true? The older plexamps were so nicely verbose.
Another thing I’ve noticed is in my /var/log/messages there’s a kernel trap reported related to the plexamp process. If anyone wants me to track that down further LMK.