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 775802 - Opening an already opened file sometimes has no visible effect
Opening an already opened file sometimes has no visible effect
Status: RESOLVED DUPLICATE of bug 766284
Product: gnome-shell
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2016-12-08 12:20 UTC by William Di Luigi
Modified: 2016-12-08 13:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description William Di Luigi 2016-12-08 12:20:11 UTC
If I use nautilus to open e.g. a picture, I will see a new eog window that will pop up with the picture. The same happens with evince for PDF files.

However, if the file was *already opened* in eog (or evince), then the operation will have no visible effect. I would expect the (already opened) window to get focused, but nothing happens.

This is especially painful if the (already opened) window is somehow hidden, e.g. because it's minimized or because it's in a different workspace. When this happens, you are just left waiting for the file to open and wondering why it's taking so long.
Comment 1 Florian Müllner 2016-12-08 13:41:31 UTC
Do you see a notification like "Eog is now ready" when this happens? If not, then the window was not blocked by focus-stealing prevention and the issue is somewhere else (either in nautilus which launches the application, or the app not raising an existing window). Oh, and if you are using a wayland session, then bug 766284 sounds like a good guess.
Comment 2 William Di Luigi 2016-12-08 13:53:10 UTC
No I don't see a notification.

Yes I am using wayland and the issue you linked seems to be exactly the one I am experiencing.

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