This issue is across Flatpak and the other one err… Snap I believe it’s called? so we’re 3 years in and no further than before with this issue… Whatever caused it jumping from v1.47 to a regression and the Dev’s didn’t spot it to begin with is just totally unforgivable.
I’m thinking that if this issue was on Windoze then it would’ve been fixed from the first update?
So for the moment, and for whatever reason I’m forced to use the HTPC version or the dreaded web browser (Way to much transcoding!) The HTPC version on a Laptop is clunky and awkward, but doesn’t cough up the display issues… COME ON DEV’s there has to be at least one that’s available to fix this simple issue instead of pouring all the resources into the Roku app…
Well playing devil’s advocate here. Lets be honest. Linux is still a niche market with a rapid development environment needing to support multiple distros. I don’t blame any company who would rather focus on Windows/OSX/IOS/Android first as those alone probably accounts for 90% of their users.
HOWEVER. 2-3 years in is nuts. That borders on abandonware.
2 Likes
I agree with you on the “Abondonware” sad thing is it was getting updated better as an Appimage on another site than it did officially on here! I’ll never move away from Linux, I’ll just keep running the HTPC app or the web browser version, the only time I use Plex on the daily driver is in the evening when I want to watch a movie with headphones on, the rest of the time it’s either Android or Roku, but as we’ve both pointed out, this isn’t the point though, if Plex release an app, in reality they should either keep it up to date and fix, or pull the plug on it.
I’ve tried the workarounds from above threads without any success, it’s like playing “Ping Pong” on an old 70’s console still… live in hope is my motto!!!
Ya, I’ve completely given up on the plex client for Linux. I distro hop a lot, and every.single.desktop… doesn’t matter what distro, does this. So annoying. I think the sound not being controllable at first was bad… but this glitching is pre-alpha stuff. So ya, gave up and unfortunately have to use the crappier web interface, but it doesn’t always glitch out and need a restart.
1 Like
came here to check years after, problem still not fixed, how amazing is that 
The pile of crap is somehow actually getting worse on Fedora 42.
its getting worse on all linux distro
So for all Linux distributions there are only 2 solutions, the buggy flatpak or pay to transcode your media in the web interface?
In my experience, the white squares happen while browsing libraries and does not happening during video playback.
when is this going to get fix
We’ve been having this problem for about a year or so, only with Linux Plex Player, including v 1.109.0.329, and only in the video player grid area (random white blocks, particularly over player controls that come and go and sometimes persist and cover the picture). The problem does not occur with Plex HTPC or Plex Web (Firefox, Chrome). Very frustrating, as the Plex Player was our preferred app for the living room htpc.
Ubuntu 22.04.5 LTS
NVIDIA Corporation GP108 [GeForce GT 1030]
X11
Just started the transition off of Plex. This is going to take the better part of a year to do as migration and cleanup isn’t going to happen overnight. Also getting my family onto remote access is going to be difficult to enable SSL security, but not impossible. But clearly Plex has no interest in either addressing this, or acknowledging there is a bug and reporting it to whoever. I’m done with this crap. The other competing software’s client has zero issues with what I’ve seen over the last week of use.
Meanwhile…
This issue is still present in the linux flatpak.
Also have been experiencing this for several years. Really annoying.
That looks more like video corruption. I believe it would be a different issue.
Experiencing the same issue on my desktop
Linux Mint 22.1 (Cinnamon)
AMD 5800X
AMD RX6800
Also on my NUC running mint 22.1 xfce which uses Intel CPU and integrated graphics.
Not sure why an issue like this has lasted so long, that’s pretty disheartening to see.
when will this get fix
The error message in the log whenever a white square appears:
ERROR:shared_image_representation.cc(207)] Attempt to read from an uninitialized SharedImage
