Bug 344411

Summary:	Network manager applet prompts for password and resets it unnecessarily
Product:	[Plasma] plasma-nm	Reporter:	Dima Ryazanov <dima>
Component:	general	Assignee:	Lukáš Tinkl <lukas>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	jgrulich
Priority:	NOR
Version:	0.9.3.4
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dima Ryazanov 2015-02-20 22:54:38 UTC

I have a wired connection set up that uses the 802.1x security. I have the private key password saved in the connection settings.

If there's a failure while I'm trying to connect (e.g., because the wired network is not actually secured), I get a prompt "Please provide the password for activating connection 'connection'". That's pretty confusing:
- "connection 'connection'" is not helpful: the connection I'm using actually has a name, and it's not "connection". (Also, see bug 334901.)
- The only password I have is for my private key. It's used to decrypt the key locally, before the connection attempt even begins, so it should fail early, and can't possibly be the cause of a connection failure.
- The private key password is saved in the settings, so there's no need to prompt me for it.

Worse yet, if I enter something in the prompt, it gets saved as the new private key password. Now, even when I connect to the correct, secured network, I get a failure - this time, because my private key password is wrong. (And again, this should be caught early, before the connection starts.)


Reproducible: Always

Comment 1 Jan Grulich 2015-02-22 13:16:52 UTC

Git commit 7aa24f41996a05f9ac2f6ec95d8889f9f16e6457 by Jan Grulich.
Committed on 22/02/2015 at 13:16.
Pushed by grulich into branch 'master'.

Show correct connection name

In ConnectionSettings name is not actual name of the connection it represents, but
the name of setting type.
Related: bug 334901

M  +1    -1    kded/passworddialog.cpp

http://commits.kde.org/plasma-nm/7aa24f41996a05f9ac2f6ec95d8889f9f16e6457

Comment 2 Jan Grulich 2015-02-22 13:17:28 UTC

Git commit 51dab26b13082e3e5c0d26d0a2e6088940953eec by Jan Grulich.
Committed on 22/02/2015 at 13:16.
Pushed by grulich into branch 'Plasma/5.2'.

Show correct connection name

In ConnectionSettings name is not actual name of the connection it represents, but
the name of setting type.
Related: bug 334901

M  +1    -1    kded/passworddialog.cpp

http://commits.kde.org/plasma-nm/51dab26b13082e3e5c0d26d0a2e6088940953eec

Comment 3 Jan Grulich 2015-02-22 13:17:55 UTC

Git commit 8b21d56a83d622fde3eba117b8de1af03dd2bded by Jan Grulich.
Committed on 22/02/2015 at 13:16.
Pushed by grulich into branch '0.9.3'.

Show correct connection name

In ConnectionSettings name is not actual name of the connection it represents, but
the name of setting type.
Related: bug 334901

M  +1    -1    kded/passworddialog.cpp

http://commits.kde.org/plasma-nm/8b21d56a83d622fde3eba117b8de1af03dd2bded

Comment 4 Jan Grulich 2015-02-22 13:36:28 UTC

You should not use your secured connection for also unsecured networks, NM then probably tries to use your configuration and obviously fails, because your connection is configured for another network. It also makes sense that the new password gets saved, because that's mostly what you want and the password doesn't get saved only in case you explicitly set it shouldn't be stored.

Comment 5 Dima Ryazanov 2015-02-24 01:33:48 UTC

I completely agree. The problem is, in my case, the IT messed up and left the network unsecured. After they fixed it, I tried to connect again - and still failed because of this bug. I ended up wasting IT's time because I was assuming it was still a problem with the network, only to realize it was actually a problem on my end...