This has been happening for a few months, but I stuck with Mutter 43.2.2.
Today I got the latest update, and Mutter was upgraded and I am not able to downgrade.
This is the most annoying bug. Any solutions?
If that is like I got yesterday:
Using Dash-To-Dock ==> starting one app was o.K., second DtD did not react…
but if I klicked Mouse on the second screen, it worked again. using XOrg.
Then I deletetd /home/(username)/.cache directory and did “strg F2”
then this error had gone; might be coincidentally?
I didn’t think it’s related.
I also happens in a brand new live USB.
1 Like
Seems “error” has gone since one of the latest updates (I am on unstable).
But:
swap monitors physically/electical (Main <==> second) - a certain combination had strange effects
(tested last year) maybe the “faster reacting” screen winns to become the main-screen?
Thanks for the suggestion, I tried this but it did not work.
So mutter is not the point, as Packages
shows latest version to test is 44.2-1 (unstable)
Switching from former versions (v80)of DtD to latest (82-1) had this effekt
( https://github.com/micheleg/dash-to-dock/releases )
==> any difference free / non-free drivers?
It happens even if I disable Dash to Dock.
The last version of mutter that worked properly was 43.2.2. Every version after that had the same bug.
Possibility to complain at:
https://gitlab.gnome.org/GNOME/mutter/-/issues
I cannot confirm the bug any longer (Repo unstable)
?? (search term: focus second monitor
Thanks for the taking the time. I will try and make a post, even though it seems to be ignored.
I tried your other link but it did not work.
What mutter version do you have in unstable?
You tried replicating it and did not have the same bug?
https://packages.manjaro.org/?query=mutter
Version: 44.2-1
Do not be afraid to use the “search” function of the Forum,
you are not alone - some to many problems are solved already. 
EDIT:
before switching to unstable, please use “TimeShift” (restore-point-Programm)
(falls Sie Psycho-Therapeut sind: Computer ticken anders)
I’ve searched the entire internet and still no solution for this. Only temporary hack arounds.
I installed Mutter 44.2.1, and it still happens.
I won’t risk moving to unstable for now, I will wait.
How did you know I am a psychotherapist?
Yet you’ll risk blindly downgrading random packages which is unsupported and guaranteed to cause breakage? 
1 Like
Of course not. 
That package is not available in the stable branch. You can’t cherry pick random packages, either.
If you want to actually receive support, Please reset to the default packages in the stable repo or switch to testing or unstable.
sudo pacman -Syuu
Let us know when you’re in a supported state and which branch you chose.
1 Like
Thanks for taking the time.
I switched to unstable, but the issue was still there.
Tried something using dconf-editor…
changed the key:
/org/gnome/shell/extensions/dash-to-dock/preferred-monitor-by-connector
from "DisplayPort-0 " to “primary” - "primary is the default - but DtD resets it to “DisplayPort-0”
as soon as I change this key.
Afterwards both screen focus as expected, but this may be not a solution?!
/org/gnome/mutter/focus-change-on-pointer-rest - what isthis good for?
Mine is set to primary. The other setting did not help, unfortunately.
Then this is a case for @Yochanan
Giving up… 
EDIT:
One last workarround:
Goto Tweaks ==> “keyboard and mouse” ==> mouse click emulation
and select the third entry.
Then goto “windows” ==> “window focus” and select the second entry.
Just saw the edit.
That’s the workaround I have been using since the issue came up.
It keeps me workflow productive, but it’s not a real fix.
Thank you!
Edit:
It seems here that the issue has been fixed:
Any idea on how I can update to a version that includes the fix? In which version of mutter will it be included?
Has it been release yet? I can’t tell.
1 Like