https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c1 --- Comment #1 from Fero Hrach 2011-05-28 15:58:43 UTC --- Created an attachment (id=431985) --> (http://bugzilla.novell.com/attachment.cgi?id=431985) NetworkManager log - network connection on wlan0 does not start at boot time -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c zj jia changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |bili@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c4 Fero Hrach changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hrach2@post.sk | --- Comment #4 from Fero Hrach 2011-05-30 20:40:32 UTC --- Hi Bin (I hope, this is your first name :-) ), looks like, it is not knetworkmanager/plasmoid issue. According this link I have installed nm-applet: http://susestarter.blogspot.com/2011/03/step-2-need-mobile-broadband-use-gno... But the results are the same. eth0 was successfully started in system boot, but WiFi system connection did not start automatically in system boot. Looks like, NM accepts only pre-installed system connection for eth0 and other system connections are ignored. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c6 Fero Hrach changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hrach2@post.sk | --- Comment #6 from Fero Hrach 2011-05-31 11:32:26 UTC --- Hi Bin, maybe you didnt understand my problem. Tests from terminal, you wrote, I should run from terminal, when LOGGED IN. nm-applet and also plasmoid can connect networks, when LOGGED IN. Problem is, I've configured WiFi system connection (/etc/NetworkManager/system-connections) and this should be automatically started with system boot (that means, in NOT LOGGED IN state). Listing of /etc/NetworkManager/system-connections directory: 9076787 -rw------- 1 root root 156 May 31 13:17 Auto eth0 9076971 -rw------- 1 root root 381 May 31 00:06 WifiConnection Both files have no autoconnect set (that means from documentation per default autoconnect=TRUE) Pre-installed wired configuration 'Auto eth0' works perfect, network is connected in system boot before LOGGED IN My 'WifiConnection' does not start automatically in system boot before LOGGED IN. (in LOGGED IN state this connection is started without problems) Should I run tests you wrote? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c8 Li Bin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |hrach2@post.sk --- Comment #8 from Li Bin 2011-06-01 09:24:05 UTC --- Fero, I've changed the wireless connection "Available to all users", then delete the "/var/log/NetworkManager". then reboot the system, after start, not log in the desktop, just in console(Ctrl + Alt + F1), view the /var/log/NetworkManager, found the wireless was auto-connected. And in the log you can found a lot of (wlan0)'s information. So it works fine for me. Could you make a test for it again? And attach your /var/log/NetworkManager again. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c10 --- Comment #10 from Fero Hrach 2011-06-01 20:37:30 UTC --- Created an attachment (id=432572) --> (http://bugzilla.novell.com/attachment.cgi?id=432572) NetworkManager log - after login -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c12 Fero Hrach changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|hrach2@post.sk | --- Comment #12 from Fero Hrach 2011-06-01 20:42:43 UTC --- Hi Bin, so there are full NetworkManager logs before login and after login with starting WiFiConnection. NetwrokManager logging entries after login start with timestamp Jun 1 22:09:06 (see NetwrokManager log after login) I hope, these logs helps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=696793 https://bugzilla.novell.com/show_bug.cgi?id=696793#c14 Li Bin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #14 from Li Bin 2011-12-07 08:56:30 UTC --- Thanks for the feedback, I still found the reason why you failed in 11.4. Anyway I'll close it as 'worksforme'. Thanks again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.