After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 795534 - window not moving to foreground
window not moving to foreground
Status: RESOLVED DUPLICATE of bug 766284
Product: gedit
Classification: Applications
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2018-04-25 08:05 UTC by Peter
Modified: 2018-05-12 14:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peter 2018-04-25 08:05:38 UTC 
I'm used to call gedit with 'super' gedit <enter> which is pretty cool as it is fast and doesn't require me to play with Alt-tab or switching workspaces. But in recent versions, gedit started to create a new tab and keep it's window hidden under other windows(gedit can even be in a different workspace) instead of creating a new window. Looking on the Internet I found that I'm not the only one affected by this behavior change. Why this change was introduced? How to revert it?

As details of my environment I use the 'Alternatetab', and 'Launch new instace' extensions running on Fedora 27.

Thank you!
Comment 1 Strangiato 2018-05-12 14:19:13 UTC 
do you use Wayland or X11?
Comment 2 Peter 2018-05-12 14:28:21 UTC 
Wayland
Comment 3 Strangiato 2018-05-12 14:32:21 UTC 

*** This bug has been marked as a duplicate of bug 766284 ***
Comment 4 Peter 2018-05-12 14:35:11 UTC 
I do not expect to change workspace when I call gedit with 'super' gedit <enter>, I expect it to open a new window in the workspace I'm at and that gedit window comes to the foreground.

There was a behavior change and I want to know how to revert it.
Comment 5 Strangiato 2018-05-12 14:38:48 UTC 
the same problem was already reported (bug 787137) and marked as duplicate of bug 766284
Comment 6 Peter 2018-05-12 14:44:46 UTC 
oh that is frustrating, but you are right. Moving to Xorg solves the problem.

*** This bug has been marked as a duplicate of bug 766284 ***