Bug 307710

Summary:	password for TTLS network is not remembered when kwallet is not enabled
Product:	[Unmaintained] Network Management	Reporter:	Piotr Mitas <yabolus>
Component:	Wireless	Assignee:	Lamarque V. Souza <lamarque>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Piotr Mitas 2012-10-02 09:45:12 UTC

Currently to connect to a TTLS secured network I have to do the following every time:

1. Go to the applet's configuration screen
2. Select my the network and click Edit.
3. Wait 25 seconds for a dbus error saying "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.", click ok.
4. Enter my password in the settings dialog, confirm.
5. Connect to the network.

The password then works only once. If I disconnect, or the connection fails I have do all of this again.

Connecting to a WPA2 Personal network works fine and the password is stored correctly.

Reproducible: Always

Comment 1 Piotr Mitas 2012-10-02 09:47:54 UTC

Sorry, forgot to add, network management applet version 0.9.0.4, networkmanager 0.9.6.0, KDE 4.9.1, on Gentoo Linux.

Comment 2 Piotr Mitas 2012-10-02 10:53:23 UTC

Just updated to version 0.9.0.5, the error message changed to "No agents were available for this request." and there is no longer a 25 second wait. The password is still not being saved.

Comment 3 Lamarque V. Souza 2012-10-02 12:41:56 UTC

Is kwallet enabled? Do you use systemd? I also use Gentoo and I do have not this  problem here, but I know systemd can cause such problems and kwallet is the preferred secret storage for Plasma NM.

Comment 4 Piotr Mitas 2012-10-02 13:26:57 UTC

I didn't have KDE wallet enabled. Enabling it seems to have fixed this issue. I'll be able to confirm this 100% tomorrow (I don't have access to that network now). The password does seem to to be saved correctly.

Still, if there are technical issues with using whatever is being used when kwallet is disabled, a more informative error message would be nice.

I don't use systemd.

Comment 5 Lamarque V. Souza 2012-10-02 14:05:59 UTC

If you do not use kwallet you must configure Plasma NM to store secrets in plain text file (Manage Connections -> Other -> Store connection secrets -> In file (unencrypted)).

The 25s timeout must be due to Plasma NM trying to contact kwallet and failing. The message "Did not receive a reply..." is the generic dbus message from something goes wrong.

The "No agents were available for this request." comes from NetworkManager and  is the generic error message when something goes wrong when retrieving secrets. If you configure Plasma NM to use 'In file' storage it should work, but as the configuration says Plasma NM will store secrets unencrypted.

Comment 6 Lamarque V. Souza 2012-10-02 14:10:24 UTC

Git commit ecb9e75286e2892f8b59a526400e37cc31b38d0d by Lamarque V. Souza.
Committed on 02/10/2012 at 16:08.
Pushed by lvsouza into branch 'master'.

Add warning when storage mode is kwallet and kwallet is not enabled. The
warning will be printed in ~/.xsession-errors.

M  +20   -0    libs/service/secretstorage.cpp

http://commits.kde.org/networkmanagement/ecb9e75286e2892f8b59a526400e37cc31b38d0d

Comment 7 Lamarque V. Souza 2012-10-02 14:11:32 UTC

Git commit 85f0437aafee9b1fc7f40781bfadbaafea9b7a19 by Lamarque V. Souza.
Committed on 02/10/2012 at 16:08.
Pushed by lvsouza into branch 'nm09'.

Add warning when storage mode is kwallet and kwallet is not enabled. The
warning will be printed in ~/.xsession-errors.
(cherry picked from commit ecb9e75286e2892f8b59a526400e37cc31b38d0d)

M  +20   -0    libs/service/secretstorage.cpp
M  +1    -1    plasma_nm_version.h

http://commits.kde.org/networkmanagement/85f0437aafee9b1fc7f40781bfadbaafea9b7a19

Comment 8 Piotr Mitas 2012-10-02 16:31:50 UTC

Do you mean these warnings will be *only* printed in .xsession-errors and or will they be actually shown to the user?

Comment 9 Lamarque V. Souza 2012-10-02 16:43:10 UTC

Only in ~/.xsession-errors. Users are supposed to look at ~/.xsession-errors when  anything goes wrong in any program (even non-KDE programs) that run in the Xorg's session (this includes all non-root programs, NetworkManager is not include here since it run as root).