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 · 94 comments

Comments

Projects
None yet
@jmssil

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

This comment has been minimized.

Show comment
Hide comment
@jmssil

jmssil Feb 5, 2016

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

jmssil commented Feb 5, 2016

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

@evaldas325

This comment has been minimized.

Show comment
Hide comment
@evaldas325

evaldas325 Feb 11, 2016

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.

evaldas325 commented Feb 11, 2016

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

This comment has been minimized.

Show comment
Hide comment
@flexiondotorg

flexiondotorg Feb 19, 2016

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.

Member

flexiondotorg commented Feb 19, 2016

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

This comment has been minimized.

Show comment
Hide comment
@evaldas325

evaldas325 Mar 3, 2016

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

evaldas325 commented Mar 3, 2016

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

@evaldas325

This comment has been minimized.

Show comment
Hide comment
@evaldas325

evaldas325 Mar 9, 2016

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.

evaldas325 commented Mar 9, 2016

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

This comment has been minimized.

Show comment
Hide comment
@jmssil

jmssil 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.

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.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 May 24, 2016

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.

jlacroix82 commented May 24, 2016

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

This comment has been minimized.

Show comment
Hide comment
@pasikarkkainen

pasikarkkainen Oct 21, 2016

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.

pasikarkkainen commented Oct 21, 2016

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.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Oct 23, 2016

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

jlacroix82 commented Oct 23, 2016

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

@jmssil

This comment has been minimized.

Show comment
Hide comment
@jmssil

jmssil 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.

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

This comment has been minimized.

Show comment
Hide comment
@daemonblade

daemonblade Oct 27, 2016

It also happens with mate-1.12 on FreeBSD.

daemonblade commented Oct 27, 2016

It also happens with mate-1.12 on FreeBSD.

@allanlaal

This comment has been minimized.

Show comment
Hide comment
@allanlaal

allanlaal Nov 15, 2016

happens in Ubuntu 16.04 LTS too

allanlaal commented Nov 15, 2016

happens in Ubuntu 16.04 LTS too

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Nov 16, 2016

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.

jlacroix82 commented Nov 16, 2016

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Nov 16, 2016

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).

Member

raveit65 commented Nov 16, 2016

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

This comment has been minimized.

Show comment
Hide comment
@pilot51

pilot51 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)

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Nov 16, 2016

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.

Member

raveit65 commented Nov 16, 2016

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Nov 16, 2016

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.

Member

raveit65 commented Nov 16, 2016

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.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Nov 17, 2016

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.

jlacroix82 commented Nov 17, 2016

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

This comment has been minimized.

Show comment
Hide comment
@pasikarkkainen

pasikarkkainen Nov 17, 2016

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.

pasikarkkainen commented Nov 17, 2016

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

This comment has been minimized.

Show comment
Hide comment
@jmssil

jmssil Nov 17, 2016

Try hexchat to see if it triggers the issue.

jmssil commented Nov 17, 2016

Try hexchat to see if it triggers the issue.

@raveit65

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Nov 17, 2016

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 .

Member

raveit65 commented Nov 17, 2016

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Nov 17, 2016

Member

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

Member

raveit65 commented Nov 17, 2016

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

@pilot51

This comment has been minimized.

Show comment
Hide comment
@pilot51

pilot51 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.

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.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Nov 18, 2016

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.

jlacroix82 commented Nov 18, 2016

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

This comment has been minimized.

Show comment
Hide comment
@fredo-m

fredo-m 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.

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.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Nov 18, 2016

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.

jlacroix82 commented Nov 18, 2016

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Nov 18, 2016

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 :-)

Member

raveit65 commented Nov 18, 2016

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 :-)

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Nov 19, 2016

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

jlacroix82 commented Nov 19, 2016

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

@muktupavels

This comment has been minimized.

Show comment
Hide comment
@muktupavels

muktupavels Apr 22, 2017

Contributor

Not a solution, I know, but why not use Metacity if it works?

Contributor

muktupavels commented Apr 22, 2017

Not a solution, I know, but why not use Metacity if it works?

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Apr 24, 2017

Not a solution, I know, but why not use Metacity if it works?

It doesn't work that well, as it's not well-integrated. For example, there's no way that I know of to customize workspaces. I think it's best to fix the native MATE solution if we can.

jlacroix82 commented Apr 24, 2017

Not a solution, I know, but why not use Metacity if it works?

It doesn't work that well, as it's not well-integrated. For example, there's no way that I know of to customize workspaces. I think it's best to fix the native MATE solution if we can.

@raveit65

This comment has been minimized.

Show comment
Hide comment
Member

raveit65 commented May 2, 2017

raveit65 added a commit that referenced this issue May 10, 2017

Revert "compositor: fix possible crash closing/destroying window"
This reverts commit 768fdd8.

fixes probably "strange window switching foreground/background behavior"
#251

raveit65 added a commit that referenced this issue May 10, 2017

raveit65 added a commit that referenced this issue May 10, 2017

Revert "compositor: fix possible crash closing/destroying window"
This reverts commit 768fdd8.

fixes probably "strange window switching foreground/background behavior"
#251
@raveit65

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 May 10, 2017

Member

fixed in
master 38940ed
1.18 18e28b0
and 1.16 e1aa4ec
New releases coming soon.
Please test and blame me if you think it isn't fixed ;-)

