Bug 446493 - Firefox window turns blank after Minecraft goes fullscreen
Summary: Firefox window turns blank after Minecraft goes fullscreen
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.23.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-04 23:21 UTC by evanmohr22
Modified: 2023-09-06 10:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description evanmohr22 2021-12-04 23:21:21 UTC
SUMMARY
***
Once Minecraft goes fullscreen or leaves fullscreen, my Firefox tab on my second monitor turns blank until I mouse over it. I demonstrated it on YouTube, but it occurs on all webpages. I was also using a third party launcher, but the issue also occurs on the official Minecraft launcher.  I tried to recreate the issue in Cyberpunk 2077, but the issue didn't occur. It may be something more specific to Minecraft rather than affecting all fullscreen programs.
***


STEPS TO REPRODUCE
1. Open Firefox on a second monitor (I'm not sure if it is actually a problem with second monitors, but it would only be noticeable for those who have one)
2. Launch Minecraft into fullscreen

OBSERVED RESULT
Firefox tab turns blank, could take a few seconds to actually update.

EXPECTED RESULT
My firefox tab would continue displaying as normal.

SOFTWARE/OS VERSIONS
Linux: 5.15.6
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Nvidia Driver 495.44 on X11
Comment 1 evanmohr22 2021-12-04 23:22:59 UTC
IMPORTANT: Forget to link video of the issue - https://youtu.be/a0mdbBPtyPo
Comment 2 evanmohr22 2021-12-06 01:25:33 UTC
Edit: And it's just not Minecraft. The issue has also occurred with Team Fortress 2.
Comment 3 David Edmundson 2023-09-06 10:38:16 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.