plexinc / plex-media-player

Next generation Plex Desktop/Embedded Client
GNU General Public License v2.0
1.16k stars 170 forks source link

PMP on Windows is having a major UI glitch #991

Closed flying-sausages closed 3 years ago

flying-sausages commented 3 years ago

FYI the log instructions do not have any new logs since September last year. I've been using PMP even after this, obviously.

Test environment

PMS Version: 1.20.3.3421-54b6523bd (Ubuntu 20.04 server) PMP Version: 1.20.0.1406-f47a81b7 Platform (Windows/macOS/Embedded RPi/Embedded Intel): Windows 10

Steps to reproduce

  1. Open app
  2. Hover over cover, or observe the On Deck cards
  3. Try play video

Current behavior

Expected behavior

image

ezgif com-video-to-gif

This persists after re-install. I retrieve my PMP install from Chocolatey

flying-sausages commented 3 years ago

More flippage image

flying-sausages commented 3 years ago

Also, the broken video is a consistent error code 4294967280

mseeley commented 3 years ago

There's a lot to unpack here. The first step is to resolve which app you're running and grab a new version. Please share a screenshot of the Settings > General screen it should include an application version.

Please replace all Plex for Windows / PMP versions from Chocolatey with the official downloads. We've never seen this issue before and would like to rule out the Chocolatey.

flying-sausages commented 3 years ago

I've already tested this with the official download from your site and it was reproducing.However the issue stopped reproducing itself and it's the weirdest thing ever.

I have WSL2 installed on my ARM machine, tried to play with some VBox machines, and had to disable hypervisorlaunchtype in bcdedit.exe. So when I set it back to bcdedit /set hypervisorlaunchtype auto it all goes back to normal after restart.

I'm absolutely clueless how this is in any way related. Something something Hyper-v, something something Windows. Hope there's a slight chance this helps.

mseeley commented 3 years ago

Thanks for replying 👍

We've been unable to reproduce similar behavior on non VM setup. It's too esoteric of an issue to dive deeply into. Please feel free to update this issue over time with any additional root cause info.