Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strange window switching foreground/background behavior [$50 awarded] #251

Closed
jmssil opened this issue Jan 29, 2016 · 98 comments
Closed

strange window switching foreground/background behavior [$50 awarded] #251

jmssil opened this issue Jan 29, 2016 · 98 comments

Comments

@jmssil
Copy link

jmssil commented Jan 29, 2016

I've been experiencing difficulties with marco on Linux Mint 17.3. These problems did not happen after a recent fresh install, but soon afterwards.

It's hard to explain, but basically when I click to switch windows in the task bar (window list) the selected windows is not brought to the front, it stays in the back. So, it looks like I'm clicking on the correct window, but I'm clicking in one in the background.

It looks like the foreground/background + window switching logic is wrong.

Associated with this, there is a strange shadow between the maximized windows and the task bar. I'm attaching a screenshot.

screenshot at 2016-01-29 13 43 39


The $50 bounty on this issue has been claimed at Bountysource.

@jmssil
Copy link
Author

jmssil commented Feb 5, 2016

I found this happens only after running HexChat in a session, even if I close it afterwards.

@evaldas325
Copy link

Hi, this is biggest annoyance for me since upgrade to 1.12. I reproduce this bug constantly on Debian/testing desktop with dual monitor setup. Also I installed Linux Mint 17.3 on laptop and started to reproduce this problem as well. I do not use HexChat. I have 4 workspaces with lots of windows open. Have no idea what program/window causes this but this affects all windows opened on current workspace.

@flexiondotorg
Copy link
Member

I have experienced this on Ubuntu MATE 15.10 with MATE 1.12 installed. But, I'm using Compiz, so I don't think Marco is to blame.

@evaldas325
Copy link

Restarting Marco helps me. If I run into this weird window behavior, I execute " marco --replace" in terminal and the problem is gone.

@evaldas325
Copy link

In my previous message I said that executing "marco --replace" fixes the problem temporary until windows start switching to foreground/background again unpredictably.
However I've tried "marco --replace --no-composite" and it seems turning off compositioning solves the problem permanently.

@jmssil
Copy link
Author

jmssil commented Mar 12, 2016

However I've tried "marco --replace --no-composite" and it seems turning off compositioning solves the problem permanently.

I seem to confirm this.

@LearnLinuxTV
Copy link

I can also confirm this bug on Ubuntu MATE 16.04 with Marco. If it helps, the machine I encounter this on has a Haswell i7 CPU, 16GB RAM, Geforce GTX 760 video card. I have two other machines, both with Intel graphics, and I've never seen this issue on those machines.

@pasikarkkainen
Copy link

I'm seeing this same bug on Fedora 24. It seems to happen often (but not always) after switching workspace from the MATE workspace switcher applet.

So basicly after changing the active workspace some random window is on the foreground, but focus is actually on some background window.. so you think you're using/clicking the foreground window, but in reality all the actions go to the background window. The way to fix this is to minimize all windows from the workspace and then maximize/open the window you need. It's super annoying.

I didn't have this bug with Fedora 22, which obviously used older version of MATE/marco.

@LearnLinuxTV
Copy link

This bug was reported back in January. Has it been assigned to a developer yet, or are we just talking amongst ourselves?

@jmssil
Copy link
Author

jmssil commented Oct 24, 2016

From the column on the right, nothing has been made concerning this issue. It seems strange to me, since it seems a major regression, but I don't know how development in MATE/marco works.

@daemonblade
Copy link

It also happens with mate-1.12 on FreeBSD.

@allanlaal
Copy link

happens in Ubuntu 16.04 LTS too

@LearnLinuxTV
Copy link

What do we need to do in order to get this assigned to someone? MATE is too frustrating to use with this bug. I just tried upgrading MATE from the PPA but it's still not fixed. This happens so frequently for me that window navigation is a major nuisance. I'm going to try disabling compositing to see if that helps. If not, I may switch to GNOME, as this problem is not present there.

@raveit65
Copy link
Member

I'm seeing this same bug on Fedora 24. It seems to happen often (but not always) after switching workspace from the MATE workspace switcher applet.

I can't confirm this with f24 and Mate-1.16 (gtk3 version) and origin nvidia driver 940xxx.

It's hard to explain, but basically when I click to switch windows in the task bar (window list) the selected windows is not brought to the front, it stays in the back.

Since fedora 18 i'm building official fedora mate packages but i never run in this issue with my main box and my laptop (intel graphics).

@pilot51
Copy link

pilot51 commented Nov 16, 2016

Disabling compositing worked for me.

I am aware of two GUI methods to disable it in Mint 18:

  1. Preferences -> Windows -> uncheck 'Enable software compositing window manager'
  2. Preferences -> Desktop Settings -> Windows -> Window Manager -> pick 'Marco' (without + Compositing)

