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 349406 - opening files on a samba share launches gedit instead of another specified app
opening files on a samba share launches gedit instead of another specified app
Status: RESOLVED NOTABUG
Product: nautilus
Classification: Core
Component: Metadata
2.14.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-31 09:54 UTC by Glenn Jahnke
Modified: 2007-12-09 10:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Glenn Jahnke 2006-07-31 09:54:37 UTC
Please describe the problem:
Despite changing the "Opens with" dialog to point to my text editor of choice, SciTE or some other text editors, gedit opens.

Steps to reproduce:
1. open nautilus and navigate to a folder on a remote samba server
2. right-clicked on a file with application/x-php mime-type (php file)
3. clicked add and browsed for other text editor (I chose SciTE and tried both relative and non-relative paths)
4. selected the radio button for SciTE that showed up in the list and closed the dialog
5. double-clicking any php file continued to launch gedit


Actual results:
Despite changing the program associated with that mime-type, gedit launches and opens that file for editing

Expected results:
the program associated with that mime-type to open the file instead of gedit

Does this happen every time?
Yes, now no matter what, gedit opens the files

Other information:
I believe this was previously working, and an update was pushed out and it broke.
Comment 1 William Lovaton 2007-12-08 23:58:30 UTC
Are you still seeing this problem?  maybe the other programs doesn't support gnome-vfs and hence they can't open files on a remote location.  May be we should close this bug report unless it's still happening with the latest version of gnome.

Cheers.