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.
Bug 2095712 - nautilus with latest libsmbclient 4.16.1 fails to connect, nautilus with version 4.15.5 does just fine
Summary: nautilus with latest libsmbclient 4.16.1 fails to connect, nautilus with vers...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gvfs
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ondrej Holy
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-10 10:41 UTC by tuxbenutzer
Modified: 2022-11-08 10:44 UTC (History)
6 users (show)

Fixed In Version: gvfs-1.36.2-13.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:45:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-124975 0 None None None 2022-06-10 10:50:22 UTC
Red Hat Product Errata RHBA-2022:7587 0 None None None 2022-11-08 09:46:00 UTC

Description tuxbenutzer 2022-06-10 10:41:16 UTC 
Description of problem:
Running the Gnome desktop under COS8stream, after yesterdays update libsmbclient went to version 4.16.1 from the @basos. Today I realized that nautilus ("Files") could no longer connect to my Synology NAS via Samba. The error window said:
"Oops! Something went wrong.
Unhandled error message: Failed to mount Window share: Invalid argument"

Connection from an old Mac, however, worked. As well as connecting through nautilus via ssh.

After downgrading libsmbclient again to 4.15.5, nautilus could connect to the samba shares just fine again.



Version-Release number of selected component (if applicable):
good: 4.15.5
bad:  4.16.1


How reproducible: Reliably. Nautilus does not connect with libsmbclient 4.16.1 , instantly worked fine after downgrade to 4.15.5 (together with libwbclient, samba-client, samba-client-libs, samba-common, samba-common-libs)

Steps to Reproduce:
1. Have a NAS named diskstation setup with Samba shares. 
2. Have latest libsmbclient 4.16.1
3. Try to connect from nautilus as smb://diskstation

Actual results: No connection. Error message "Unhandled error message: Failed to mount Window share: Invalid argument"


Expected results: Connection asking for credentials.


Additional info: An strace output is available, if desired.
Comment 1 Martin Krajnak 2022-06-14 13:50:42 UTC 
gvfs-afp-1.36.2-12.el8.x86_64
gvfs-client-debuginfo-1.36.2-12.el8.x86_64
gvfs-tests-1.36.2-12.el8.x86_64
gvfs-mtp-debuginfo-1.36.2-12.el8.x86_64
gvfs-archive-1.36.2-12.el8.x86_64
gvfs-smb-1.36.2-12.el8.x86_64
gvfs-fuse-debuginfo-1.36.2-12.el8.x86_64
gvfs-devel-1.36.2-12.el8.x86_64
gvfs-debugsource-1.36.2-12.el8.x86_64
gvfs-afc-1.36.2-12.el8.x86_64
gvfs-gphoto2-debuginfo-1.36.2-12.el8.x86_64
gvfs-client-1.36.2-12.el8.x86_64
gvfs-gphoto2-1.36.2-12.el8.x86_64
gvfs-archive-debuginfo-1.36.2-12.el8.x86_64
gvfs-1.36.2-12.el8.x86_64
gvfs-mtp-1.36.2-12.el8.x86_64
gvfs-afp-debuginfo-1.36.2-12.el8.x86_64
gvfs-debuginfo-1.36.2-12.el8.x86_64
gvfs-afc-debuginfo-1.36.2-12.el8.x86_64
gvfs-fuse-1.36.2-12.el8.x86_64
gvfs-goa-debuginfo-1.36.2-12.el8.x86_64
gvfs-goa-1.36.2-12.el8.x86_64
gvfs-smb-debuginfo-1.36.2-12.el8.x86_64
Comment 6 errata-xmlrpc 2022-11-08 09:45:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gvfs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7587
Note You need to log in before you can comment on or make changes to this bug.