Arch Linux DDE weird behaviour of wm

[ShellbackII]

Hello!

I have a little problem that is anoying me a little.

When I have more than one window open and click inside one that is not in focus, that window will have focus, I can use it like normal, but it does not rise up above other windows. The only way I have to raise it is to click on the titlebar of the windows. Only then will the window get raised.

I have tried to set different settings in dconf-editor without any success. I can though set focus to follow the mouse, and then windows will rise as fast I hoover the mouse over them, but that is not my prefered way.

I have also tried to make a new user, but still nothing different :(

Does anyone have a clue?

(if you whant more info/data, just ask ;)

[fasheng]

How about this:

gsettings set com.deepin.wrap.gnome.desktop.wm.preferences raise-on-click true

[felixonmars]

or something like #95

[sonald]

It is weirder that it never occurs on my laptop, and there are so many focus problems since the gtk update. It may related to that.

[ShellbackII]

fasheng: That is one of those settings I have checked in dconf-editor. It is set to true, I have even tried to set it to false and back again to se if it changes anything but to no luck :(

felixonmars: I don't understand that page. Think that I'm missing support (and knowlege) of the language used.

[hualet]

Several users complained the focus issue to me on Telegram yesterday.

[felixonmars]

@ShellbackII You can try to switch to the 2D window manager, which some user used to workaround this.

[fasheng]

I must say, it's fine in my archlinux. Btw, I use the deepin gtk theme.

[felixonmars]

@fasheng It works fine at the beginning, but could be weird after a certain amount of time. Still not sure what happened during the period.

[ShellbackII]

@felixonmars I have now tried to switch to deepin-metacity, but that didn't make any difference either I'm afraid :(

[sonald]

then It indicated that the focus problem is not related to mutter at all. it's deep down in the gtk probably.

[hualet]

@felixonmars Have you seen similar issues reported to GNOME Shell ?

[felixonmars]

No as far as I know.

[ShellbackII]

The update of deepin-mutter to 3.20 arrived to me today, and with that the problem got solved.

Probably something with gtk and the previous version of the wm that didn't play well enough together. Anyway, problem solved!

[fasheng]

Great job!