RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Version-Release number of selected component (if applicable):
gvfs-1.4.3-17.el6

How reproducible:
100%

Steps to Reproduce:

1. Click on Places in Gnome
2. Click on Connect to Server
3. Set service type SSH
   Server: localhost
   User Name: name of user (e.g. test)

Actual results:
Display modal window with error message: cannot display location "sftp://test@localhost/"
Error reading from unix Input/Output Error

Expected results:
Succesful connection to ssh/sftp server

Additional info:
This problem occured only on architectures s390x, x86_64

It looks like duplicate of Bug 1118325 and it should be fixed in gvfs-1.4.3-18.el6. Isn't it?

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