Network manager can't auto-connect to WLAN -- also teredo failure

freyr · 2011-04-13 07:57:52

Hi!

I've installed GNOME 3 from testing repo a few days ago. Network manager can't connect to WLAN automatically, but it can connect, I just need to click on the WLAN name at nm-applet. Of course it is set to auto connection.

everything.log:

Apr 13 09:27:22 lynx NetworkManager[2791]: <info> NetworkManager (version 0.8.998) is starting...
Apr 13 09:27:22 lynx NetworkManager[2791]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Apr 13 09:27:23 lynx polkitd[2800]: started daemon version 0.101 using authority implementation `local' version `0.101'
Apr 13 09:27:23 lynx NetworkManager[2791]: <error> [1302679643.506638] [nm-session-monitor.c:326] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
Apr 13 09:27:23 lynx NetworkManager[2791]: <error> [1302679643.506810] [nm-session-monitor.c:326] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile: parsing Auto Procyon lotor ... 
Apr 13 09:27:23 lynx NetworkManager[2791]: <error> [1302679643.536396] [nm-session-monitor.c:326] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile:     read connection 'Auto Procyon lotor'
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile: parsing Auto WebSTAR ... 
Apr 13 09:27:23 lynx NetworkManager[2791]: <error> [1302679643.544321] [nm-session-monitor.c:326] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile:     read connection 'Auto WebSTAR'
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile: parsing Auto Milestone 1761 ... 
Apr 13 09:27:23 lynx NetworkManager[2791]: <error> [1302679643.562975] [nm-session-monitor.c:326] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile:     read connection 'Auto Milestone 1761'
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile: parsing 1. vezetékes kapcsolat ... 
Apr 13 09:27:23 lynx NetworkManager[2791]: <error> [1302679643.581939] [nm-session-monitor.c:326] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile:     read connection '1. vezetékes kapcsolat'
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile: parsing Auto eth0 ... 
Apr 13 09:27:23 lynx NetworkManager[2791]: <error> [1302679643.626427] [nm-session-monitor.c:326] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
Apr 13 09:27:23 lynx NetworkManager[2791]:    keyfile:     read connection 'Auto eth0'
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> trying to start the modem manager...
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> monitoring kernel firmware directory '/lib/firmware'.
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> found WiFi radio killswitch rfkill2 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:04:00.0/ieee80211/phy0/rfkill2) (driver <unknown>)
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (driver acer-wmi)
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> found WWan radio killswitch rfkill1 (at /sys/devices/platform/acer-wmi/rfkill/rfkill1) (driver acer-wmi)
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> WiFi enabled by radio killswitch; enabled by state file
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> WWAN disabled by radio killswitch; enabled by state file
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> WiMAX enabled by radio killswitch; enabled by state file
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> Networking is enabled by state file
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): carrier is OFF
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): new Ethernet device (driver: 'tg3' ifindex: 2)
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): now managed
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): device state change: 10 -> 20 (reason 2)
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): bringing up device.
Apr 13 09:27:23 lynx kernel: tg3 0000:02:00.0: irq 48 for MSI/MSI-X
Apr 13 09:27:23 lynx kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): preparing device.
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (eth0): deactivating device (reason: 2).
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlagn' ifindex: 4)
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (wlan0): now managed
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (wlan0): device state change: 10 -> 20 (reason 2)
Apr 13 09:27:23 lynx NetworkManager[2791]: <info> (wlan0): bringing up device.
Apr 13 09:27:24 lynx NetworkManager[2791]: <info> (wlan0): preparing device.
Apr 13 09:27:24 lynx NetworkManager[2791]: <info> (wlan0): deactivating device (reason: 2).
Apr 13 09:27:24 lynx kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 13 09:27:24 lynx NetworkManager[2791]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Apr 13 09:27:24 lynx NetworkManager[2791]: <info> wpa_supplicant started
Apr 13 09:27:24 lynx NetworkManager[2791]: <info> (wlan0): supplicant interface state: starting -> ready
Apr 13 09:27:24 lynx NetworkManager[2791]: <info> (wlan0): device state change: 20 -> 30 (reason 42)
Apr 13 09:27:24 lynx NetworkManager[2791]: <info> (wlan0): supplicant interface state: ready -> inactive
Apr 13 09:27:25 lynx ntpd[2835]: ntpd 4.2.6p3@1.2290-o Sun Apr  3 17:50:25 UTC 2011 (1)
Apr 13 09:27:25 lynx ntpd[2836]: proto: precision = 0.769 usec
Apr 13 09:27:25 lynx ntpd[2836]: line 11 column 21 syntax error, unexpected T_String, expecting T_EOC
Apr 13 09:27:25 lynx ntpd[2836]: syntax error in /etc/ntp.conf line 11, column 21
Apr 13 09:27:25 lynx ntpd[2836]: line 12 column 20 syntax error, unexpected T_String, expecting T_EOC
Apr 13 09:27:25 lynx ntpd[2836]: syntax error in /etc/ntp.conf line 12, column 20
Apr 13 09:27:25 lynx ntpd[2836]: line 13 column 24 syntax error, unexpected T_String, expecting T_EOC
Apr 13 09:27:25 lynx ntpd[2836]: syntax error in /etc/ntp.conf line 13, column 24
Apr 13 09:27:25 lynx ntpd[2836]: line 16 column 26 syntax error, unexpected T_String, expecting T_EOC
Apr 13 09:27:25 lynx ntpd[2836]: syntax error in /etc/ntp.conf line 16, column 26
Apr 13 09:27:25 lynx ntpd[2836]: line 17 column 26 syntax error, unexpected T_String, expecting T_EOC
Apr 13 09:27:25 lynx ntpd[2836]: syntax error in /etc/ntp.conf line 17, column 26
Apr 13 09:27:25 lynx ntpd[2836]: line 18 column 26 syntax error, unexpected T_String, expecting T_EOC
Apr 13 09:27:25 lynx ntpd[2836]: syntax error in /etc/ntp.conf line 18, column 26
Apr 13 09:27:25 lynx ntpd[2836]: line 19 column 26 syntax error, unexpected T_String, expecting T_EOC
Apr 13 09:27:25 lynx ntpd[2836]: syntax error in /etc/ntp.conf line 19, column 26
Apr 13 09:27:25 lynx ntpd[2836]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Apr 13 09:27:25 lynx ntpd[2836]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Apr 13 09:27:25 lynx ntpd[2836]: Listen and drop on 1 v6wildcard :: UDP 123
Apr 13 09:27:25 lynx ntpd[2836]: Listen normally on 2 lo 127.0.0.1 UDP 123
Apr 13 09:27:25 lynx ntpd[2836]: Listen normally on 3 lo ::1 UDP 123
Apr 13 09:27:25 lynx ntpd[2836]: peers refreshed
Apr 13 09:27:25 lynx crond[2838]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel info
Apr 13 09:27:25 lynx acpid: starting up
Apr 13 09:27:25 lynx acpid: 1 rule loaded
Apr 13 09:27:25 lynx acpid: waiting for events: event logging is off
Apr 13 09:27:25 lynx osspd: OSS Proxy v1.3.2 (C) 2008-2010 by Tejun Heo <teheo@suse.de>
Apr 13 09:27:25 lynx osspd: Creating dsp (14:3), adsp (14:12), mixer (14:0)
Apr 13 09:27:39 lynx logger: ACPI group/action undefined: processor / CPU0
Apr 13 09:27:39 lynx logger: ACPI group/action undefined: processor / CPU1
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0) starting connection 'Auto Procyon lotor'
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> (wlan0): device state change: 30 -> 40 (reason 0)
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> (wlan0): device state change: 40 -> 50 (reason 0)
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0/wireless): access point 'Auto Procyon lotor' has security, but secrets are required.
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> (wlan0): device state change: 50 -> 60 (reason 0)
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 13 09:28:08 lynx NetworkManager[2791]: <warn> No agents were available for this request.
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> (wlan0): device state change: 60 -> 120 (reason 7)
Apr 13 09:28:08 lynx NetworkManager[2791]: <warn> Activation (wlan0) failed for access point (Procyon lotor)
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> Marking connection 'Auto Procyon lotor' invalid.
Apr 13 09:28:08 lynx NetworkManager[2791]: <warn> Activation (wlan0) failed.
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> (wlan0): device state change: 120 -> 30 (reason 0)
Apr 13 09:28:08 lynx NetworkManager[2791]: <info> (wlan0): deactivating device (reason: 0).
Apr 13 09:28:10 lynx acpid: client connected from 2996[0:100]
Apr 13 09:28:10 lynx acpid: 1 client rule loaded
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Successfully called chroot.
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Successfully dropped privileges.
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Successfully limited resources.
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Running.
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Watchdog thread running.
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Canary thread running.
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Successfully made thread 3069 of process 3069 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Apr 13 07:28:20 lynx rtkit-daemon[3071]: Supervising 1 threads of 1 processes of 1 users.
Apr 13 07:28:21 lynx rtkit-daemon[3071]: Successfully made thread 3074 of process 3069 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Apr 13 07:28:21 lynx rtkit-daemon[3071]: Supervising 2 threads of 1 processes of 1 users.
Apr 13 07:28:21 lynx rtkit-daemon[3071]: Successfully made thread 3075 of process 3069 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Apr 13 07:28:21 lynx rtkit-daemon[3071]: Supervising 3 threads of 1 processes of 1 users.
Apr 13 07:28:24 lynx rtkit-daemon[3071]: Successfully made thread 3095 of process 3095 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Apr 13 07:28:24 lynx rtkit-daemon[3071]: Supervising 4 threads of 2 processes of 1 users.
Apr 13 09:28:24 lynx pulseaudio[3095]: pid.c: Daemon already running.
Apr 13 09:28:37 lynx kernel: EXT4-fs (sda5): re-mounted. Opts: commit=0
Apr 13 09:28:38 lynx kernel: EXT4-fs (sda6): re-mounted. Opts: commit=0
Apr 13 09:28:43 lynx accounts-daemon[3260]: started daemon version 0.6.8
Apr 13 09:29:02 lynx miredo[2778]: Cannot resolve Teredo server address "teredo.remlab.net": Temporary failure in name resolution

