Bug 796707

Summary:	Places > Network fails
Product:	Red Hat Enterprise Linux 6	Reporter:	o.h.weiergraeber
Component:	gvfs	Assignee:	Ondrej Holy <oholy>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-09 14:29:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description o.h.weiergraeber 2012-02-23 14:26:40 UTC

Description of problem:
When selecting Places > Network, after a very long delay (>20 seconds) an error message pops up saying

-------------------------------------------------------------------------------
Could not display "network:///".
Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: 
the remote application did not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
Please select another viewer and try again.
-------------------------------------------------------------------------------

When the local firewall is disabled, this message appears only once after each login, and in subsequent trials an empty window is displayed. The latter might be the expected behavior, but I am not sure why this window never lists any of my linux machines.

Version-Release number of selected component (if applicable):
2.28.4-18

How reproducible:
always

Steps to Reproduce:
1. log in
2. choose Places > Network
3. try again with firewall disabled

Actual results:
error message given above

Expected results:
1. If no machines are found on the network, an empty window should be displayed.
2. A linux machine should find other linux machines on its network 

Additional info:

Comment 2 Tomáš Bžatek 2012-02-23 15:07:53 UTC

Firewall needs to be disabled (or a rule/exception should be in place) to allow replies from broadcast packets to come in. Both samba and avahi work that way.

Using network:// has always been tricky and doesn't work in all environments. You could see some debug output by killing gvfs processes and watching debug prints from the `GVFS_SMB_DEBUG=5 GVFS_DEBUG=1 /usr/libexec/gvfsd-smb-browse` command.

Please let me know if that helps to resolve the issue.

Comment 3 o.h.weiergraeber 2012-02-26 18:16:09 UTC

Thanks a lot for your reply. I tried the following:

- As root: service iptables stop; service ip6tables stop
- As normal user, killed that user's gvfs processes (as given by 'ps -ef | grep gvfs')
- As normal user: bash (my users have tcsh as default);
                  GVFS_SMB_DEBUG=5 GVFS_DEBUG=1 /usr/libexec/gvfsd-smb-browse

I can confirm the process is running. But this command did not yield ANY output, neither on the console nor in /var/log/messages. Where would you expect the output to go?

Comment 4 Suzanne Logcher 2012-03-07 21:28:06 UTC

This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.

Comment 5 RHEL Program Management 2012-07-10 07:59:44 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2012-07-10 23:23:08 UTC

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 7 RHEL Program Management 2012-09-07 05:27:23 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 8 Ondrej Holy 2015-10-09 14:29:34 UTC

This is an old bug report and there is no activity for several years. I can't reproduce the bug and there isn't enough info to fix it, so closing it. Feel free to reopen with additional info...