Bug 1369578

Summary:	Opening a file on a remote share does not work via Thunar
Product:	[Fedora] Fedora	Reporter:	Robert Banfield <rbanfield>
Component:	Thunar	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	christoph.wickert, dhiru, kevin, nonamedotc
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 16:44:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robert Banfield 2016-08-23 20:23:27 UTC

Description of problem:
When attempting to open a file on a remote file share (I have tried smb and sftp), the file is not opened.  Additional looking at the problem shows that no argument is passed to the target executable.  The user is not informed of any failure.  Permission to open/read/write the target file has been verified.


Version-Release number of selected component (if applicable):
% rpm -q -a | grep -i thunar
thunar-media-tags-plugin-0.2.1-7.fc24.x86_64
Thunar-1.6.10-6.fc24.x86_64
thunar-volman-0.8.1-3.fc24.x86_64
thunar-archive-plugin-0.3.1-7.fc24.x86_64


How reproducible:
Every time

Steps to Reproduce:
1. Open remote file share in thunar (e.g. thunar smb://path/to/share)
2. Choose to open a remote file by double clicking or via right clicking + "Open With".  I have tried to open it with geany, bluefish, etc.

Actual results:
The program opens, however the target file is not loaded.

Expected results:
The target file is loaded in the application.

Additional info:
The result of 'ps' shows that the program was called with no arguments.  At a minimum, I would expect the program to be called with the remote location of the filename and push the responsibility upon the called program to understand how to open it (and for bluefish at least, this would have worked).  A message that the operation was going to fail would have also been helpful.  

When a local file is opened, 'ps' shows that the program has been called with the location of the target file.

Comment 1 Kevin Fenzi 2016-08-23 21:55:50 UTC

Do you have gvfs-smb installed?

Comment 2 Robert Banfield 2016-09-01 15:39:37 UTC

Sorry for the delay.  Yes I do have that installed:

[rbanfield@rbanfieldpc ~]$ rpm -q -a | grep gvfs-smb
gvfs-smb-1.28.3-1.fc24.x86_64

Comment 3 Kevin Fenzi 2016-09-02 23:09:52 UTC

Odd. I can't seem to duplicate this here. ;( 

If you make a brand new user and login as them, does it work there?

(That would tell us if it's system wide, or something per user).

Comment 4 Fedora End Of Life 2017-07-25 22:36:27 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-08-08 16:44:57 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.