After manual connect:

Apr 13 09:28:43 lynx accounts-daemon[3260]: started daemon version 0.6.8
Apr 13 09:29:02 lynx miredo[2778]: Cannot resolve Teredo server address "teredo.remlab.net": Temporary failure in name resolution
Apr 13 09:30:42 lynx miredo[2778]: Cannot resolve Teredo server address "teredo.remlab.net": Temporary failure in name resolution
Apr 13 09:32:22 lynx miredo[2778]: Cannot resolve Teredo server address "teredo.remlab.net": Temporary failure in name resolution
Apr 13 09:32:51 lynx kernel: chromium-sandbo (3326): /proc/3324/oom_adj is deprecated, please use /proc/3324/oom_score_adj instead.
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) starting connection 'Auto Procyon lotor'
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> (wlan0): device state change: 30 -> 40 (reason 0)
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> (wlan0): device state change: 40 -> 50 (reason 0)
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0/wireless): access point 'Auto Procyon lotor' has security, but secrets are required.
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> (wlan0): device state change: 50 -> 60 (reason 0)
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> (wlan0): device state change: 60 -> 40 (reason 0)
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> (wlan0): device state change: 40 -> 50 (reason 0)
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0/wireless): connection 'Auto Procyon lotor' has security, and secrets exist.  No new secrets needed.
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Config: added 'ssid' value 'Procyon lotor'
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Config: added 'scan_ssid' value '1'
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Config: added 'psk' value '<omitted>'
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> Config: set interface ap_scan to 1
Apr 13 09:33:00 lynx NetworkManager[2791]: <info> (wlan0): supplicant interface state: inactive -> scanning
Apr 13 09:33:03 lynx kernel: wlan0: authenticate with 00:22:15:ad:86:4c (try 1)
Apr 13 09:33:03 lynx kernel: wlan0: authenticated
Apr 13 09:33:03 lynx kernel: wlan0: associate with 00:22:15:ad:86:4c (try 1)
Apr 13 09:33:03 lynx NetworkManager[2791]: <info> (wlan0): supplicant interface state: scanning -> associating
Apr 13 09:33:03 lynx kernel: wlan0: RX AssocResp from 00:22:15:ad:86:4c (capab=0x431 status=0 aid=1)
Apr 13 09:33:03 lynx kernel: wlan0: associated
Apr 13 09:33:03 lynx kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 13 09:33:03 lynx NetworkManager[2791]: <info> (wlan0): supplicant interface state: associating -> associated
Apr 13 09:33:03 lynx NetworkManager[2791]: <info> (wlan0): supplicant interface state: associated -> group handshake
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> (wlan0): supplicant interface state: group handshake -> completed
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Procyon lotor'.
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> (wlan0): device state change: 50 -> 70 (reason 0)
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> dhcpcd started with pid 3434
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 13 09:33:04 lynx dhcpcd[3434]: version 5.2.12 starting
Apr 13 09:33:04 lynx dhcpcd[3434]: wlan0: rebinding lease of 192.168.0.10
Apr 13 09:33:04 lynx NetworkManager[2791]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Apr 13 09:33:05 lynx dhcpcd[3434]: wlan0: acknowledged 192.168.0.10 from 192.168.0.1
Apr 13 09:33:05 lynx dhcpcd[3434]: wlan0: checking for 192.168.0.10
Apr 13 09:33:10 lynx dhcpcd[3434]: wlan0: leased 192.168.0.10 for 3600 seconds
Apr 13 09:33:10 lynx NetworkManager[2791]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Apr 13 09:33:10 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 13 09:33:10 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Apr 13 09:33:10 lynx NetworkManager[2791]: <info>   address 192.168.0.10
Apr 13 09:33:10 lynx NetworkManager[2791]: <info>   prefix 24 (255.255.255.0)
Apr 13 09:33:10 lynx NetworkManager[2791]: <info>   gateway 192.168.0.1
Apr 13 09:33:10 lynx NetworkManager[2791]: <info>   nameserver '79.121.0.2'
Apr 13 09:33:10 lynx NetworkManager[2791]: <info>   nameserver '79.121.0.5'
Apr 13 09:33:10 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 13 09:33:10 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 13 09:33:10 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Apr 13 09:33:11 lynx NetworkManager[2791]: <info> (wlan0): device state change: 70 -> 100 (reason 0)
Apr 13 09:33:11 lynx NetworkManager[2791]: <info> Policy set 'Auto Procyon lotor' (wlan0) as default for IPv4 routing and DNS.
Apr 13 09:33:11 lynx NetworkManager[2791]: <info> Activation (wlan0) successful, device activated.
Apr 13 09:33:11 lynx NetworkManager[2791]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Apr 13 09:33:13 lynx kernel: wlan0: no IPv6 routers present