@raveit65
Copy link
Member

PS: i'm using always this settings.
[rave@mother ~]$ gsettings get org.mate.Marco.general auto-raise
true
[rave@mother ~]$ gsettings get org.mate.Marco.general focus-mode
'sloppy'

Maybe this is the reason why i never run in this issue.

@raveit65
Copy link
Member

If someone can provide steps to reproduce or a video i'm happy to use 'git bisect' to find a culprit commit which probably caused the issue since 1.10 of whatever.
Marco is independent to most other packages, so this should work if we know since what time the issue occurs.

@LearnLinuxTV
Copy link

The problem with reproducing this bug, is that I can't seem to find a way to reproduce it at all. Sometimes it happens, sometimes it doesn't. It happens most often when I switch to another workspace.

@pasikarkkainen
Copy link

Yep, it's hard to give exact information to reproduce. It happens randomly, but quite often, ie. usually many times per hour.

My environment currently is Fedora 24 Mate + two displays .. and it happens quite often after switching workspaces.

@jmssil
Copy link
Author

jmssil commented Nov 17, 2016

Try hexchat to see if it triggers the issue.

@raveit65
Copy link
Member

My environment currently is Fedora 24 Mate + two displays .. and it happens quite often after switching workspaces.

I don't have a second monitor to reproduce but i will connect my monitor to my laptop for a while.
...but i'm working normal on a powerful PC and all my confs aren't on my laptop, so i can't do that really a long time.
Any chance to work with one monitor for a while to see if the issue occurs?

Try hexchat to see if it triggers the issue.

Looks like a chance to switch configs from xchat to hexchat .

@raveit65
Copy link
Member

PS: Can you please test those settings?
#251 (comment)

@pilot51
Copy link

pilot51 commented Nov 17, 2016

I have two 1920x1080 monitors, 4 workspaces that I regularly switch between, and usually about a half dozen or so windows across all workspaces with a couple set to always show on visible workspace. The windows I usually have open are Mumble, Discord, Firefox, Steam, KVIrc, and often Caja and Xed. I've never used Hexchat. The issue was especially annoying when I was doing development with about twice as many windows. I never found reproducible steps, but I think it may have been related to switching between workspaces when there are windows overlaying each other.

@LearnLinuxTV
Copy link

The comment from pilot51 seems to mirror my setup. I have two displays and the problem happens when I switch from one workspace to another. I've seen this happen with MATE applications too, like Caja or Pluma for example. It's hard to reproduce on demand. I see this problem several times a day but window management also works as expected sometimes.

@fredo-m
Copy link

fredo-m commented Nov 18, 2016

Hi,

I had the same bug, I had opened a bug report on Debian's bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828077

I opened the bug against mate-panel, but it seems that marco is involved.

I have several applications open on my 5 workspaces including several in the same workspace. Application windows are open to the maximum, I click on the panel at the bottom of the screen to move from one application to another.

After a few hours of use, I have not found a trigger but it is necessary to be passed several times from one workspace to another, the application that is visible in a workspace is no longer clickable.
It seems that this is an application that is below that is clickable.
To find which application is clickable, I have to click one by one on all the buttons on the panel.

I do not know if it's related, but it appears the same time, the libreoffice main menu which is normally written in black is written in white.

Regards.

@LearnLinuxTV
Copy link

This bug doesn't appear to be assigned to anyone. What do we need to do, in order to get this bug assigned to a developer? It appears that we're just talking amongst ourselves.

@raveit65
Copy link
Member

This bug doesn't appear to be assigned to anyone. What do we need to do, in order to get this bug assigned to a developer? It appears that we're just talking amongst ourselves.

Be relaxed and google my nick name :-)

@LearnLinuxTV
Copy link

Sorry, I didn't notice you were listed as a developer. I'm glad you're looking at this.

@raveit65
Copy link
Member

I recommend to file out first a report at ubuntu at launchpad, to get ubuntu specific help ;-)

@alcarola
Copy link

What is not related to this report? The slowly responding ppa version? The OP fits my original problem perfectly.

Indeed, I guess I should ask the ubuntu people for help with finding a version of marco that works on my system. Thanks for the advice!

I have not seen the bug since I switched back to software compositing and ran those two gsetting commands, although the auto-raising of windows is rather annoying when you're not used to it.

@LearnLinuxTV
Copy link

@alcarola Your original issue was the window ordering bug mentioned in this report, however, that was solved already and a commit was created to fix it. If you have issues that start after installing a PPA, then your problem is with the PPA. Therefore, a bug report should be filed there.

@alcarola
Copy link

