Set wireless to connect to a network with security: "WPA & WPA2 Personal". Ticked automatically connect to this network when it's available and it never does when I login. Reproducible: Always Steps to Reproduce: 1. Log in 2. Realize it's not going to automatically connect to wireless network 3. Connect to wireless network Actual Results: Doesn't automatically connect when I log in. Expected Results: Automatically connect when "automatically connect to this network when it's available" is ticked.
Which NetworkManager version do you use? Is "All users may connection to this network" checkbox checked for that connection?
Hmm. Ticking that box seems to have corrected it. Seems a bit obtuse though, no? I'm the only user on my machine. Version is 0.9.8.8ubuntu27
With that unchecked the connection's password is stored in kwallet. When you logs in Plasma NM tries to open wallet to retrieve the connection password and then send it to NetworkManager. Probably kwallet is broken in your system or kwallet's password dialog is hidden behind another window. After logging in try hitting Alt+Tab and check if there is a password dialog in the list. If it does then that is the problem. If not then probably there is something wrong with kwallet.
I am experiencing this problem. Seems that we should file a bug with kwallet? Because I do get the kwallet prompt at login and I put in my password. I still have to manually connect to wifi. I have to manually connect on suspend and sleep as well. My internet is really terrible so this make for an unpleasant experience.
I was experiencing this bug, and ticking that box fixed it. But really, that label is horrible, and does not convey accurately what is being chosen. How about: "Store password in networkmanager rather than in kwallet"
Valorie, "kwallet" is a technical term, it should not appear in user interface if not really necessary. Using "All users may connection to this network" has its side effects too. Secrets are stored in plan text by NetworkManager and any user can see the connection's secrets in Plasma NM's connection dialog in that case. I do not recommend using that option unless you know what you are doing it. It looks like there is a problem in kwallet or NetworkManager is not correctly handling "auto connect". Keep in mind that NetworkManager has its timeout for asking for password (5 minutes IIRC). After the 5 minutes timeout auto-connection will abort regardless if you had typed kwallet's password.
Changing some setting on the connect. No matter which. Makes aotu connection work until rebooting again.
Would be helpful to know what version of plasma-nm do you use? In the latest release we dropped support for plain text files and we store secrets under NetworkManager or in KWallet, but we unfortunately broke it for those with stored secrets in plain text files. One solution is to enable KWallet, edit your wireless connection, fill in your secrets and save it again. Those issues are already fixed in git and will be available in the next version.
$ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu28 Candidate: 0.9.8.8-0ubuntu28 Version table: *** 0.9.8.8-0ubuntu28 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Part of the problem is that kwallet has been broken since right before I upgraded. It reports that I have the wrong password, when I've been using that same password for a long, long time. So the wireless password is stored directly in networkmanager until I get Kwallet sorted.
I have the same bug as the original poster: after upgrading to Kubuntu 14.10, plasma-nm does not automatically connect to my wireless network anymore. Neither at log-in nor after suspend/resume. I have downgraded the wpasupplicant, network-manager and plasma-nm packages to their 14.04 versions (which used to work fine) and the problem persists, so I guess their another piece of code involved that should trigger the connection and fails to do so. If I could get some more background on what's involved I could try to find a working set and from there pinpoint the issue...
*** This bug has been marked as a duplicate of bug 340568 ***
I can confirm this very annoying bug, please try to solve it soon... I can make any tests you want to help you.
Created attachment 90101 [details] attachment-23985-0.html I had to restart Network Manager at some point and things started to work as expected when resuming from standby (suspend to RAM)... I suggest people having the issue update their system and try again. Please post whether this fixes the issue or not. On 23 December 2014 at 15:27, Tobias Bora <tobias.bora@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=339674 > > Tobias Bora <tobias.bora@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |tobias.bora@gmail.com > > --- Comment #12 from Tobias Bora <tobias.bora@gmail.com> --- > I can confirm this very annoying bug, please try to solve it soon... I can > make > any tests you want to help you. > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
Created attachment 90103 [details] attachment-27808-0.html On 23 décembre 2014 22:15:21 HNEC, "Hervé Fache " <herve@lucidia.net> wrote: >https://bugs.kde.org/show_bug.cgi?id=339674 > >--- Comment #13 from Hervé Fache <herve@lucidia.net> --- >I had to restart Network Manager at some point and things started to >work >as expected when resuming from standby (suspend to RAM)... >I suggest people having the issue update their system and try again. >Please >post whether this fixes the issue or not. > >On 23 December 2014 at 15:27, Tobias Bora <tobias.bora@gmail.com> >wrote: > >> https://bugs.kde.org/show_bug.cgi?id=339674 >> >> Tobias Bora <tobias.bora@gmail.com> changed: >> >> What |Removed |Added >> >> >---------------------------------------------------------------------------- >> CC| >|tobias.bora@gmail.com >> >> --- Comment #12 from Tobias Bora <tobias.bora@gmail.com> --- >> I can confirm this very annoying bug, please try to solve it soon... >I can >> make >> any tests you want to help you. >> >> -- >> You are receiving this mail because: >> You are on the CC list for the bug. >> > >-- >You are receiving this mail because: >You are on the CC list for the bug.
Created attachment 90104 [details] attachment-28043-0.html The thing is that a restart of network-manager solve the issue during the current session, but after a reboot the bug appears again. I tried to put service network-manager restart in /etc/rc.local but it's not enough…