I start X with startx command. My .xinitrc is exec ck-launch-session gnome-session.

The miredo has some problem, too, but it's not as important yet.

Last edited by freyr (2011-04-13 08:05:28)

oliparcol · 2011-04-14 12:17:04

I have the same problem... and once I'm connected to a wifi network, I can't change

pntruongan · 2011-04-16 14:43:50

I have the same problem too

intgr · 2011-04-21 22:25:21

I had a problem with Wi-Fi in GNOME 3 too, but merely installing 'network-manager-applet' package fixed it. No need to run nm-applet even.

Shakz · 2011-04-21 23:30:07

Had to ditch networkmanager for wicd on my KDE install. It may work for you as well although networkmanager worked perfectly with gnome 3 for me at least.

Silversun · 2011-04-22 06:52:27

I had the same problem and switched from networkmanager to wicd.
It works well, now.

Padfoot · 2011-04-23 05:05:28

It seems Gnome 3 is in a slightly random state at the moment. While I don't have issues with my wi-fi, other things seem to work and then fail at random boots and other times.

One thing you might try with nm-applet to get wi-fi to connect automatically is change the following lines in /etc/rc.conf:

Change:

eth0="dhcp"
INTERFACES=(eth0)

to:

wlan0="dhcp"
INTERFACES=(wlan0)

