FS#21796 - [networkmanager] wlan disabled since upgrade yesterday
Attached to Project:
Arch Linux
Opened by Florian Apolloner (apollo13) - Tuesday, 23 November 2010, 08:21 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 30 November 2010, 19:14 GMT
Opened by Florian Apolloner (apollo13) - Tuesday, 23 November 2010, 08:21 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 30 November 2010, 19:14 GMT
|
Details
Since yesterday network-manager thinks the wlan is disabled;
though I am currently connected manually through wlan.
uname -a: Linux apollo13 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 21:22:26 CEST 2010 x86_64 Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz GenuineIntel GNU/Linux lspci|grep Net: 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35) driver in use: iwlagn networkmanager log: Nov 23 09:09:00 apollo13 NetworkManager[4294]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01). Nov 23 09:09:00 apollo13 NetworkManager[4294]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlagn' ifindex: 3) Nov 23 09:09:00 apollo13 NetworkManager[4294]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Nov 23 09:09:00 apollo13 NetworkManager[4294]: <info> (wlan0): now managed Nov 23 09:09:00 apollo13 NetworkManager[4294]: <info> (wlan0): device state change: 1 -> 2 (reason 2) Nov 23 09:09:00 apollo13 NetworkManager[4294]: <info> (wlan0): bringing up device. Nov 23 09:09:00 apollo13 NetworkManager[4294]: <info> (wlan0): deactivating device (reason: 2). |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Tuesday, 30 November 2010, 19:14 GMT
Reason for closing: Not a bug
Tuesday, 30 November 2010, 19:14 GMT
Reason for closing: Not a bug
03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5300
uname -a: Linux xxx 2.6.36-ARCH #1 SMP PREEMPT Wed Nov 24 00:39:57 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU L9400 @ 1.86GHz GenuineIntel GNU/Linux
login method: I am not using a login manager. I log in via terminal and run xinit.
/var/log/daemon.log: http://pastebin.com/a0VwEK65
rfkill list: http://pastebin.com/CVQzrV7y
packages:
extra/network-manager-applet 0.8.2-2
extra/networkmanager 0.8.2-6
I use startx, ~/.xinitrc:
nm-applet --sm-disable &
exec ck-launch-session dbus-launch openbox
/var/log/daemon.log:
http://pastebin.com/qESRNSuY
Console output of nm-applet (from startx TTY):
** (nm-applet:3632): WARNING **: <WARN> activate_connection_cb(): Connection activation failed: No user settings service available
rfkill list:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
I had 700, changed it to 755. No difference.
I figured out I just have to kill and restart nm-applet after a reboot then it is working fine.
This is how I start nm-applet in my ~/.xinitrc:
if [ -x /usr/bin/nm-applet ] ; then
nm-applet --sm-disable &
fi
exec ck-launch-session xmonad
Any chance you could tell how to start nm-applet correctly?
#!/bin/sh
if [ -x /usr/bin/nm-applet ] ; then
nm-applet --sm-disable &
fi
exec xmonad
run this script from your .xinitrc using
exec ck-launch-session sh ~/.xsession
instead of exec ck-launch-session xmonad.