Giving invalid details in the connect to Windows server dialog gives two error messages

Bug #1400772 reported by PerfectCarl
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Files
Confirmed
Medium
Unassigned

Bug Description

When I enter invalid info to connect to Windows server dialog, I get an error message that is "Failed to mount Windows share" which is expected/

If I click to "continue" without changing anything, I get another message "Please verify your user details"

Note that the button label is changing. Not sure that this is a good idea

Tags: networking
Revision history for this message
PerfectCarl (name-is-carl) wrote :
Revision history for this message
PerfectCarl (name-is-carl) wrote :

Second error message

summary: - Giving invalid details in the connect to Windows server dialog gives one
- two error messages
+ Giving invalid details in the connect to Windows server dialog gives two
+ error messages
Changed in pantheon-files:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Jeremy Wootten (jeremywootten) wrote :

Could you suggest what the correct behaviour, error message (s) and button label(s) should be? Thanks.

Changed in pantheon-files:
status: Confirmed → Incomplete
Revision history for this message
PerfectCarl (name-is-carl) wrote :

I found the following behavior that can be related to that issue:

when I try to connect to a SAMBA folder that doesn't require a password as guest, the "connect to server" dialog shows me an error asking me for a password. When I try to click the connect button another time (without changing anything or inputting a password) it works

Revision history for this message
PerfectCarl (name-is-carl) wrote :

#3

Here is how I see things.

1) don't display two different error message for the same error

2) try to connect to the server before displaying a message (to fix #4).
Of course, the connection must not bock the ui thread

As for the error message, I have no idea.
It depends on what SAMBA gives us as error: are those codes? Or full fledged string that one must have to translate?

And about the button, I would stay with connect.
The button performs the same action, it should have the same label.
Changing it because there is an error ranges from confusing and borders to nagging.

Changed in pantheon-files:
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.