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 775358 - Existing gedit window does not come to the front when another document is opened from nautilus
Existing gedit window does not come to the front when another document is ope...
Status: RESOLVED DUPLICATE of bug 766284
Product: gedit
Classification: Applications
Component: file loading and saving
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2016-11-29 19:15 UTC by Nate Graham
Modified: 2017-01-07 19:15 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22



Description Nate Graham 2016-11-29 19:15:14 UTC
Description:
in GNOME 3.22 on Fedora 25, opening a document in gedit when there is already a gedit window open does not bring it to the front.

Steps to reproduce:
1. Open a document in gedit.
2. Open a nautilus window and cover the gedit window with it.
3. Navigate to another text file in that nautilus window and open it.

Expected results:
gedit jumps to the front, displaying the just-opened file in a new tab.

Actual results:
gedit opens the file in a new tab, but does not bring itself to the front. If the prior gedit window wasn't visible at all, there is no way to know whether the document opened successfully. This is not especially user-friendly. A novice might easily assume that the file couldn't be opened or something.

Additional information:
Seems related to or a recurrence of https://bugzilla.gnome.org/show_bug.cgi?id=324148, which was reported fixed 9 years ago.
Comment 1 Nate Graham 2016-11-29 21:43:51 UTC
Duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=768151

*** This bug has been marked as a duplicate of bug 768151 ***
Comment 2 Michael Catanzaro 2017-01-07 19:15:34 UTC

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