Member

raveit65 commented May 10, 2017

fixed in
master 38940ed
1.18 18e28b0
and 1.16 e1aa4ec
New releases coming soon.
Please test and blame me if you think it isn't fixed ;-)

@raveit65 raveit65 closed this May 10, 2017

@flexiondotorg flexiondotorg changed the title from strange window switching foreground/background behavior [$50] to strange window switching foreground/background behavior [$50 awarded] May 24, 2017

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Jun 12, 2017

I apologize that I haven't had a chance to test this since the fix was implemented. I've moved on from MATE due to this bug, but now that it was fixed, I've decided to try it out. So far, I cannot reproduce this anymore. I may consider returning to MATE, I appreciate the hard work that's going into it.

jlacroix82 commented Jun 12, 2017

I apologize that I haven't had a chance to test this since the fix was implemented. I've moved on from MATE due to this bug, but now that it was fixed, I've decided to try it out. So far, I cannot reproduce this anymore. I may consider returning to MATE, I appreciate the hard work that's going into it.

@alcarola

This comment has been minimized.

Show comment
Hide comment
@alcarola

alcarola Jun 14, 2017

Hello,

I run Ubuntu 16.04.2 with the mate desktop with a dual-monitor setup and suffer from this bug, so I tried installing marco 1.16 from this ppa: https://launchpad.net/~ubuntu-mate-dev/+archive/ubuntu/xenial-mate
With the new mate version, I immediately noticed that my desktop became very sluggish, taking over a second to respond to desktop changes and clicks.

Hence, I tried opening mate tweak and changing compton compositing, but I still suffer from the problem.

Any advice on how to get my desktop to stop bugging? I am reluctant to upgrading to a newer version of ubuntu, since my computer is rather old and 16.04 is a long-term-support version which works great for me apart from this bug.

Thanks for any help!

Edit: Just as I posted this, I discovered that I should try
gsettings set org.mate.Marco.general auto-raise true
gsettings set org.mate.Marco.general focus-mode 'sloppy'

so I'm now trying that. Anyway, I'd be grateful for help.

alcarola commented Jun 14, 2017

Hello,

I run Ubuntu 16.04.2 with the mate desktop with a dual-monitor setup and suffer from this bug, so I tried installing marco 1.16 from this ppa: https://launchpad.net/~ubuntu-mate-dev/+archive/ubuntu/xenial-mate
With the new mate version, I immediately noticed that my desktop became very sluggish, taking over a second to respond to desktop changes and clicks.

Hence, I tried opening mate tweak and changing compton compositing, but I still suffer from the problem.

Any advice on how to get my desktop to stop bugging? I am reluctant to upgrading to a newer version of ubuntu, since my computer is rather old and 16.04 is a long-term-support version which works great for me apart from this bug.

Thanks for any help!

Edit: Just as I posted this, I discovered that I should try
gsettings set org.mate.Marco.general auto-raise true
gsettings set org.mate.Marco.general focus-mode 'sloppy'

so I'm now trying that. Anyway, I'd be grateful for help.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Jun 14, 2017

I recommend creating a new bug report. Your behavior isn't related to this bug.

jlacroix82 commented Jun 14, 2017

I recommend creating a new bug report. Your behavior isn't related to this bug.

@raveit65

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Jun 14, 2017

Member

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

Member

raveit65 commented Jun 14, 2017

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

@alcarola

This comment has been minimized.

Show comment
Hide comment
@alcarola

alcarola Jun 14, 2017

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.

alcarola commented Jun 14, 2017

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.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Jun 14, 2017

@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.

jlacroix82 commented Jun 14, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@alcarola

alcarola Jun 14, 2017

Indeed, thanks! :)

alcarola commented Jun 14, 2017

Indeed, thanks! :)

@owensss

This comment has been minimized.

Show comment
Hide comment
@owensss

owensss 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

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

This comment has been minimized.

Show comment
Hide comment
@naturally-intelligent

naturally-intelligent Oct 26, 2017

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.

naturally-intelligent commented Oct 26, 2017

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Oct 26, 2017

Member

Please file out a report against compiz at your distro.

Member

raveit65 commented Oct 26, 2017

Please file out a report against compiz at your distro.

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Oct 26, 2017

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.

jlacroix82 commented Oct 26, 2017

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Oct 26, 2017

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 :-)

Member

raveit65 commented Oct 26, 2017

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 :-)

@jlacroix82

This comment has been minimized.

Show comment
Hide comment
@jlacroix82

jlacroix82 Oct 26, 2017

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.

jlacroix82 commented Oct 26, 2017

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

This comment has been minimized.

Show comment
Hide comment
@naturally-intelligent

naturally-intelligent 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.)

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

This comment has been minimized.

Show comment
Hide comment
@spook

spook 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.

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

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Dec 21, 2017

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)?

Member

raveit65 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.

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

@raveit65

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Dec 21, 2017

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/

Member

raveit65 commented Dec 21, 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.)

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

@Dos98

This comment has been minimized.

Show comment
Hide comment
@Dos98

Dos98 Aug 6, 2018

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

Dos98 commented Aug 6, 2018

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

@raveit65

This comment has been minimized.

Show comment
Hide comment
@raveit65

raveit65 Aug 6, 2018

Member

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.

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

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