| Summary: | Second monitor misbehaves when YouTube is played in fullscreen on the other monitor | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Chris King <chris> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | dragoiu.bogdan, nate |
| Priority: | NOR | Keywords: | multiscreen |
| Version First Reported In: | 6.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Chris King
2024-10-23 04:27:19 UTC
After exiting YouTube fullscreen, if I go into the Display Configuration and disable the affected monitor, apply the changes, then re-enabling the monitor again; then I can avoid rebooting the computer. Rebooting will also remediate the display issue. Turning the monitors off/on or removing the HDMI cables has no affect Hi Chris, I might have had the same bug and had opened a bug with no success with Firefox. Is the behaviour similar to mine? https://bug1925340.bmoattachments.org/attachment.cgi?id=9431651 Also a workaround you could try is starting firefox with `MOZ_ENABLE_WAYLAND=0`. This will change the window protocol from wayland to xwayland and was how I could keep using firefox since the Plasma or Firefox update introduced the issue. I could also reproduce the issue with a fresh secondary account and was recreating my desktop layout until I found that setting the fractional scaling values for the screen seemed to the culprit. For me one screen is 120% and the misbehaving one is 110%. In trying to see if I could flip which screen goes bad I messed around with the values and this seems to have fixed my problem. So maybe a more permanent fix could be messing with the scaling values again and see if this magically clears whatever caused the issue. Bogdan (In reply to Bogdan Dragoiu from comment #2) > I might have had the same bug and had opened a bug with no success with > Firefox. Is the behaviour similar to mine? > https://bug1925340.bmoattachments.org/attachment.cgi?id=9431651 Yes, this does look like the same behaviour > Also a workaround you could try is starting firefox with > `MOZ_ENABLE_WAYLAND=0`. This will change the window protocol from wayland to > xwayland and was how I could keep using firefox since the Plasma or Firefox > update introduced the issue. I just tried starting with MOZ_ENABLE_WAYLAND=0 firefox MOZ_ENABLE_WAYLAND=1 firefox and both of these behaved correctly, so then I went an tried firefox from the icon and it also worked correctly for a while and then the second monitor bugged out after a few minutes, so it looks like a can't reproduce this 100% of the time anymore. The only new change is Yesterday, firefox updated to 132.0. The release notes for firefox 132.0 https://www.mozilla.org/en-US/firefox/132.0/releasenotes/?utm_source=firefox-browser&utm_medium=firefox-desktop&utm_campaign=about-dialog do not mention anything specific to wayland, and the closest change that may have some effect is "The getCapabilities method allows applications to gather the media capabilities supported for the live MediaStreamTrack." > I could also reproduce the issue with a fresh secondary account and was > recreating my desktop layout until I found that setting the fractional > scaling values for the screen seemed to the culprit. For me one screen is > 120% and the misbehaving one is 110%. In trying to see if I could flip which > screen goes bad I messed around with the values and this seems to have fixed > my problem. The 110% we have in common > So maybe a more permanent fix could be messing with the scaling values again > and see if this magically clears whatever caused the issue. After futher extended testing, I can still reproduce the problem via starting firefox from the icon or with command line: > MOZ_ENABLE_WAYLAND=1 firefox However starting with command line: > MOZ_ENABLE_WAYLAND=0 firefox is preventing the issue from occurring over the extended time While this can be bypassed in this manner, it is not a convenient way to start the app |