Networkmanager Upgrade + No wireless

GogglesGuy · 2010-11-08 14:30:09

After the latest networkmanager upgrade I cannot connect to any wireless networks anymore. The nm-applet will list them but selecting them won't have any effect.

[2010-11-07 10:36] upgraded networkmanager (0.8.1-1 -> 0.8.2-1)
[2010-11-07 10:36] upgraded network-manager-applet (0.8.1-2 -> 0.8.2-2)
[2010-11-07 10:36] upgraded networkmanager-openvpn (0.8.1-1 -> 0.8.2-1)
[2010-11-07 10:36] upgraded networkmanager-pptp (0.8.1-1 -> 0.8.2-1)

Nothing relevant the log files:

Nov 8 08:14:08 huygens ntpd[7342]: adjusting local clock by 0.323734s
Nov 8 08:14:40 huygens NetworkManager[5982]: <info> WiFi now enabled by radio killswitch
Nov 8 08:14:40 huygens NetworkManager[5982]: <info> (wlan0): bringing up device.
Nov 8 08:14:40 huygens NetworkManager[5982]: <info> (wlan0): supplicant interface state: starting -> ready
Nov 8 08:14:40 huygens NetworkManager[5982]: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Nov 8 08:14:45 huygens dbus-daemon: [system] Reloaded configuration
Nov 8 08:14:45 huygens dbus-daemon: [system] Reloaded configuration
Nov 8 08:14:45 huygens dbus-daemon: [system] Reloaded configuration
Nov 8 08:14:45 huygens dbus-daemon: [system] Reloaded configuration
Nov 8 08:16:55 huygens ntpd[7342]: adjusting local clock by 0.322900s
Nov 8 08:17:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired.AN0RLV
Nov 8 08:17:41 huygens NetworkManager[5982]: keyfile: error: File did not exist or was not a regular file
Nov 8 08:17:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired.AN0RLV
Nov 8 08:17:41 huygens NetworkManager[5982]: keyfile: error: File did not exist or was not a regular file
Nov 8 08:17:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired
Nov 8 08:18:55 huygens ntpd[7342]: adjusting local clock by 0.223583s
Nov 8 08:22:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired.FQXRLV
Nov 8 08:22:41 huygens NetworkManager[5982]: keyfile: error: File did not exist or was not a regular file
Nov 8 08:22:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired.FQXRLV
Nov 8 08:22:41 huygens NetworkManager[5982]: keyfile: error: File did not exist or was not a regular file
Nov 8 08:22:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired
Nov 8 08:27:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired.I2XRLV
Nov 8 08:27:41 huygens NetworkManager[5982]: keyfile: error: File did not exist or was not a regular file
Nov 8 08:27:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired.I2XRLV
Nov 8 08:27:41 huygens NetworkManager[5982]: keyfile: error: File did not exist or was not a regular file
Nov 8 08:27:41 huygens NetworkManager[5982]: keyfile: updating /etc/NetworkManager/system-connections/Wired

wonder · 2010-11-08 15:32:20

thanks for using testing. it should be fixed in 0.8.2-2

GogglesGuy · 2010-11-08 20:25:18

wonder wrote:

thanks for using testing. it should be fixed in 0.8.2-2

This one still doesn't work for me. The wired connection works, but clicking on any of the wireless networks just doesn't do anything (in the network manager applet)

wonder · 2010-11-08 21:21:19

logs please

GogglesGuy · 2010-11-08 22:19:55

wonder wrote:

logs please

Here's the log after turning on the wireless hardware switch:

Nov 8 16:16:55 huygens kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0).
Nov 8 16:16:55 huygens kernel: atkbd serio0: Use 'setkeycodes e070 <keycode>' to make it known.
Nov 8 16:16:55 huygens kernel: atkbd serio0: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0).
Nov 8 16:16:55 huygens kernel: atkbd serio0: Use 'setkeycodes e070 <keycode>' to make it known.
Nov 8 16:16:55 huygens NetworkManager[3735]: <info> WiFi now enabled by radio killswitch
Nov 8 16:16:55 huygens NetworkManager[3735]: <info> (wlan0): bringing up device.
Nov 8 16:16:55 huygens kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 8 16:16:55 huygens NetworkManager[3735]: <info> (wlan0): supplicant interface state: starting -> ready
Nov 8 16:16:55 huygens NetworkManager[3735]: <info> (wlan0): device state change: 2 -> 3 (reason 42)

