Description of problem: Version-Release number of selected component (if applicable): mate desktop as of 7/21/20 How reproducible: always Steps to Reproduce: 1.one window has focus 2.focus switches to another newly selected window 3.close second window when done 4.focus does not return to first window Actual results: Expected results: focus return to previously focused window. Additional info: could not find anything meaningful about this after searching web. it is very common to work e.g. on a list of items in window 1, successively launching a second window to deal with each item. when done with the second window, return to where you were in the first window. This has always been the standard. e.g. I have "emacs -nw" running in xterm with the "open with" emacs package from melpa. in dired I run down a list of ".pdf" files and open one of them. Focus switches from the emacs window to the pdf application. When I close the pdf file, NO WINDOW has the focus. I would expect the emacs window to have the focus. This same behavior applies to other applications, not just emacs, xterm and the pdf viewer.
garberw@electron> ps aux | grep wayland earlyoom 5811 0.0 0.0 2616 1824 ? SLs Jul09 0:57 /usr/bin/earlyoom -r 0 -m 4 -M 409600 --prefer ^Web Content$ --avoid ^(dnf|packagekitd|gnome-shell|gnome-session-c|gnome-session-b|lightdm|sddm|sddm-helper|gdm|gdm-wayland-ses|gdm-session-wor|gdm-x-session|Xorg|Xwayland|systemd|systemd-logind|dbus-daemon|dbus-broker|cinnamon|cinnamon-sessio|kwin_x11|kwin_wayland|plasmashell|ksmserver|plasma_session|startplasma-way|xfce4-session|mate-session|marco|lxqt-session|openbox)$ garberw 3254090 0.0 0.0 216220 724 pts/2 S+ 18:02 0:00 grep --color=auto wayland garberw@electron> Seems wayland is running.
https://github.com/jothan/mate-window-manager/blob/master/doc/how-to-get-focus-right.txt this web page explains that this is an (unpopular) "feature" and not a bug. in gnome2 when you are (1) in a window and you (2) launch a second windowed program, after the second windowed program exits you expect (3) the focus to return to the first window. Instead this update on the github website above seems to make focus mainly dependent on where the pointer (mouse) is. It is therefore not a bug, but makes it awkward since the desktop is usually under the pointer, so you have to press "alt - tab" to switch to the previous window. Since pressing "alt-tab" over and over and over and over is already a big nuisance for something like programming or data entry, this mouse focus choice is not going to be a popular "feature" because now you have to press "alt-tab" twice as often, However, for some users mouse focus could be a useful "optional feature". Wiping out the traditional standard gnome2 behaviour is frustrating me. So what is "mouse focus" intended to help? Gamers? those kind of users probably would not use mate desktop anyway.
the problem is in the marco window manager. when switching to compiz window manager I get the desired standard traditional focus behavior, but then there are other distracting problems with compiz.
Talk with Mate developer at github. If there really something needs to be change it have to be done there. https://github.com/mate-desktop/marco/issues PS: I am using mouse focus to avoid mouse clicks, an i am not a gamer ;)
https://github.com/mate-desktop/marco/issues/647 moved this discussion to the above link; thank you :-) noted that others were confused by recent development of that code; looks like it is still active and not 100% finished (or just complicated). this is what the developer said in the documented source code. https://github.com/jothan/mate-window-manager/blob/master/doc/how-to-get-focus-right.txt can close this issue now. thank you :-)
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.