7

When I have a Chromium window open for a while, GNOME and/or just the Ubuntu dock loses track of it. Note in the screenshot how I have a window open but there is no orange dot next to Chromium on the sidebar. I can still interact with the window with the mouse, I can still Alt+Tab to it, but I cannot navigate to it with a click on the Chromium icon on the sidebar or using Super+1 (as it is on the top of the list), both of these actions open a new window as if it isn't currently running.

As on September 24, 2020, I was using Ubuntu 19.10 and GNOME Shell 3.34.1. But then later on, I upgraded to Ubuntu 20.04 and I'm still experiencing this issue.

enter image description here

Improve this question
9
  • Does this issue happen with any other app?
    – Random Person
    Oct 7, 2020 at 9:18
  • I've only noticed it with chromium, and it doesn't happen immediately. I have a hunch it might be related to when memory gets low and/or laptop sleep/suspend, but I haven't figured out a consistent repro.
    – jaltekruse
    Oct 7, 2020 at 13:48
  • Which version of Chromium are you using? Is it the latest version? What are the steps you followed to install Chromium?
    – Random Person
    Oct 7, 2020 at 14:22
  • BTW, what is the GNOME version which you have right now?
    – Random Person
    Oct 7, 2020 at 14:29
  • Version 85.0.4183.121 (Official Build) snap (64-bit) GNOME Shell 3.36.4 I believe that I installed it though the Ubuntu Software Center, here is how it reports there (although I know you can also install outside debs though the center too, so it's possible I did that). Channel: latest/stable, Version: 85.0.4183.121, Developer: Canonical, Source: snapcraft.io
    – jaltekruse
    Oct 7, 2020 at 15:09

1 Answer 1

Reset to default
5

https://github.com/micheleg/dash-to-dock/issues/910

It looks like this has been reported to the dash-to-dock project and is still open.

Thought it would be worthwhile to at least post the quick workaround mentioned in that github issue here until the devs can address the issue.

"Only way I've found to solve it when it happens is to do an "alt+f2" and type the "r" and enter to reload the entire gnome-shell."

Improve this answer
3
  • I've also run into this issue. It also happens with Atom which is based on Chromium. Have you found resolution in the last few months?
    – JimmyJames
    Feb 22, 2021 at 15:23
  • @JimmyJames Nope, unfortunately I'm still using this workaround.
    – jaltekruse
    Feb 23, 2021 at 2:01
  • I"m having this same problem with chrome and vscode but the your work around doesn't help.
    – trampster
    Nov 9, 2021 at 3:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .