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 100096 - Double click on file opens twice
Double click on file opens twice
Status: RESOLVED DUPLICATE of bug 91176
Product: nautilus
Classification: Core
Component: Navigation
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-12-02 07:02 UTC by Stephan Haller
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stephan Haller 2002-12-02 07:10:59 UTC
Package: nautilus
Severity: normal
Version: 2.0.5
Synopsis: Double click on file opens twice
Bugzilla-Product: nautilus
Bugzilla-Component: Navigation

Description:
Description of Problem:

If I double-click an file to open it with my default associated
application then two instances of this application with this file are
opened instead of one. Workaround is to right-click on this file and
select 'Open' in context-menu.

Steps to reproduce the problem:
1. Double-click on file to open with default application

Actual Results:

Two instance of associated application are open with selected file

Expected Results:

Only one instance should be opened.

How often does this happen?

Everytime.

Additional Information:

As mentioned above the workaround is to select the file I want to open
with the associated default application. Then call up the context menu
by right-clicking on selecting. In the context menu appearing choose
'Open'. This creates only one instance!

-- 
Stephan Haller <nomad@cadoritz.de>




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-12-02 02:10 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Stephan Haller 2002-12-02 07:37:14 UTC

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