[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Network Management] [Bug 314093] NM does not take the password out of the wallet when manually conn
From:       kabud <kaabud-kde () yahoo ! de>
Date:       2013-01-30 7:35:11
Message-ID: bug-314093-17878-dQg0cMPjN4 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=314093

--- Comment #3 from kabud <kaabud-kde@yahoo.de> ---
(In reply to comment #1)
> It may surprise you but when more than one wifi connection is set as
> auto-connect NetworkManager client's (Plasma NM, nm-applet, etc) have no
> control on which one the NetworkManager daemon will choose to activate.

Oh. Indeed it is a bit surprising. But I think this the issue that I am
observing is not caused by auto-connect. It is caused by manual connect.

> NetworkManager must be activating the wrong connection and then asking the
> password for that wrong connection. You can check if the passwords are
> correctly saved using kwalletmanager program. Search for the connection's
> ssid in kwalletmanager's dialog.
> 
Ok. I tried, but it is a rather cumbersome, since in kwalletmanager ->
kdewallet -> Network Management -> Maps there are quite a number of entries and
I don't really see how I can identify which line belongs to which network. I
managed to find the password of one of the networks (lets call it A) but I
couldn't find the password of the other (lets call it K). Maybe I overlooked
something? Maybe it has to do with the fact that K is a 'System connection'
whereas A is not?

Anyway, what I can do to convince myself that indeed both passwords are stored
is the following:
- set A to auto-connect and K NOT to auto-connect
- disable network/ re-enable
- NM connects to A just fine without asking me for the password
- set A to NOT auto-connect and K to auto-connect
- disable network/ re-enable
- NM connects to K just fine without askting for the password


> Send me the  ~/.xsession-errors file and NetworkManager's log for when the
> problem happens.

Ok, I attach a copy of .xsession-errors file after performing the following
sequence of events:
1 set both A and K to NOT auto-connect
2 rm .xsession-errors
3 reboot
4 click on A 
5 I'm asked for the kwallet password, I enter it
6 connection to A is established
7 click on K
8 I am asked for the password for K
9 I enter it, connecteion established
10 click on A
11 I am asked for A's password
12 enter A's password
13 connection to A is established
14 goto 7

maybe a relevant line from .xsession-errors is this:
kded(2753)/Network Management (NetworkManager backend)
ConnectionDbus::fromDbusMap: Setting  "802-1x" not initialized

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]