GogglesGuy · 2010-11-08 22:33:08

nm-applet spits out the following error/warning message when selecting one of the available wireless networks:

** (nm-applet:4813): WARNING **: <WARN> activate_connection_cb(): Connection activation failed: No user settings service available

GogglesGuy · 2010-11-08 23:01:10

I also like to mention that downgrading (disable Testing) will make things work again. I'm using XFCE here on 64 bit.

wonder · 2010-11-09 09:45:24

what is your login method into xfce? startx, login manager?

Cdh · 2010-11-09 12:51:23

With today's networkmanager update I still have the issue. (** (nm-applet:31786): WARNING **: <WARN> activate_connection_cb(): Connection activation failed: No user settings service available)

No login manager
~/.xinitrc

exec dbus-launch ck-launch-session /usr/bin/startxfce4

Last edited by Cdh (2010-11-09 12:52:31)

Dogmeat · 2010-11-09 13:01:12

Cdh: Are you aware of a bug in consolekit from testing? FS#21391

By the way, while networkmanager 0.8.2-1 wasn't working at all for me, networkmanager 0.8.2-2 works great with knetworkmanager from kdeplasma-applets-networkmanagement under KDE (login via KDM).

wonder · 2010-11-09 13:01:18

keep in mind that consolekit from testing doesn't work quite well using that method.

https://bugs.archlinux.org/task/21391

try shining suggestion

GogglesGuy · 2010-11-09 14:48:03

Yes, Shining's suggestion works. Is this a permanent solution or should we expect some changes?

wonder · 2010-11-09 15:04:34

GogglesGuy wrote:

Yes, Shining's suggestion works. Is this a permanent solution or should we expect some changes?

i'm not sure. but in any case, once is fixed, you shouldn't do anything special.

Tuxe · 2010-11-23 17:02:05

I had the same problem. shining's solution didn't work for me. Instead, I had to run ck-launch-session before starting nm-applet. I put

exec ck-launch-session dbus-launch $HOME/.xinitrc-ck-dbus $1

in my .xinitrc and .xinitrc-ck-dbus is where I start nm-applet, window manager etc. I'm using slim to login.

GogglesGuy · 2010-11-25 03:15:48

Tuxe wrote:

I had the same problem. shining's solution didn't work for me. Instead, I had to run ck-launch-session before starting nm-applet. I put
exec ck-launch-session dbus-launch $HOME/.xinitrc-ck-dbus $1
in my .xinitrc and .xinitrc-ck-dbus is where I start nm-applet, window manager etc. I'm using slim to login.

(I was running XFCE with startx with)

I think nowadays you almost cannot get away without using ck-launch-session if I'm not mistaken.
Shinings solution does work, but in combination with ck-launch-session. (which I already had in my xinitrc.)

whatshisname · 2010-11-25 16:17:42

I lost my ability to connect to wireless networks a couple of months ago and have pulled my hair out trying to solve it. I finally reinstalled Arch and while reconfiguring my new install I figured out network manager had been my problem all along.

https://bbs.archlinux.org/viewtopic.php?id=107609

Maybe it's not the most elegant solution but I've scrapped network and network manager and connect the old-fashioned way by calling a "connect" script in rc.local:

#!/bin/bash

ifconfig eth1 up
iwconfig eth1 essid MyRouter
dhclient -v eth1

Xiong Chiamiov · 2010-12-10 20:34:24

Added

session    optional    pam_loginuid.so
session    optional    pam_ck_connector.so

into /etc/pam.d/login and it worked once. Today I had to readd `ck-launch-session` to the front of the nm-applet launch in my .xinitrc (I removed it some months ago for some reason), and it works, hopefully for more than a day.

KoS · 2011-01-14 15:35:40

Someone should put ck-launch-session in .xinitrc if it is not using gdm. What if I'm using gdm? Should I put ck-launch-session somewhere?
I can not enable wireless in nm-applet.
I don't see any new log messages in dmesg, messages.log, daemon.log, kernel.log or everything.log when I try to enable the wireless. It still stays disabled.
I just switched from b43 to broadcom-wl before I realized that it's a networkmanager issue.