alcarola commented Jun 14, 2017

Indeed, thanks! :)

@owensss
Copy link

owensss commented Aug 22, 2017

I have the problem discribed at #257 and the fix don't work for me.
the two issues seems alike and perhaps have a same cause

$ marco --version
marco 1.18.1

@naturally-intelligent
Copy link

I keep running into this too, Ubuntu MATE 16.04, using Compiz. I don't know the cause, but last time it happened, it was from the standard popup after inserting a DVD.

To fix it in session, I opened Compiz Config -> General Options -> Focus & Raise, then turn on Auto-Raise, poke around, then turn it back off. Works for me without having to lose session - BUT - some windows seem to retain the unwanted behavior until interacted with twice.

@raveit65
Copy link
Member

Please file out a report against compiz at your distro.

@LearnLinuxTV
Copy link

I keep running into this too, Ubuntu MATE 16.04, using Compiz. I don't know the cause, but last time it happened, it was from the standard popup after inserting a DVD.

This bug was fixed in newer versions of MATE. Since Ubuntu MATE 16.04 is locked at an older version of MATE, it will not receive the fix for this. The only solution is to upgrade to a newer version of the distro.

There is a work-around, where you can try to change between software and hardware rendering in MATE tweak. One of them should stop this from happening, but I can't remember which.

@raveit65
Copy link
Member

This bug was fixed in newer versions of MATE. Since Ubuntu MATE 16.04 is locked at an older version of MATE, it will not receive the fix for this. The only solution is to upgrade to a newer version of the distro.

There is a work-around, where you can try to change between software and hardware rendering in MATE tweak. One of them should stop this from happening, but I can't remember which.

The guy use compiz WM, not marco :-)

@LearnLinuxTV
Copy link

The guy use compiz WM, not marco :-)

Ah, good point! For some reason, I forgot that those were separate.

I agree with raveit65, if you're using Compiz, file a bug against Compiz.

It may be useful to test a newer version of Ubuntu MATE to see if this has already been addressed. Keep in mind, 16.04 is approaching two years old now.

@naturally-intelligent
Copy link

naturally-intelligent commented Dec 19, 2017

This bug has come back to me even with the new NVIDIA drivers.

Same solution as above to save working session. (Compiz Config -> General Options -> Focus & Raise, then turn on Auto-Raise, poke around, then turn it back off.)

@spook
Copy link

spook commented Dec 21, 2017

And still there for Ubuntu 17.04 with marco 1.18.0, with or without the new NVIDIA drivers.
The workaround of disabling "software compositing window manager" still gets around the problem.

@raveit65
Copy link
Member

And still there for Ubuntu 17.04 with marco 1.18.0, with or without the new NVIDIA drivers.
The workaround of disabling "software compositing window manager" still gets around the problem.

Are you shure 17.04 use this fix or is your post more a blind-post (date)?

@raveit65
Copy link
Member

This bug has come back to me even with the new NVIDIA drivers.

Same solution as above to save working session. (Compiz Config -> General Options -> Focus & Raise, then turn on Auto-Raise, poke around, then turn it back off.)

Did you blame nvidia for this?
https://devtalk.nvidia.com/

@Dos98
Copy link

Dos98 commented Aug 6, 2018

This problem is in UBUNTU 18 also.
Anyone has solution to this problem.

@raveit65
Copy link
Member

raveit65 commented Aug 6, 2018

This problem is in UBUNTU 18 also.
Anyone has solution to this problem.

Yes,
file out a report against your distro + nvidia
I don't see this issue with fedora and nvidia driver.

@mate-desktop mate-desktop deleted a comment from jmssil Aug 6, 2018
@ego2dot0
Copy link

ego2dot0 commented Oct 2, 2019

This bug isn't solved. I am experiencing it on Fedora 30 and Mate 1.22.1 on an Ryzen 2500U with an AMD GPU.
I should be triggered by switching between workspaces. Maybe in condition with focus keeping apps like Remmina or VirtualBox.

@pasikarkkainen
Copy link

Same here. I still have this bug with marco in Fedora 30 (marco-1.22.2-1.fc30.x86_64).
I'm using Intel integrated graphics. Same issue happens on two different f30 systems.

@raveit65
Copy link
Member

raveit65 commented Oct 2, 2019

@pasikarkkainen @ego2dot0
Please do not hijack old and fixed bug reports.
Please open a new one and provide as much infos as possible.
Otherwise we can't help you.
I will lock this report.

Thank you.

@mate-desktop mate-desktop locked as resolved and limited conversation to collaborators Oct 2, 2019
@raveit65
Copy link
Member

raveit65 commented Dec 6, 2019

Fixed again in new released marco-1.22.4 and 1.23.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests