pop-os / pop

A project for managing all Pop!_OS sources

Home Page:https://system76.com/pop

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Exact same Firefox window is duplicated / rendered on every workspace

Rick1029 opened this issue · comments

Distribution (run cat /etc/os-release):
PopOS 22.04

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
Gnome-shell 42.5-0ubuntu1pop1~ 1675984688 ~22.04 f574f54
Cosmic-workspaces 0.1.0
1712161020 ~22.04 ~e928053
X11
Issue/Bug Description:
Firefox duplicates across all workspaces - this has only happened to me once but I found a similar issue on the Brave browser issue tracker under Fedora running Gnome, so I have reason to believe this is an issue caused upstream in Gnome. I'm curious if it happens on Wayland but I have no idea how to reproduce it.

image
As you can see, this github page where I am reporting is duplicated on every workspace. I can start typing in my top workspace and finish exactly where I left off, with my cursor still blinking, in another, which insinuates it is exactly the same window and not just a copy of the window. Editing one workspace makes the same changes on another (to do with this browser window only) Closing the window stops the effect for that window and closes it on every workspace, opening new windows doesn't necessarily mean the effect returns. Creating a new workspace (moving some application, regardless of whether its Firefox or not, to another workspace,) duplicates the already duplicated windows onto the new workspace. The new application is unaffected. It's possible to have the duplicate window in its own workspace, but not to have two on the same one, if you do that the effect disappears completely and they stop being duplicated.

Steps to reproduce (if you know):
No clue. I opened Firefox from a suspend that followed a restart to switch graphics from integrated to hybrid.

Expected behavior:
Don't duplicate (though its a little fun)

Other Notes:

Always on visible workspace was not enabled! Though enabling it shows the exact same situation, so maybe it was enabled without showing it was?