KoS · 2011-03-23 22:06:15

Guys, is this problem solved for everyone yet?
I tried ck-launch-session and pam modifications but they did not help. With the latest networkmanager-0.8.3-0.20110113 and network-manager-applet-0.8.2-4 I still can't enable the wireless with nm-applet. Unfortunately libnotify was recently updated so keeping back the update of these packages will be more and more painful
I will have to change from nm-applet if nothing helps.

SirYasoKuhl · 2011-03-27 08:05:15

I have installed a new archbox and nm-applet worked fine for me ( without ck-launch ) and everything.....later after i had setup my XDM nm-applet didtn work any longer.

Step 1 Added ck-session-launch to the startfile

result: nm-applet is starting from a non-priv. user, but doesnt do anything. The applet shows this error:

** (nm-applet:1909): WARNING **: <WARN>  activate_connection_cb(): Connection activation failed: No user settings service available

Step 2 After searchin some hours and following some links and trying different solutions i found a really good one:
Problem: It's a new security feature of the new version of consolekit (0.4.3)
Solution:
Create the file /etc/polkit-1/localauthority/50-local.d/org.freedesktop.NetworkManager.pkla

[nm-applet]
Identity=unix-group:plugdev
Action=org.freedesktop.NetworkManager.*
ResultAny=yes
ResultInactive=no
ResultActive=yes

and add yourself into the plugdev group

For more inforamtion see:
https://bbs.archlinux.org/viewtopic.php?id=113564

Last edited by SirYasoKuhl (2011-03-27 08:06:59)

KoS · 2011-04-12 20:41:01

Unfortunately this still does not help to me ...
I don't get any error messages, nothing, simply nothing happens when trying to enable wireless... it still stays disabled.
Switching back to wicd ...

KoS · 2011-07-27 21:25:58

Ahh... one of my friends finally found the solution for my problem!

The problem is that the shitty acer_wmi kernel module is automatically loaded besides the real b43 or wl (broadcom-wl) module. That module does not do anything, just sits there and provides another non-real wireless hardware (one can list them with rfkill).
After blacklisting acer_wmi nm-applet works again! Finally!

Last edited by KoS (2011-07-27 21:27:38)

Arch Linux

#1 2010-11-08 14:30:09

Networkmanager Upgrade + No wireless

#2 2010-11-08 15:32:20

Re: Networkmanager Upgrade + No wireless

#3 2010-11-08 20:25:18

Re: Networkmanager Upgrade + No wireless

#4 2010-11-08 21:21:19

Re: Networkmanager Upgrade + No wireless

#5 2010-11-08 22:19:55

Re: Networkmanager Upgrade + No wireless

#6 2010-11-08 22:33:08

Re: Networkmanager Upgrade + No wireless

#7 2010-11-08 23:01:10

Re: Networkmanager Upgrade + No wireless

#8 2010-11-09 09:45:24

Re: Networkmanager Upgrade + No wireless

#9 2010-11-09 12:51:23

Re: Networkmanager Upgrade + No wireless

#10 2010-11-09 13:01:12

Re: Networkmanager Upgrade + No wireless

#11 2010-11-09 13:01:18

Re: Networkmanager Upgrade + No wireless

#12 2010-11-09 14:48:03

Re: Networkmanager Upgrade + No wireless

#13 2010-11-09 15:04:34

Re: Networkmanager Upgrade + No wireless

#14 2010-11-23 17:02:05

Re: Networkmanager Upgrade + No wireless

#15 2010-11-25 03:15:48

Re: Networkmanager Upgrade + No wireless

#16 2010-11-25 16:17:42

Re: Networkmanager Upgrade + No wireless

#17 2010-12-10 20:34:24

Re: Networkmanager Upgrade + No wireless

#18 2011-01-14 15:35:40

Re: Networkmanager Upgrade + No wireless

#19 2011-03-23 22:06:15

Re: Networkmanager Upgrade + No wireless

#20 2011-03-27 08:05:15

Re: Networkmanager Upgrade + No wireless

#21 2011-04-12 20:41:01

Re: Networkmanager Upgrade + No wireless

#22 2011-07-27 21:25:58

Re: Networkmanager Upgrade + No wireless

Board footer