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 788406 - "Launch new instance (middle click or ctrl-click) does not work for Files
"Launch new instance (middle click or ctrl-click) does not work for Files
Status: RESOLVED DUPLICATE of bug 756844
Product: gnome-shell
Classification: Core
Component: general
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-10-01 18:42 UTC by voidmage413
Modified: 2017-10-01 20:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description voidmage413 2017-10-01 18:42:33 UTC 
Steps to reproduce:
1.  Close all instances of Files.
2.  Open one instance of Files.
3.  Using Middle Click or Ctrl-Click, try to open a second instance of Files

Expected behavior:
Another instance of Files opens.

Actual behavior:  
The cursor goes into the spinning "wait" animation for a while, but Files does not open another instance.

Note: 
Right-clicking on the Files icon and selecting "New window" appears to still work, opening another instance of Files as expected. 

Tested on Arch Linux (Gnome 3.24) and CentOS 7 (Gnome 3.22) so far.
Comment 1 voidmage413 2017-10-01 18:45:18 UTC 
This bug does not appear to affect other applications, as far as I can tell.  Since the "Right-click --> New Window" option still works, I am not sure if this bug should be filed against Files or against the Gnome Shell Dash.  This is my first bug report here, so apologies in advance if I filed it under the wrong section or component.
Comment 2 Florian Müllner 2017-10-01 20:15:53 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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