I got an update of NetworkManager on March 16 that broke the wireless applet.
Only when I downgraded a number of components and rebooted could I select a
wireless network with the applet.
The components that I replaced are:
NetworkManager 0.7.0.r4359-15.1.1-x86_64 with 0.7.0.r4323-1.11-x86_64
NetworkManager-kde 0.7r848570-23.2.1-x86_64 with 0.7r848570-23.1-x86_64
NetworkManager-glib 0.7.0.r4359-15.1.1-x86_64 with 0.7.0.r4323-1.11-x86_64
NetworkManager-gnome 0.7.0.r1053-11.1.1-x86_64 with 0.7.0.r1043-1.9-x86_64
I have not looked at the logs to see what actually broke. I’ll do that and file
a bug report. I also do not know if 32-bit code is also broken.
I got an update of NetworkManager on March 16 that broke the wireless applet.
Only when I downgraded a number of components and rebooted could I select a
wireless network with the applet.
Interesting. As I read this thread earlier today, I was in the process of updating via zypper. Tonight, I find I have the same problem. Running opeSUSE 11.0 with these updates
NetworkManager-0.7.0.r3685-7.4 Tue 17 Mar 2009 22:12:42 NZDT
NetworkManager-glib-0.7.0.r3685-7.4 Tue 17 Mar 2009 22:11:53 NZDT
My vodafone gsm card (and I guess wireless devices as well) can’t be enabled from knetworkmanager. Just for the moment I have reverted to ‘traditional ifup’ method, and can connect with modem device config and ‘ifup modem0’. I guess I’ll have to back down to prior version as well.
Hmm, my wireless dies on me today also, on my 1st reboot after some updates. Think I may be having the same problem. I can’t connect at all from Suse, so I’m working from my XP install.
Working from within Yast, how do I downgrade/replace those components? Will I need access to the internet, or can I use my install DVD?
I experienced a broken wireless connection after updates also.I went to YAST, software management, installed and and searched out the network manager (I use gnome) and selected the program, clicked reinstall, apply. and rebooted for grins. Ta-da! Hope iit works for others. I’m still a Newbie ('bout a year) and am totally in love with SUSE linux. I’ve had some trouble with updates breaking things before but have so far not had a problem that I have not been able to find a solution for within the community. I’m finding over time that while it is not always obvious the fix has mostly been very simple. When my connection broke I started checking on things internally dmesg, AP authentication and association, ping, dns, etc and all checked out okay. Went back to the forums, FAQ’s,and How To’s to start looking for help and then I had a big “DUH” moment and reinstalled the network manager.
SparkieSteve wrote:
> deltaflyer44;1960178 Wrote:
>> Check the versions tab in YaST - software management & click the one
>> earlier than you have installed
>>
>> Andy
>
> Wow, that’s handy. Never knew about that - thank you
>
> Well, I had suceeded in rolling back the components, but it didn’t work
> for me. Wonder if my problem is the same? :
>
> Anyway, I just went into Yast and used the ‘Traditional method’
> approach and it’s worked a treat.
>
> I’ll go and enable those repos again now…
If you have the same problem as I do, you will see the following in
/var/log/NetworkManager
Mar 17 16:06:01 larrylap NetworkManager: <info> Activation (wlan2/wireless):
access point ‘lwfdjf_rad’ has security, but secrets are required.
Mar 17 16:06:01 larrylap NetworkManager: <info> (wlan2): device state change:
5 -> 6
Mar 17 16:06:01 larrylap NetworkManager: <info> Activation (wlan2) Stage 2 of
5 (Device Configure) complete.
Mar 17 16:06:01 larrylap NetworkManager: <WARN> get_secrets_cb(): Couldn’t get
connection secrets: A security policy in place prevents this sender from sending
this message to this recipient, see message bus configuration file (rejected
message had interface org.freedesktop.NetworkManagerSettings.Connection.Secrets"
member “GetSecrets” error name “(unset)” destination
“org.freedesktop.NetworkManagerUserSettings”).
Recent NetworkManager, dbus-1, hal upgrades as reported by this openSUSE Security Announcement suggest that the dbus system policy was too permissive.
This stated:
The new DBus policy is applied immediately to new connections so it
is advisable to apply the update for the affected packages in the
same update run as DBus.
To enable the syslog code the dbus-daemon needs to be restarted.
Doing so in the running system is not recommended so please reboot
the system after applying all updates.
In my case at least, I didn’t restart after the updates were installed as required. After doing this, NetworkManager is working as before. (Operator error).
Same thing worked for me. Couldn’t connect to Wireless and the error I got from /var/log/NetworkManager was:
Mar 19 12:16:11 mycomputer NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/0 failed to activate (timeout): (0) Connection was not provided by any settings service
Fixed it by plugging in a LAN cable and reinstalling the NetworkManager and NetworkManager-kde packages (NetworkManager-kde had a version older than the currently installed, shown in red, which makes me think that the problem has been fixed in the repositories already by downgrading the rpm to a previous version). After reinstallation, kill NetworkManager and start it again (or restart system). Voila!
Hope it helps.
Although I normally don’t use NWM I made little “non-representative” test on my Box with OS 11.1 i586 and x86_64 (as NWM was installed the whole time and of course also went through the mentioned updates).
On i586 no problems with the updates, switched to NWM instead of ifup and knetworkmanager worked immediately.
On x86_64 it was even worse than described before.
I had to downgrade all dbus- and NWM-packages to their version from oss-repo, to make it work.
After that I upgraded all dbus- and NMW-packages together in one go, rebooted the box and everything was fine.
Very odd, but worth a shot if everything else fails.
I couldn’t get connected to my network with kde4 no matter what I tried. I gave up and uninstalled kde4 and reinstalled kde3. That didn’t work either. I have encryption on and that compounded things.
This morning, after I booted up, network manager (the plasmoid) began working! I don’t know if it was only the downgrade, but I did something else new. I previously started kwallet to handle the password. Each time it tried to connect to my network, both networkmanager and kwallet would ask for a password. I supplied it to both and the connection failed. This morning, on a whim, I ignored the network manager request and supplied the password for only kwalet. The connection worked.
So, I don’t know which of these moving parts was the problem: kde4 network manager, kwallet, the plasmoid.
In my case, it definitely is the NM/DBus interaction. NM is unable to provide
the “secret” due to a permission problem. I filed a Bug for my problem and
someone from openSUSE just asked me to upgrade again, reboot, and post the logs.
My problem is on an x86_64 system.
Neither my ethernet nor my wireless works. All was fine this morning till I accepted some updates! I think using an earlier version of knetworkmanager might help me but unfortunately it seems files for earlier versions are not tored locally! Is it possible to find them else where and manually put them in their place? As of now yast is trying to go online to install the ealier version but, of course, the reason I want the earlier one i because I want to be able to go online! ANy help will be much appreciated.
It seems I managed to switch to an earlier version of knetworkmanager but I still have no internet. Has anyone been able to fix this successfully? I, unfortunately, didn’t make a note of the updates that I accepted, is there a way to find out which ones they are and additionally to reverse/remove them?
It was definitely the downgrade. I got over-confident and did a zypper up. That brought back newer versions of the networkmanager rpm’s. Wireless failed and I couldn’t get to the net to downgrade anymore! So, I dragged over a cable, downgraded again and marked the files taboo (or locked or whatever) so they wouldn’t be updated.
Now, with the addition of kwallet. It is working again. I don’t know if there is a way to keep these all files, in case I give in and try to upgrade in the future.
I do confirm the problem on a DELL XPS M1330 with OpenSuse 11.1 and gnome. After upgrade my WEP link to my AP has not been working anymore. The only solution has been downgrading NetworkManager to 0.7.0-r4332 release.
Everything works perfectly now.