Cheers.

pntruongan · 2011-04-23 07:22:34

intgr wrote:

I had a problem with Wi-Fi in GNOME 3 too, but merely installing 'network-manager-applet' package fixed it. No need to run nm-applet even.

Install network-manager-applet fixed mine too, thanks guy

Avatar · 2011-04-28 22:05:55

I had the same problem until I went to Network Settings -> Options and then checked the "Available to all users" checkbox.
In my case, I don't mind the network being available to all users and it solved the auto-connect issue.
Maybe that works for you?

Arch Linux

#1 2011-04-13 07:57:52

Network manager can't auto-connect to WLAN -- also teredo failure

#2 2011-04-14 12:17:04

Re: Network manager can't auto-connect to WLAN -- also teredo failure

#3 2011-04-16 14:43:50

Re: Network manager can't auto-connect to WLAN -- also teredo failure

#4 2011-04-21 22:25:21

Re: Network manager can't auto-connect to WLAN -- also teredo failure

#5 2011-04-21 23:30:07

Re: Network manager can't auto-connect to WLAN -- also teredo failure

#6 2011-04-22 06:52:27

Re: Network manager can't auto-connect to WLAN -- also teredo failure

#7 2011-04-23 05:05:28

Re: Network manager can't auto-connect to WLAN -- also teredo failure

#8 2011-04-23 07:22:34

Re: Network manager can't auto-connect to WLAN -- also teredo failure

#9 2011-04-28 22:05:55

Re: Network manager can't auto-connect to WLAN -- also teredo failure

Board footer