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 787917 - smb: Very vague "Invalid argument" error given when mounting host that isn't available
smb: Very vague "Invalid argument" error given when mounting host that isn't ...
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: smb backend
1.34.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2017-09-19 19:26 UTC by Michael Terry
Modified: 2018-09-21 18:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Terry 2017-09-19 19:26:59 UTC 
$ gio mount smb://nope/test
gio: smb://nope/test/: Failed to mount Windows share: Invalid argument

That's not a very user-friendly message.  Most users likely wouldn't even guess that the hostname was the problem there.

Might I suggest something like "Server %s not found" or similar?
Comment 1 Ondrej Holy 2017-09-21 16:05:07 UTC 
Thanks for your bug report. Yes, the error message is not optimal, but it is not as straightforward as it looks. EINVAL is returned from samba and it can probably have a lot of meanings. But it is true, that in most cases it probably means that server is not found. Will you please prepare patch?
Comment 2 Michael Terry 2017-09-26 17:01:31 UTC 
That is something I could prepare.  Not sure on timeline, but I'll add it to my todo list.
Comment 3 GNOME Infrastructure Team 2018-09-21 18:12:17 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/315.