Important Information
I have a dual monitor setup and have noticed an issue with the latest mpv. When playing an mpv video on either monitor and making said video fullscreen, the bottom ~15% of the other monitor (the one without the mpv window) is covered in a black bar for a few seconds, then that entire monitor flickers once. I utilize Latte-dock, and whilst the mpv video is playing fullscreen, the dock on the second monitor has an ugly black border around it, and the dock animations (bouncing, zooming, etc) and any KDE screen-edge controls (like Show All Windows) are completely disabled until the mpv window is no longer fullscreen, at which point the second monitor goes black and flickers for a second or two before going back to normal and re-enabling all animations and window flair.
I am not utilizing any custom profiles as far as I know. This happens when I simply call mpv <URL> to watch a video for which I have the link, but also happens when using the ani-cli script which calls mpv in the background. It happens when the active mpv window is active on either monitor, causing whichever monitor is secondary to have the issues.
I've attached a screenshot that shows the latte-dock problem, and can provide a video upon request.
Here is my system info:
- mpv version : 0.34.0
- Linux Distribution and Version: Arch Linux
- Source of the mpv binary: Arch Linux community repository
- If known which version of mpv introduced the problem: 0.34.0 (current)
- Window Manager and version: KWin using KDE Plasma version 5.23.4, KDE Frameworks version 5.88.0, Qt version 5.15.2
- GPU driver and version: NVIDIA 2070 Super, driver 495.44-15 (from Arch Linux extra repository)
- Possible screenshot or video of visual glitches:

Reproduction steps
Issue IS reproducible with --no-config option.
Describe the reproduction steps as precise as possible. It's very likely that
the bug you experience wasn't reproduced by the developer because the workflow
differs from your own.
- Open a terminal window and call stock mpv with any url (no profiles, custom scripts, etc):
mpv <URL>
- Upon loading, in the mpv GUI, click the fullscreen option
Expected behavior
- mpv should make the video fullscreen without affecting the secondary
Actual behavior
- the mpv window goes fullscreen, but the secondary monitor freezes momentarily, the bottom ~15% of the screen is fulled with a black bar which then disappears when the window flickers, but latte-dock retains the black border around it, and all window and dock animations are completely disabled on the secondary monitor until the mpv window is no longer fullscreen
Log file
mpv_log.txt
The issue will be closed for ignoring the issue template.
Important Information
I have a dual monitor setup and have noticed an issue with the latest mpv. When playing an mpv video on either monitor and making said video fullscreen, the bottom ~15% of the other monitor (the one without the mpv window) is covered in a black bar for a few seconds, then that entire monitor flickers once. I utilize Latte-dock, and whilst the mpv video is playing fullscreen, the dock on the second monitor has an ugly black border around it, and the dock animations (bouncing, zooming, etc) and any KDE screen-edge controls (like Show All Windows) are completely disabled until the mpv window is no longer fullscreen, at which point the second monitor goes black and flickers for a second or two before going back to normal and re-enabling all animations and window flair.
I am not utilizing any custom profiles as far as I know. This happens when I simply call
mpv <URL>to watch a video for which I have the link, but also happens when using the ani-cli script which calls mpv in the background. It happens when the active mpv window is active on either monitor, causing whichever monitor is secondary to have the issues.I've attached a screenshot that shows the latte-dock problem, and can provide a video upon request.
Here is my system info:
Reproduction steps
Issue IS reproducible with
--no-configoption.Describe the reproduction steps as precise as possible. It's very likely that
the bug you experience wasn't reproduced by the developer because the workflow
differs from your own.
mpv <URL>Expected behavior
Actual behavior
Log file
mpv_log.txt
The issue will be closed for ignoring the issue template.