Bug 344600

Is that Kubuntu 14.10? Because there was an issue in NetworkManager causing this problem.

(In reply to Jan Grulich from comment #1)
> Is that Kubuntu 14.10? Because there was an issue in NetworkManager causing
> this problem.

15.04 Beta 1.

Can you send me NetworkManager log? Is your connection configured to be connected automatically?

(In reply to Jan Grulich from comment #3)
> Can you send me NetworkManager log?
Would you please tell me how do I get that?

> Is your connection configured to be connected automatically?
I did not see the option to connect automatically. Could you tell me where that option is?

(In reply to marco_parillo from comment #4)
> (In reply to Jan Grulich from comment #3)
> > Can you send me NetworkManager log?
> Would you please tell me how do I get that?
"cat /var/log/syslog | grep NetworkManager"

> > Is your connection configured to be connected automatically?
> I did not see the option to connect automatically. Could you tell me where
> that option is?
In kde-nm-connection-editor edit your connection and go to "General configuration" tab.

Created attachment 91391 [details]
The Network Manager Log

(In reply to Jan Grulich from comment #5)
> (In reply to marco_parillo from comment #4)
> > (In reply to Jan Grulich from comment #3)
> > > Can you send me NetworkManager log?
> > Would you please tell me how do I get that?
> "cat /var/log/syslog | grep NetworkManager"

Thank you. I will attach it.

> > > Is your connection configured to be connected automatically?
> > I did not see the option to connect automatically. Could you tell me where
> > that option is?
> In kde-nm-connection-editor edit your connection and go to "General
> configuration" tab.

I suspect that this may be the secret. However, I get:

mparillo@mparillo-AOD255E:~$ kde-nm-connection-editor
The program 'kde-nm-connection-editor' is currently not installed. You can install it by typing:
sudo apt-get install plasma-nm
mparillo@mparillo-AOD255E:~$ sudo apt install plasma-nm
Reading package lists... Done
Building dependency tree       
Reading state information... Done
plasma-nm is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Sorry, I didn't realize you have Plasma 5, in Plasma 5 you have kde5-nm-connection-editor. In the provided log I don't see any attempt to auto-activate your connection.

(In reply to Jan Grulich from comment #8)
> Sorry, I didn't realize you have Plasma 5, in Plasma 5 you have
> kde5-nm-connection-editor.

Thank you.
I did open it (it briefly asked for my Plasma5 kwallet) and automatically connect was checked.
But, now, I cannot seem to connect at all (so I cannot send you the logs).

> In the provided log I don't see any attempt to
> auto-activate your connection.

Exactly. In Plasma 4, this happened automatically without having to use the connections editor.
It was the default behavior of the wireless network widget in the tray.

Another idea: When I try to connect from kde5-nm-connection-editor, kded5 asks for my kdewallet password (which just got migrated to KDE5). The system tray applet did not ask for a password. Could the two methods be using different password managers?

There shouldn't be any difference between activating a connection from the editor or from the applet, because both call same method. I'll have to try Kubuntu 15.04 beta to see what could be wrong there, because I don't have any problem here on Fedora.

Thank you very much for being willing to test on another distro (especially seeing your e-mail domain). Another idea: Could it have something to do with older, WEP security? I do know the installer does not allow me to connect to the WEP access point, so I have to install without a network and connect later. This was the case for both Plasma 4 and Plasma 5. The difference is that in Plasma 4 the applet automatically re-connected and in Plasma 5 it does not.

It has nothing to do with any wireless security type. I just tested Kubuntu 15.04 Beta 1 on livecd and didn't have any problem with password storing. I connected to a wireless network secured with WPA2 and re-connected again without any problem. I also tried to create a new wireless connection with WEP security and the password was stored/loaded properly so it's hard to say where could be a problem on your side. Did you upgrade from an older Kubuntu version or is that a fresh installation? What you can also try is to create a new user if it was not a fresh installation or you used your old $HOME directory.

*** Bug 341340 has been marked as a duplicate of this bug. ***

Thank you for checking. It was a fresh install for me. Perhaps with the duplicate bug report you found, there will be something in common, so I hope the other bug reporter has something to add.

Almost immediately on my first login, I saw something about a migration to a newer version of kwallet (I think it was kwallet). Could that have had any effect on storing the pass

However, I am pretty sure the password is stored, because when I use the applet to connect, it does so without asking me for the WEP password again. It is just that I would like it to connect automatically.

For me, it may very well have been a wallet issue.  It started connecting 
properly after I manually set the password in the network manager widget.

I think that the autoconnecting issue is still bug 340568, more specifically https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924

The problem with password storing is probably something else.

In a comment to https://plus.google.com/110954078302330754910/posts/bPkdrSHDS3E Sayantan Das reports
3. KDE wallet doesnt automatically unlock upon login. Hence WiFi is not connected until wallet is unlocked.
Could that be the root cause?

Yes, but it still doesn't explain why you are not prompted for KWallet password from our secret agent.

Did the situation change with any recent update?

(In reply to Jan Grulich from comment #20)
> Did the situation change with any recent update?

Not for me. I have been running upgrades (but not a clean install) and am up to Plasma 5.4.1.

One more thing to try, edit your connection and check "All users may connect to this network". This should force NM to store secrets in NM storage so it shouldn't require our secret agent for activation. I would also try a different user with fresh configuration just in case there is anything wrong with your configuration.

(In reply to Jan Grulich from comment #22)
> One more thing to try, edit your connection and check "All users may connect
> to this network". This should force NM to store secrets in NM storage so it
> shouldn't require our secret agent for activation. I would also try a
> different user with fresh configuration just in case there is anything wrong
> with your configuration.

I did a clean install of Manjaro today (Plasma 5.4.1), and every time I boot, I need to enter my password. Now that I think about it, my sudo and kwallet passwords are the same. Could that make it more difficult to debug?

What password you need to enter? For KWallet or for the wireless network? If for KWallet, then it's correct.

(In reply to Jan Grulich from comment #24)
> What password you need to enter? For KWallet or for the wireless network? If
> for KWallet, then it's correct.

The WEP Password, I only need to enter once (the first time I boot the installation). After that, with each re-boot, I am entering my kwallet password.

Then it's not a bug, it behaves as it should. If you don't want to enter KWallet password everytime you would need to store your WEP password into NetworkManager or do not use password for KWallet at all.

For some reason, this bug has been resolved. Perhaps coincidence, but when sitter fixed https://bugs.kde.org/show_bug.cgi?id=351805 I no longer had to enter my kwallet password to activate wifi with every re-boot.