gnome-shell crash opening a new browser tab while having a fullscreen video in another tab
Affected version
- OS: Arch Linux
- Gnome Version: 3.38 and higher
- Issue appear on both XOrg and Wayland with different behaviors
Bug summary
It's kinda tricky to explain since I've been able to reproduce this behavior on browser, games and other fullscreen applications, but the easiest way to notice and reproduce the issue it's using a browser. When I have a fullscreen video reproducing in a browser window (eg a youtube video), and I keep that window in a separated workspace, and from another workspace i do something that triggers the opening of a new browser tab (eg opening a link from an email, or launching a google search from programs like albert), gnome crashes and have a different behavior depending whether you're running on XOrg or Wayland. On XOrg simply restart gnome-shell, on Wayland, since it's impossible to restart gnome-shell, the entire session crashes to a black screen with a line of random characters on top, and the only recovery it's to kill the gnome session from another tty and open another one.
I've noticed that his happens only when the video it's full screen (for example pressing F on youtube), and not the entire browser (what happens when you press F11). I've also noticed that this DOESN'T happen on gnome Web, but it's perfectly reproducible on Firefox and Chrome.
Another scenario where this bug present it's having a game in fullscreen loading, switching to another desktop, and when the game finally load and tries to switch you in the game window, gnome crashes.
Steps to reproduce
- Open a youtube video on Firefox or Chrome
- Press F to make it full screen
- Switch to another desktop
- Open a link from another app, such a link from an email on Evolution
What happened
gnome crashed, on XOrg restarted gnome-shell, on Wayland got a black screen with a line of random characters
What did you expect to happen
Just open a new tab in the browser
Relevant logs, screenshots, screencasts etc.
I've had some troubles getting a stack trace for the entire gnome-shell, but if needed I can retry to get one